| Summary: | dev-lang/pike fails with QA notice "insecure RUNPATH" | ||
|---|---|---|---|
| Product: | Gentoo Security | Reporter: | Francesco R. (RETIRED) <vivo> |
| Component: | Auditing | Assignee: | Gentoo Security <security> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 81745 | ||
======================================================= [ebuild N ] dev-lang/pike [7.6.24] +crypt -debug -doc -fftw +gdbm +gif +gtk -hardened +jpeg -kerberos +opengl +pdflib +scanner -svg +tiff +truetype +zlib 0 kB ======================================================= Dumping of some modules failed (not fatal) (0x0000000a) Could not resolv Getopt. (Perhaps the installed pike tree has been moved.) lib/master.pike:2337: master()->__lambda_65598_1_line_2334("Getopt") Dumping of some modules failed (not fatal) (0x0000000a) Could not resolv Getopt. (Perhaps the installed pike tree has been moved.) lib/master.pike:2337: master()->__lambda_65598_1_line_2334("Getopt") Dumping of some modules failed (not fatal) (0x0000000a) Pike installation completed successfully. make[2]: Leaving directory `/var/tmp/portage/pike-7.6.24/work/Pike-v7.6.24/build/linux-2.6.15-rc1-mm1-prof-i686' make[1]: Leaving directory `/var/tmp/portage/pike-7.6.24/work/Pike-v7.6.24' man: prepallstrip: strip: i686-pc-linux-gnu-strip --strip-unneeded usr/bin/pike [...] usr/lib/pike/modules/___MIME.so QA Notice: the following files contain insecure RUNPATH's Please file a bug about this at http://bugs.gentoo.org/ For more information on this issue, kindly review: http://bugs.gentoo.org/81745 /var/tmp/portage/pike-7.6.24/work/Pike-v7.6.24/build/linux-2.6.15-rc1-mm1-prof-i686/bundles/lib:/usr/local/lib:/usr/X11R6/lib usr/bin/pike !!! ERROR: dev-lang/pike-7.6.24 failed. !!! Function dyn_install, Line 1069, Exitcode 0 !!! Insecure binaries detected !!! If you need support, post the topmost build error, NOT this status message. =======================================================