Results 1 to 5 of 5

Thread: suse-11.2: tcl threads, pydoc -g fix

  1. #1

    Default suse-11.2: tcl threads, pydoc -g fix

    $ pydoc -g
    dies with the last words:
    "TclError: out of stack space (infinite loop?)"

    This error may indicate that tcl has been compiled without thread support:
    http://bugs.python.org/issue3835#msg73304

    Solution:
    Download tcl-8.5.7-4.6.src.rpm from the "standard" repo.
    (download.opensuse.org/source/distribution/11.2/repo/oss/suse/src/)

    # rpm -ivh tcl-8.5.7-4.6.src.rpm
    # vi tcl.spec

    (1) add "http-4.15" to the "known-failures" list (line# 111)
    (2) fix the typo on line# 93: should be
    "--enable-threads",
    rather than "--enable-treads"
    (3) line# 104 ("instrumentation for profiling"):
    replace with PFLAGS=""

    # rpmbuild -bb --clean tcl.cpec
    # rpm -Uvh --force tcl-8.5.7-4.6.x86_64.rpm

    Reasons for the changes:
    (r1) test "http-4.15" fails since my isp screws DNS queries and "no_such_host" is redirected to earthlink-help.
    (r2) obvious typo
    (r3) buggy gcc-4.4 optimizer fails with
    "error: corrupted profile info...", - every time in different files.
    see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38292

    After the fix "pydoc -g" works fine.

    > uname -a
    2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux

  2. #2
    Join Date
    Sep 2008
    Location
    France
    Posts
    22

    Default Re: suse-11.2: tcl threads, pydoc -g fix

    Hello,

    I have the same problem with OpenSuse 11.4.
    I tried the modification above and I have the following error

    Code:
    Tests ended at Tue Feb 14 15:59:05 CET 2012
    all.tcl:        Total   24550   Passed  23280   Skipped 1269    Failed  1
    Sourced 137 Test Files.
    Files with failing tests: unixInit.test
    Number of tests skipped for each constraint:
            9       !ieeeFloatingPoint
            3       asyncPipeChan
            76      bigEndian
            5       bug-3057639
            1       dontCopyLinks
            59      emptyTest
            2       hasIsoLocale
            1       impossible
            30      knownBug
            2       largefileSupport
            100     localeRegexp
            50      longIs32bit
            14      macosxFileAttr
            17      memory
            40      nonPortable
            265     notRoot
            8       nt
            1       testWinCPUID
            7       testaccessproc
            1       testexprparser && !ieeeFloatingPoint
            8       testopenfilechannelproc
            7       teststatproc
            1       testwinclock
            21      testwordend
            3       unknownFailure
            2       unthreaded
            2       wideBiggerThanInt
            523     win
    + grep FAILED testresults
    + grep -Fqvwf known-failures
    + exit 1
    error: Bad exit status from /var/tmp/rpm-tmp.sT4JIG (%build)
    
    
    RPM build errors:
        Bad exit status from /var/tmp/rpm-tmp.sT4JIG (%build)

    Some Informations
    uname -r : 2.6.37.6-0.11-desktop
    tcl-8.5.9-2.11.x86_64
    gcc-4.5-19.1.x86_64

  3. #3
    Join Date
    Sep 2008
    Location
    France
    Posts
    22

    Default Re: suse-11.2: tcl threads, pydoc -g fix

    I tried with the last tcl-8.5.11-40.1.src.rpm
    version from /repositories/devel:/languages:/tcl/openSUSE_11.4
    and I have the following errors

    Code:
    Tests ended at Tue Feb 14 17:34:11 CET 2012
    all.tcl:        Total   27009   Passed  25732   Skipped 1272    Failed  5
    Sourced 137 Test Files.
    Files with failing tests: env.test httpold.test unixInit.test
    Number of tests skipped for each constraint:
            9       !ieeeFloatingPoint
            3       asyncPipeChan
            76      bigEndian
            5       bug-3057639
            1       dontCopyLinks
            59      emptyTest
            2       hasIsoLocale
            1       impossible
            1       knownBadTest
            30      knownBug
            2       largefileSupport
            100     localeRegexp
            50      longIs32bit
            14      macosxFileAttr
            17      memory
            40      nonPortable
            265     notRoot
            8       nt
            1       testWinCPUID
            7       testaccessproc
            1       testexprparser && !ieeeFloatingPoint
            8       testopenfilechannelproc
            7       teststatproc
            1       testwinclock
            21      testwordend
            3       unknownFailure
            2       unthreaded
            2       wideBiggerThanInt
            523     win
            2       win2000orXP
    + grep -Fqvwf known-failures
    + grep FAILED testresults
    + exit 1
    error: Bad exit status from /var/tmp/rpm-tmp.L6imTf (%build)
    
    
    RPM build errors:
        Bad exit status from /var/tmp/rpm-tmp.L6imTf (%build)
    Someone have an idea ?

  4. #4
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: suse-11.2: tcl threads, pydoc -g fix

    On 02/14/2012 05:46 PM, fchaudier wrote:
    >
    > I tried with the last tcl-8.5.11-40.1.src.rpm
    > version from /repositories/devel:/languages:/tcl/openSUSE_11.4
    > and I have the following error


    your subject line says suse-11.2 and the above line says openSUSE 11.4

    since there is no "suse-11.2" i have to wonder exactly what operating
    system and version you are using..

    return the terminal output from this command please:
    cat /etc/SuSE-release

    and also please describe you level of expertise with Linux and
    openSUSE...thanks

    --
    DD
    Read what Distro Watch writes: http://tinyurl.com/SUSEonDW

  5. #5
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: suse-11.2: tcl threads, pydoc -g fix

    On 02/14/2012 05:46 PM, fchaudier wrote:
    > I tried with the last tcl-8.5.11-40.1.src.rpm
    > --------------------
    > Tests ended at Tue Feb 14 17:34:11 CET 2012


    it is not at all clear to me what you have done:
    -what kind of "Tests ended"?
    -what was the command which kicked off these "tests"?
    -were the 'tests' performed on the rpm or using whatever is in the rpm?
    -what is in the RPM? what is the name of the application, and what it
    supposed to do?

    what kind of 'test' results were you expecting?

    is what you are showing us the output of an attempt to build a package
    from source?

    if so, show us both your command inputs (from the first character of the
    prompt and _all_ the out puts until the last character of the waiting
    prompt) all inside of code tags..

    --
    DD http://tinyurl.com/DD-Caveat
    Read what Distro Watch writes: http://tinyurl.com/SUSEonDW

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •