This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Date: Mon, 3 Apr 2000 18:10:56 +1000 (EST) From: greyham@research.canon.com.au (Graham Stoney) Using --rpath also helps, but again this should be unnecessary since the compiler frontend is supposed to tell the linker this kind of stuff. There are three paths involved: * The path the linker uses to find libraries which are explicitly mentioned on the command line (-L). * The path the linker uses to find shared libraries which are implicitly referenced by shared libraries already included in the link (--rpath-link). * The path the linker records in the binary to tell the dynamic linker how to find shared libraries at runtime (--rpath). See the documentation for how these options work. There is no one correct way for these options to default. Depending upon what you are doing, different actions are appropriate. So there is no simple way for the compiler frontend to tell the linker about this. Ian ------ 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] |