This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hi all, I'm trying to find out what shared libraries are used by an executable from my development host (namely, I develop on a i586-linux for arm-linux). After some research, I found that ldd is part of libtool (somehow I expected it to be part of binutils, but anyway). However, compiling libtool isn't has straightforward as I thought, I think I mix up who is host and who is target.. Or maybe ldd can't work at all like that? I think it should. Anyway, I configure libtool as follow: configure --host=arm-linux --build=i586-linux --target=i586-linux --prefix=$prefix and the produced ldd works (so it is compiled for i586), tries to run $prefix/$target/lib/ld-linux.so.2 which, well, fails because it's an arm library. So, my questions: - Has anyone already compiled/used libtool for that purpose? How do you tell it that it works in cross-compiling environment? - Is there another way of doing it? (I can't find an option to ld to dump shared libraries, but maybe there is?) Thanks! Yves ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |