Re: Libtool fails to build working binary when -no-install is used

[Simon Josefsson]

Ralf Wildenhues <address@hidden> writes:

> Hi Simon,
>
> Thanks for the bug report.
>
> * Simon Josefsson wrote on Thu, Mar 29, 2007 at 12:17:32PM CEST:
>>
>> /bin/sh ../libtool --tag=CC   --mode=link gcc  -DLIBSSH2_DARWIN -I/ 
>> usr/include -I/usr/include -no-install -L/usr/lib -lcrypto -L/usr/lib  
>> -lz -o simple simple.o ../src/libssh2.la
>> mkdir .libs
>> gcc -DLIBSSH2_DARWIN -I/usr/include -I/usr/include -o simple  
>> simple.o  -L/usr/lib ../src/.libs/libssh2.dylib -lcrypto -lz
>> make  check-TESTS
>> dyld: Library not loaded: /usr/local/lib/libssh2.1.dylib
>>    Referenced from: /Users/daniel/Desktop/libssh2/tests/./simple
>>    Reason: image not found
>> FAIL: simple
>
> Looks like a Darwin-related (hint, hint! ;-) bug to me.
>
> Note to self: expose -no-install in testsuite ((also) in stresstest.at
> as optional additional flag to `main' and `dlself').  No wonder it
> doesn't work: it's not covered in the testsuite.  :-/
>
> I think you should be able to work around it by adding
>   -R ../src
>
> to the link flags for `simple' (untested, please try it!  self: also put
> in testsuite), that should be more efficient than dropping -no-install
> and thus having the wrapper everywhere.

Hi Ralf!

I think removing the -no-install is a better workaround until libtool
is fixed.  Won't adding -R../src break on other platforms that doesn't
know what -R is?

> Please also note that on w32 you'll get (a warning and) a wrapper
> regardless, as there's no way to hardcode there.

Right, and that's fine.  Possibly the documentation should be changed
here though.  For example, change:

`-no-install'
     Link an executable OUTPUT-FILE that can't be installed and
     therefore doesn't need a wrapper script.  Useful if the program is
     only used in the build tree, e.g., for testing or generating other
     files.

into:

`-no-install'
     Declare that OUTPUT-FILE won't be installed, and therefor (on
     some platforms) can do without a wrapper script.  Useful if the
     program is only used in the build tree, e.g., for testing or
     generating other files.

/Simon