View previous topic :: View next topic |
Author |
Message |
lynczu n00b

Joined: 23 Dec 2005 Posts: 17
|
Posted: Tue Jan 31, 2006 1:12 am Post subject: Insecure RUNPATH's bug workaround |
|
|
Emerging gnome-base/libbonoboui ends with
Code: | prepallstrip:
strip: i686-pc-linux-gnu-strip --strip-unneeded
/usr/bin/bonobo-browser
/usr/bin/test-moniker
/usr/lib/libglade/2.0/libbonobo.so
/usr/lib/bonobo-2.0/samples/bonobo-sample-controls-2
/usr/lib/libbonoboui-2.so.0.0.0
removing executable bit: /usr/lib/libbonoboui-2.la
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
/tmp/portage/libbonoboui-2.10.1-r1/image//usr/lib usr/bin/bonobo-browser
/tmp/portage/libbonoboui-2.10.1-r1/image//usr/lib usr/bin/test-moniker
/tmp/portage/libbonoboui-2.10.1-r1/image//usr/lib usr/lib/libglade/2.0/libbonobo
.so
/tmp/portage/libbonoboui-2.10.1-r1/image//usr/lib usr/lib/bonobo-2.0/samples/bon
obo-sample-controls-2
!!! ERROR: gnome-base/libbonoboui-2.10.1-r1 failed.
Call stack:
ebuild.sh, line 1894: Called dyn_install
!!! Aborting due to serious QA concerns with RUNPATH/RPATH
!!! If you need support, post the topmost build error, and the call stack if rel
evant. |
Did anyone figure out workaround? I know this bug hasn't been fixed yet, but there exist workarounds for some packages..
Any ideas?
Last edited by lynczu on Wed Feb 01, 2006 1:45 pm; edited 1 time in total |
|
Back to top |
|
 |
lynczu n00b

Joined: 23 Dec 2005 Posts: 17
|
Posted: Tue Jan 31, 2006 1:48 am Post subject: |
|
|
Got it! I need to add these lines to libbonoboui-2.10.1-r1.ebuild and emerge goes without any problems:
Code: | src_install() {
/usr/bin/chrpath -r /usr/bin /tmp/portage/libbonoboui-2.10.1-r1/image/usr/bin/bonobo-browser
/usr/bin/chrpath -r /usr/bin /tmp/portage/libbonoboui-2.10.1-r1/image/usr/bin/test-moniker
/usr/bin/chrpath -r /usr/lib /tmp/portage/libbonoboui-2.10.1-r1/image/usr/lib/libglade/2.0/libbonobo
make DESTDIR=${D} install
} |
Maybe someone find it useful (:
ps. it needs emerged chrpath package |
|
Back to top |
|
 |
sethlang n00b

Joined: 28 May 2005 Posts: 14
|
|
Back to top |
|
 |
lynczu n00b

Joined: 23 Dec 2005 Posts: 17
|
Posted: Tue Jan 31, 2006 7:21 am Post subject: |
|
|
All problems with package's insecure runpaths/rpaths can be fixed this way - after libbonoboui I have problems with gtkmm: similar problem, similar solution. Whole scheme goes more or less like this:
warning about insecure runpaths
Code: | 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/gtkmm-2.8.1/image//usr/lib usr/lib/libgdkmm-2.4.so.1.0.24
=> /var/tmp/portage/gtkmm-2.8.1/image//usr/lib usr/lib/libgtkmm-2.4.so.1.0.24 |
2. edit gtkmm-2.8.1.ebuild
depending on the number of files with insecure runpath's, need to add this line for each file listed under QA notice, e.g.
Quote: | /usr/bin/chrpath -r /usr/lib /var/tmp/portage/gtkmm-2.8.1/image/usr/lib/libgtkmm-2.4.so.1.0.24
/usr/bin/chrpath -r /usr/lib /var/tmp/portage/gtkmm-2.8.1/image/usr/lib/libgdkmm-2.4.so.1.0.24 |
if src_install doesn't exist, create it and add at the end of the function:
Quote: | src_install() {
(...)
chrpath -r /usr/lib ${D}/usr/lib/libgtkmm-2.4.so.1.0.24
chrpath -r /usr/lib ${D}/usr/lib/libgdkmm-2.4.so.1.0.24
##make DESTDIR=${D} install
} |
Quote: | make DESTDIR=${D} install |
Normally there is no need to add this, just in case if compilation isn't even about to start (it happens sometimes, especially if src_install was created manually).
3. ebuild gtkmm-2.8.1.ebuild digest && emerge gtkmm
Hope it'll make emerging packages containing insecure RUNPATH's much easier (: |
|
Back to top |
|
 |
|