Bug 62162 - untrusted RPATH in xmlcatalog
Summary: untrusted RPATH in xmlcatalog
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-31 14:10 UTC by Matthias Andree
Modified: 2004-02-03 09:31 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Andree 2004-01-31 14:10:25 UTC 
The libxml2 port installs lib/python2.3/site-packages/libxml2mod.so 
which lists
/usr/ports/textproc/libxml2/work/libxml2-2.6.5/.libs in its RPATH.
This shouldn't happen.

How-To-Repeat: install libxml2 package
readelf -d /usr/local/lib/python2.3/site-packages/libxml2mod.so | grep RPATH
Comment 1 Joe Marcus Clarke freebsd_committer freebsd_triage 2004-01-31 21:08:10 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->gnome

Over to libxml2 maintainers.
Comment 2 Joe Marcus Clarke freebsd_committer freebsd_triage 2004-01-31 21:08:27 UTC 
State Changed
From-To: open->closed

This is a noble effort you're undertaking, but this bug is a bit misplaced. 
The problem lies in libtool (and it's not just FreeBSD-specific).  Libtool 
will add all -L directories to RPATH (which is wrong IMHO).  Libtool should 
be patched to honor its own hardcode_minus_L variable, and not hardcode 
those paths if not requested.  Please take this up with the libtool developers. 
If you do get a patch that can be applied to FreeBSD, please send it to our 
libtool maintainer, ade.  Thanks.
Comment 3 Alexander Nedotsukov freebsd_committer freebsd_triage 2004-02-03 09:26:28 UTC 
State Changed
From-To: closed->open

Re-open PR for the good news.
Comment 4 Alexander Nedotsukov freebsd_committer freebsd_triage 2004-02-03 09:27:30 UTC 
State Changed
From-To: open->closed

After anoter attempt to beat the monster we found the 
solution. 
Please update your ports tree. This should be fixed now. 
Thanks to marcus for on-line collaboration.