#22 perl 5.8.4 make test fails on gentoo

closed
nobody
None
5
2005-02-18
2004-06-07
Anonymous
No

from your provided gentoo distrib (
gentoo-i586-ext3-2g-deluxe ), if you update the system
(emerge system) it tries to get perl 5.8.4 which fails
on some of the time tests and hangs on the
lib/benchmark test.

this can be repeated by doing: emerge perl

also I downloaded the latest perl source and confirmed
this error once again. (make step works, make install
fails)

Thanks,
Kris

kbright@rocketmail.com

Discussion

  • George P Boutwell

    Logged In: YES
    user_id=30412

    Kris,

    Yes this is a known issue, as of right now we have no
    solution, but an workaround is available.

    Edit the ebuild for perl and comment out the line:

    emake test

    Thanks for taking the time to submit a bug.

    George

     
  • Clifford Caoile

    Clifford Caoile - 2004-09-03

    Logged In: YES
    user_id=3562

    Other workarounds (gleened off the mailing list when searching for "perl" (http://sourceforge.net/search/index.php?type_of_search=mlists&group_id=98788&forum_id=40587))

    1. Upgrade to a snapshot: 20040710 (However I have not tested this suggestion)
    2. emerge inject perl-5.8.4
    3. While experiencing the phenomenon of the no-progress compile, use "top" to check the process "perl" that should be taking 99% CPU time. Kill (kill -s TERM) that process and the emerge should finish.

    I have also submitted this bug to gentoo as "Bugzilla Bug 61098: In colinux, dev-lang/perl-5.8.4 does not completely compile, stuck on testing lib/Benchmark" (http://bugs.gentoo.org/show_bug.cgi?id=61098).

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    This has been fixed in recent code version. I believe
    snapshot 0710 compiles perl correctly, even though it
    doesn't address all of the gettimeofday problems.
    I can confirm that the code snapshot from 0820 compiles
    perl without issue, as my latest gentoo emerge had an perl
    update and went without hitch.

    So your choices are to

    1) update to 0710
    2) wait for next release
    3) get latest source and compile your self (or get one of
    the unoffical binaries that are available)
    4) Use the existing work arounds.

    Thanks,

    George

     
  • George P Boutwell

    • status: open --> closed
     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    This has been fixed in recent version of coLinux please
    upgrade to them.

     

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

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks