From: Bill Cunningham <bill.cu1234@gmail.com>
To: libc-help@sourceware.org
Subject: gcc and glibc problems
Date: Tue, 25 Jan 2022 22:23:23 -0500 [thread overview]
Message-ID: <aad8a52f-f858-bbc0-bd21-99dd397db353@gmail.com> (raw)
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
next reply other threads:[~2022-01-26 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 3:23 Bill Cunningham [this message]
2022-01-31 15:31 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aad8a52f-f858-bbc0-bd21-99dd397db353@gmail.com \
--to=bill.cu1234@gmail.com \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).