* gcc and glibc problems
@ 2022-01-26 3:23 Bill Cunningham
2022-01-31 15:31 ` Carlos O'Donell
0 siblings, 1 reply; 2+ messages in thread
From: Bill Cunningham @ 2022-01-26 3:23 UTC (permalink / raw)
To: libc-help
I compiled a new gcc from my system gcc and glibc. Now to link a new gcc
and the glibc. I have not attached any copies of errors and will try to
explain the problems and will attach copies if necessary. But, the
config.log returns error 77.
I can compile working gcc executables by linking with the libc's newer
ld-linux-x86-64.so.2. But these executables are not truly linkable, as,
gcc -v -Wl,-Map -Wl,mapfile prog.c -o elffile
returns ld errors and still links with glibc at /usr/lib64. Now in the
path of the freshly made newer glibc that I compile.
I try to compile with this,
configure --prefix=/installdir --disable-nls --disable-werror
--with-build-time-tools=/mnt/path \
LDFLAGS='-Wl,-rpath -Wl/mnt/lib64' CC=/mnt/bin/gcc CXX=/mnt/bin/g++
LD_RUN_LIBRARY=/mnt/lib64
/mnt/lib is a soft link to /mnt/lib64; and all the library are there.
This compiles an executable that runs using some dynamic linker. Be it
that above mentioned or the elf file linker. But it is still linked to
the system libc. /usr/lib64 and not /mnt/lib64.
I hope this makes sense. IS there anything I can try?
B
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-01-31 15:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-26 3:23 gcc and glibc problems Bill Cunningham
2022-01-31 15:31 ` Carlos O'Donell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).