Summary: | dev-lang/parrot-2.9.1 doesn't find libpcre.so.0 in /lib(64) - fails tests, possibly runtime | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Leverton <levertond> |
Component: | [OLD] Development | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | kentnl, Martin.vGagern |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Leverton
2010-12-21 14:33:01 UTC
Which version of libpcre is that? That's dev-libs/libpcre-8.02 8.12 same issue it seems. dev-lang/parrot-3.6.0[pcre] fails to build for me: Compiled: parrot_nci_thunk_gen.o x86_64-pc-linux-gnu-gcc -o parrot_nci_thunk_gen "parrot_nci_thunk_gen.o" "/var/tmp/portage/dev-lang/parrot-3.6.0/work/parrot-3.6.0/src/parrot_config.o" -L"/var/tmp/portage/dev-lang/parrot-3.6.0/work/parrot-3.6.0/blib/lib" -lparrot -Wl,-E -Wl,--as-needed -lnsl -ldl -lm -lcrypt -lutil -lpthread -lrt -lreadline -lffi -lpthread -ldl -lm -L/usr/lib64 -licuuc -licudata -lpthread -ldl -lm Linked: parrot_nci_thunk_gen ./parrot_nci_thunk_gen \ --loader-name=Parrot_glut_nci_loader \ --loader-storage-class=PARROT_DYNEXT_EXPORT \ --output=src/glut_nci_thunks.c \ <src/glut_nci_thunks.nci Failed to load libpcre current instr.: 'parrot;PCRE;init' pc 249 (runtime/parrot/library/pcre.pir:162) called from Sub 'read_one_sig' pc 1982 (tools/dev/nci_thunk_gen.pir:861) called from Sub 'read_sigs' pc 1903 (tools/dev/nci_thunk_gen.pir:823) called from Sub 'main' pc 40 (tools/dev/nci_thunk_gen.pir:48) make: *** [src/glut_nci_thunks.c] Error 1 emake failed I guess this is the same problem. Has the same failure as #c4 stable amd64 [ebuild U ~] dev-lang/parrot-3.6.0 [3.3.0] USE="gdbm nls opengl pcre ssl unicode -doc -examples -gmp" 0 kB [ebuild U ~] dev-lang/rakudo-2011.07 [2011.04] USE="-doc" 0 kB Bug 377379 comment 5 has a patch that might help for this issue here as well. Should apply to parrot versions since 2.9.0, as those are the ones containing the commit that is suspected to have introduced this issue. Should be fixed in newer versions. |