notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.
New feature planned: get notified when the package is available. Now is the time to contribute ideas/suggestions.
non port: devel/libbonobo/files/patch-samples-echo-Makefile.in

Number of commits found: 2

Wednesday, 23 Jul 2014
10:28 tijl search for other commits by this committer
Remove two libtool fixes from Mk/Uses/libtool.mk.  They don't always work
when an older version of a package is installed.  This is the case when an
executable links with installed libraries and with uninstalled libraries
that link with other uninstalled libraries.  For each of the directly
linked libraries the executable will have an rpath (/usr/local/lib for the
installed libraries and a path under WRKDIR for each of the uninstalled
libraries), but not for the indirect libraries.  Both ld(1) and rtld(1)
search the rpath of the executable first before any rpath of libraries, so
the indirectly linked libraries will be found in /usr/local/lib if they are
installed instead of in WRKDIR.

With this commit executables will overlink with uninstalled indirect
libraries again so their location is added to the rpath of the executable.

This partially reverts r358784.

PR:		191611
Approved by:	portmgr (bapt)
Original commitRevision:362656 
Sunday, 22 Jun 2014
10:44 tijl search for other commits by this committer
Add 4 new sed commands to USES=libtool.  The first two apply some of the
changes that Debian made to their libtool.  The first command applies to
libtool versions 1.4 and up.  The second command is somewhat more elaborate
but essentially it uses the sed hold space to move an "elif...fi" block
down.  It applies to 2.x.  Together these reduce overlinking to unpatched
.la files (from ports that don't have USES=libtool yet but also .la files
in the work directory).

The third and fourth command fix relinking.  During staging libtool may
relink libA when it links to another library in the work directory libB.
The reason is that libA created during build phase has its runpath set to
the location of libB in the work directory.  This allows running an
executable that links to libA from within the work directory.  The relink
removes this extra runpath.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
Original commitRevision:358784 

Number of commits found: 2