On 10/04/2011 12:13 PM, Caolán McNamara wrote:
On Tue, 2011-10-04 at 11:49 +0200, Stephan Bergmann wrote:
On 10/03/2011 12:45 PM, Caolán McNamara wrote:
A better solution might be to put a stock "libtool" into our tree, patch
it to smuggle the correct gb_LinkTarget__RPATHS entry into the link
l
On Tue, 2011-10-04 at 11:49 +0200, Stephan Bergmann wrote:
> On 10/03/2011 12:45 PM, Caolán McNamara wrote:
> > A better solution might be to put a stock "libtool" into our tree, patch
> > it to smuggle the correct gb_LinkTarget__RPATHS entry into the link
> > line, and then always copy our patched
On 10/03/2011 12:45 PM, Caolán McNamara wrote:
A better solution might be to put a stock "libtool" into our tree, patch
it to smuggle the correct gb_LinkTarget__RPATHS entry into the link
line, and then always copy our patched libtool over preexisting libtools
when we unpack "external" tarballs i
playing around with solenv/gbuild/ExternalLib.mk I see a bit of a
gotcha, though we've basically had it in the old build system too,
except not as obvious.
New one does basically
./configure --prefix=/path/to/solver
make install
which is cool, but libtool has this quirk that if then wants to ad
