#2908 HP Testsuite hangs with --enable-64bit --enable-threads

obsolete: 8.3.4

I am building on HPUX B.11.00 U 9000/785 2010024836 .
With compiler acc353 (/opt/ansic/bin/cc).

TCL version 8.3.4

The compilation is successful and no error is being
reported, but make test hangs at "basic.test".

I have checked later version of TCL, i am facing the
same problem (tcl8.3.5/8.4.1), only the latest release
successfully runs the testsuite. Due to policy reasons I
cannot migrate to later version. Also I have verified with
different compilers (3.23/3.39)

Following are the steps which I followed:-
./configure --enable-threads --enable-64bit --disable-
gcc --disable-shared
make test

If I drop --enable-threads testsuite works.
Also HP 32 has also successfully completed the testsuite
with enable-threads.

Is it known issue?


  • Don Porter

    Don Porter - 2004-10-04

    Logged In: YES

    Current release is Tcl 8.4.7.
    Please check whether you
    still have problems
    compiling/testing that release.

  • Don Porter

    Don Porter - 2004-10-04
    • assigned_to: nobody --> dgp
    • status: open --> pending-out-of-date
  • Jeffrey Hobbs

    Jeffrey Hobbs - 2004-10-04

    Logged In: YES

    Note that the user indicated the newer release already
    works. Of course, if something was corrected in that time
    (as it appears to have been), then the user already has
    indications of it. If you can't update for policy reasons,
    you are stuck (seems silly to have a policy that enforces
    using buggy code).

  • Don Porter

    Don Porter - 2004-10-04
    • status: pending-out-of-date --> closed-out-of-date
  • Don Porter

    Don Porter - 2004-10-04

    Logged In: YES

    sorry, I missed that. Should have
    read more carefully.

    Best course is to upgrade to 8.4.7,
    but if policy forbids that, perhaps
    it would allow a bug fix patch
    applied to 8.3.4? It will be quite a
    bit of work to find/develop that patch,
    but if 8.4.7 works, that ought to at
    least be an existence proof that
    the fix is in the development
    history somewhere. Good luck.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks