This is the mail archive of the crossgcc@sourceware.org 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] |
Other format: | [Raw text] |
On Mon, 2008-11-03 at 10:02 +0000, Michael Abbott wrote: > So: any sensible thoughts on this? I'm tempted to try building a > dynamically linked ldconfig... I used to have some patches to build a dynamically linked ldconfig for glibc 2.3 or so, and the resulting binary always seemed to work just fine. Those patches have become somewhat bit-rotten since and don't apply to newer versions but I don't think there is any reason why you couldn't do the same thing with a modern glibc. However, as you say, it is not strictly necessary to have ldconfig at all and more recently this is what I have been doing for embedded cases. You can cut down the number of directories that ld.so needs to search by turning off hwcap support, removing all extraneous entries from ld.so.conf, and coalescing your libraries into fewer directories (for example, if you still have /usr/X11R6/lib, move those libraries into /usr/lib and eliminate the search in /usr/X11R6). For most systems it should be straightforward to just search /lib and /usr/lib, and with a bit of extra effort I think you could get down to just searching /lib for all libraries. p. -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |