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...@simple.dallas.tx.us> wrote: > 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-gnueabi-ranlib: command not found >> Makefile:395: recipe for target 'install-libLTLIBRARIES' failed >> >> Any thoughts on how to proceed? >> > > 1. Assuming that you want to make progress with your work. > > 2. Assuming that your other cross-tools are named prefixed with > 'arm-blues-linux-gnueabi-'. > > 3. Assuming that ranlib is not actually necessary. > > You could change to the directory where the other cross-tools are and do > > ln -s /bin/true arm-blues-linux-gnueabi-ranlib > > Altnerately, you could find a correct ranlib binary and make sure that it > is named appropriately. > > Bob > -- > Bob Friesenhahn > bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ >
_______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
