public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hdante at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/111084] Support configurable dynamic linker path
Date: Sun, 20 Aug 2023 21:36:26 +0000	[thread overview]
Message-ID: <bug-111084-4-dQ24fuCsEV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111084-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111084

--- Comment #3 from Henrique <hdante at gmail dot com> ---
Hello, the reason is that linux from scratch bootstraps an initial toolchain
decoupled from the host toolchain before installing the final system. The final
installation will use the correct paths. The initial toolchain, however, uses a
separate directory. The procedure is not broken, it's actually pretty clean and
not specific to linux from scratch, other toolchain builders will do the same
thing (IIRC buildroot).

Is it possible to have a configure flag for changing the dynamic linker root ?

Thanks,

  parent reply	other threads:[~2023-08-20 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 21:09 [Bug driver/111084] New: " hdante at gmail dot com
2023-08-20 21:13 ` [Bug driver/111084] " pinskia at gcc dot gnu.org
2023-08-20 21:15 ` pinskia at gcc dot gnu.org
2023-08-20 21:36 ` hdante at gmail dot com [this message]
2023-08-21  2:15 ` xry111 at gcc dot gnu.org
2023-08-21  2:17 ` pinskia at gcc dot gnu.org
2023-08-21  2:22 ` xry111 at gcc dot gnu.org

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=bug-111084-4-dQ24fuCsEV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).