That's what I don't understand. I do have a ranlib binary and it is named
by the cross-tools environment that I've been given. For some reason it's
not able to find it though when running make install and I don't know how
that happens.
On Wed, May 13, 2015 at 10:10 PM, Bob Friesenhahn <
bfrie...@
On Wed, 13 May 2015, Lane wrote:
arm-blues-linux-gnueabi-libtool: install: chmod 644
/opt/blues/lib/libbl_parsers.a
arm-blues-linux-gnueabi-libtool: install: arm-blues-linux-gnueabi-ranlib
/opt/blues/lib/libbl_parsers.a
../../../arm-blues-linux-gnueabi-libtool: line 1104:
arm-blues-linux-gnuea
I hope this is the right list to ask for libtool help. If not, please
let me know.
I have an app that uses autotools and it works just fine on x86_64.
However, when cross-compiling for arm, I am able to configure, make
(successfully), but then make install is a problem and I was hop
Bob Friesenhahn writes:
> On Tue, 12 May 2015, Alberto Luaces wrote:
>
>> Hello,
>>
>> in an autoconf+automake+libtool C++ project containing only one program,
>> I want to run the executable before installing it.
>>
>> Reading the manual I thought that it could be done with
>>
>> libtool --mode=e
