Summary: | dev-libs/apr-util-1.6.1-r6[berkdb]: `apu-1-config --ldflags` contains reference to ${PORTAGE_TMPDIR} | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alessandro Barbieri <lssndrbarbieri> |
Component: | Current packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | floppym, ionen, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alessandro Barbieri
2021-03-18 00:25:48 UTC
I don't think /var/tmp/portage is problematic per se, although it's kind of interesting because it isn't going to be owned by root? I find it curious that this path is there at all, it's for a different package. I did try to reproduce but RUNPATH only has /usr/lib64 for me. I suspect something strange in output of one of: apu-1-config --includes apu-1-config --ldflags apu-1-config --link-ld apu-1-config --link-libtool apu-1-config --libs Please show them. Do you maybe use sys-devel/slibtool? If yes, then check if problem disappears after rebuilding dev-libs/apr and dev-libs/apr-util with sys-devel/libtool. apu-1-config --includes -I/usr/include/apr-1 -I/usr/include/db6.0 apu-1-config --ldflags -L/var/tmp/portage/dev-libs/apr-util-1.6.1-r6/temp apu-1-config --link-ld -laprutil-1 apu-1-config --link-libtool -laprutil-1 apu-1-config --libs -ldb-6.0 -lgdbm -lexpat I've reemerged apr apr-util and serf without slibtool but I get the same runpath (In reply to Alessandro Barbieri from comment #5) > apu-1-config --ldflags > -L/var/tmp/portage/dev-libs/apr-util-1.6.1-r6/temp It's not slibtool, looks like this happen when apr-util is built with USE=berkdb (wasn't when I tested before), and sure enough if I build serf after doing this I too get: Library runpath: [/usr/lib64:/tmp/portage/dev-libs/apr-util-1.6.1-r6/temp] |