This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG 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 Sun, Feb 10, 2013 at 12:02 PM, CT NG <crosstoolng@mrblade.de> wrote: > This helps solving the library-finding problem but it does not allow to specify the different ld.so library. If you want to use a specific runtime linker you can invoke it manually (although this doesn't help you make it transparent): $ /lib64/ld-linux-x86-64.so.2 /usr/bin/ls / bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin selinux srv sys tmp usr var I seem to think there is some way to influence which linker gets called, otherwise on a system with both 32-bit and 64-bit runtime linkers, how would it know which one to call? $ /lib/ld-linux.so.2 /usr/bin/ls /usr/bin/ls: error while loading shared libraries: /usr/bin/ls: wrong ELF class: ELFCLASS64 -- 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] |