Glibc executables still include reference to the /tools directory [CLFS-SysV]

corbis_demon · 11-30-2016, 03:15 AM

Hi,

I just finished building my CLFS x86_64 SysV setup. Now, some programs (getent, iconv etc.) installed by Glibc still include a reference to the temporary build tools directory. Eg.:

Code:

$ ldd /usr/bin/getent

	linux-vdso.so.1 (0x00007ffdc53c8000)
	libc.so.6 => /lib/libc.so.6 (0x00007f542a286000)
	/tools/lib/ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x000055d25c4ae000)

The result is, when I try to run them, they error out:

Code:

bash: /usr/bin/getent: No such file or directory

The sanity check I performed after installing Glibc produced the expected result.

Code:

[Requesting program interpreter: /lib/ld-linux-x86-64.so.2]

Only the Glibc binaries have this problem. The rest are fine. Is there a solution to this? Thanks in advance.

business_kid · 11-30-2016, 01:31 PM

That stuff is from glibc. Glibc is built in Chapter 5, and then not for a long time. When you do the 'Adjust Toolchain' bit, what does that show?http://www.clfs.org/view/CLFS-3.0.0-...adjusting.html

corbis_demon · 12-01-2016, 11:06 AM

Quote:

Originally Posted by business_kid

When you do the 'Adjust Toolchain' bit, what does that show?

It creates the gcc specs file at the appropriate location (/tools/lib/gcc/<target-triplet>/<VERSION>), and the sanity check produces the expected output:

Code:

[Requesting program interpreter: /lib/ld-linux-x86-64.so.2]

I'm now compiling Glibc again using the current instead of the the cross-compiled one from the temp tools. I'm running into problems again, though, because I have Gold as the default linker. When using bfd as the linker, I get errors because I have ssse3/avx enabled in the CFLAGS, which I do not want to disable.

business_kid · 12-02-2016, 04:17 AM

Quote:

It creates the gcc specs file at the appropriate location (/tools/lib/gcc/<target-triplet>/<VERSION>), and the sanity check produces the expected output:

Code:

[Requesting program interpreter: /lib/ld-linux-x86-64.so.2]

If you're getting the expected output, it means it's referencing the system interpreter, which is correct. Now what remains to be checked is have you a static or chapter 5 compile lying around (which all reference /tools) or have you somehow got /tools back into the configure line subsequent to chapter 5?