Databases
StackOverflow2013
Postsdbo
POHow to build the elf interpreter (ld-linux.so.2/ld-2.17.so) as static library?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to build the elf interpreter (ld-linux.so.2/ld-2.17.so) as static library?
    primarykey
    data
    text
    <p>I apologize if my question is not precise because I don't have a lot of Linux related experience. I'm currently building a Linux from scratch (mostly following the guide at linuxfromscratch.org version 7.3). I ran into the following problem: when I build an executable it gets a hardcoded path to something called ELF interpreter.</p> <pre><code>readelf -l program </code></pre> <p>shows something like</p> <pre><code>[Requesting program interpreter: /lib/ld-linux.so.2] </code></pre> <p>I traced this library ld-linux-so.2 to be part of glibc. I am not very happy with this behaviour because it makes the binary very unportable - if I change the location of /lib/ld-linux.so.2 the executable no longer works and the only "fix" I found is to use the patchelf utility from NixOS to change the hardcoded path to another hardcoded path. For this reason I would like to link against a static version of the ld library but such is not produced. And so this is my question, could you please explain how could I build glibc so that it will produce a static version of ld-linux.so.2 which I could later link to my executables. I don't fully understand what this ld library does, but I assume this is the part that loads other dynamic libraries (or at least glibc.so). I would like to link my executables dynamically, but I would like the dynamic linker itself to be statically built into them, so they would not depend on hardcoded paths. Or alternatively I would like to be able to set the path to the interpreter with environment variable similar to LD_LIBRARY_PATH, maybe LD_INTERPRETER_PATH. The goal is to be able to produce portable binaries, that would run on any platform with the same ABI no matter what the directory structure is.</p> <p>Some background that may be relevant: I'm using Slackware 14 x86 to build i686 compiler toolchain, so overall it is all x86 host and target. I am using glibc 2.17 and gcc 4.7.x.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USbobef
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to build the elf interpreter (ld-linux.so.2/ld-2.17.so) as static library?
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. POHow to build the elf interpreter (ld-linux.so.2/ld-2.17.so) as static library?
      1. USWakan Tanka
      1. VTFavorite
    1. COI believe it is a bad idea to change the ELF program interpreter (unless you are a Linux &  binutils guru); it is built with Glibc. You could try something else (e.g. [MUSL-Libc](http://musl-libc.org)...). Why do you want to change it? To what dynamic loader?? If you don't want to depend on its location and existence (which is a bad idea), give up dynamic linking and have only statically linked programs. And the dynamic linker `/lib/ld-linux.so.2` is statically built (but still a shared library, not using any external library except the kernel provided VDSO).
      singulars
      1. POHow to build the elf interpreter (ld-linux.so.2/ld-2.17.so) as static library?
      1. USBasile Starynkevitch
    2. CODynamic linking is meant to be dynamic, not to depend on static location. This [hardwired] approach is completely wrong. I want to fix it in my system. And the solution is easy I'm just not familiar enough with all the aspects to fix it myself.
      singulars
      1. POHow to build the elf interpreter (ld-linux.so.2/ld-2.17.so) as static library?
      1. USbobef
    3. COThen, patch the kernel to fit your needs. Then you'll have to patch the toolchain (compiler & linker) to obey them. Indeed, all this is free software and you can improve it.
      singulars
      1. POHow to build the elf interpreter (ld-linux.so.2/ld-2.17.so) as static library?
      1. USBasile Starynkevitch
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload