A "*-g*" in CFLAGS (and no DEBUGGING setting) results in a perl built with -DDEBUGGING in CFLAGS ("internal debugging code","bigger and will run more slowly"). This is fixed in perl-5.12.1-r2. The additional debugging code will only be added if USE=debug is set. Problem: ======== Modules built for perl-5.12.1-r1 with -g in CFLAGS and USE=-debug will *not* work with perl-5.12.1-r2 with -g in CFLAGS and USE=-debug Solution: ========= You have to uninstall perl-core/File-Spec (if installed) run perl-cleaner: emerge -C perl-core/File-Spec && emerge -1 perl-core/File-Spec perl-cleaner --modules ; perl-cleaner --force --libperl
*** Bug 329339 has been marked as a duplicate of this bug. ***
[ebuild R ] dev-lang/perl-5.12.1-r2 USE="berkdb gdbm ithreads -build -debug -doc" 0 kB # perl -V:ccflags | grep DEBUGGING # seems to be working well here.
(In reply to comment #0) > Solution: > ========= > You have to uninstall perl-core/File-Spec (if installed) run perl-cleaner: > > emerge -C perl-core/File-Spec && emerge -1 perl-core/File-Spec > perl-cleaner --modules ; perl-cleaner --force --libperl Should be: perl-cleaner --allmodules ; perl-cleaner --force --libperl
*** Bug 343405 has been marked as a duplicate of this bug. ***
*** Bug 343049 has been marked as a duplicate of this bug. ***
This comment has been removed because it contained spam. -- idl0r
There is no packages who still have this bug.