Bugzilla Bug 114820

dev-perl/PerlQt appears to have insecure RUNPATH issues.  On emerging version
3.009_beta1, the following error appears on ~sparc;

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/PerlQt-3.009_beta1/image/usr/lib:/usr/qt/3/lib
usr/lib/perl5/site_perl/5.8.7/sparc-linux/auto/Qt/Qt.so
/var/tmp/portage/PerlQt-3.009_beta1/image/usr/lib:/usr/lib usr/bin/puic

This also happens with version 3.008-r1.  I've double checked neither 
ExtUtils-MakeMaker package is installed, so that should not be influencing this.

Having the same here with 3.008-r1:

man:
gzipping man page: Qt.3pm
prepallstrip:
strip: i686-pc-linux-gnu-strip --strip-unneeded
   usr/lib/libsmokeqt.so.1.2.1
   usr/lib/perl5/site_perl/5.8.7/i686-linux/auto/Qt/Qt.so
   usr/bin/puic
making executable: /usr/lib/libsmokeqt.so.1.2.1

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/PerlQt-3.008-r1/image/usr/lib:/usr/qt/3/lib
usr/lib/perl5/site_perl/5.8.7/i686-linux/auto/Qt/Qt.so


!!! ERROR: dev-perl/PerlQt-3.008-r1 failed.
!!! Function dyn_install, Line 1057, Exitcode 0
!!! Insecure binaries detected
!!! If you need support, post the topmost build error, NOT this status message.

Created an attachment (id=74406) [details]
Compile error of PerlQT-3.006

3.008 fails with same error as above, 3.006 fails with attached error, so there
are no working versions left (including bug #100215)

fyi, i am working on this, i've gotten one of the two fixed (Qt.so), still
working on getting the binary file fixed as well

Created an attachment (id=74709) [details]
Almost there (fixes this bug, brings a new one)

This is a test ebuild - works good on the first emerge

(In reply to comment #4)
> This is a test ebuild - works good on the first emerge

To clarify - the problem I've run into is this ebuild will work fine to install
PerlQt if its a fresh install, no problem - but if its a reinstall of the same
version, the configure bit hangs checking for smokeqt in what looks to be an
infinite loop. I'm thinking my hacks to make it compliant on one front are
confusing it on a second install. Open to feedback and suggestions, my brain hurts.

I realized on my way into work this morning that this ebuild doesn't have
anything akin to support for amd64/etc. (/usr/lib vs /usr/lib64, etc.) - should
be a quick change, but didn't want anyone going to town with this as is.

hold off on this patch - there is now a flurry of perl 5.8.7 based bugs for
runpath issues, its starting to look like something is amiss in 5.8.7 (soon as
i can confirm a test case at home)

Created an attachment (id=75096) [details]
Updated ebuild

Not only a version bump (seems upstream bumped 5 days after the previous beta),
but also a working version. I'm still not thrilled with some of the steps I've
taken for this ebuild, but it is functional, avoids all aforementioned errors,
and is being presented for comment.

(In reply to comment #8)
> Created an attachment (id=75096) [details] 

Sorry, forgot this wouldn't get passed through - this file should be called
PerlQt-3.009_beta2.ebuild

Jason: does the provided ebuild fix it for you ?

Yes, the ebuild works for me.

OK, then I guess Michael can go ahead...

Micheal any news on this one?

ebuild posted, sorry 'bout that

Looks to be fixed now.

*** Bug 121117 has been marked as a duplicate of this bug. ***

Beta works on AMD64 X2 system

*** Bug 124224 has been marked as a duplicate of this bug. ***

*** Bug 128331 has been marked as a duplicate of this bug. ***

I'm curious why this bug is marked resolved fixed when I just ran into this
issue last night with the current stable version, 3.008-r1. Shouldn't a
stabling bug be filed? The above bug is mine.

(In reply to comment #20)
> I'm curious why this bug is marked resolved fixed when I just ran into this
> issue last night with the current stable version, 3.008-r1. Shouldn't a
> stabling bug be filed? The above bug is mine.
> 

That's true, only x86 is stable for PerlQt-3.009_beta2. You might want to try
it.

I suppose the maintainers are working on marking stable this version on the
other archs.

*** Bug 165724 has been marked as a duplicate of this bug. ***