From: L A Walsh <gsuite@tlinx.org>
To: xaxazak xak <xaxazak@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Building a compiler that honors symbolic links.
Date: Thu, 7 May 2020 14:03:07 -0700 [thread overview]
Message-ID: <CALOnQv7_aQSKbHwkt76ogMHXa1g0hmamfqQq66ZTRQd32J=j9A@mail.gmail.com> (raw)
In-Reply-To: <CAOZ3qUM4o9_mbRsTepyc1qP6KGaUXLVWOZBHB3U0Sj_p3dE-hg@mail.gmail.com>
Try mounting your target onto a "make" directory using the bind feature in
mount.
On Thu, May 7, 2020 at 1:44 AM xaxazak xak via Gcc-help <
gcc-help@gcc.gnu.org> wrote:
> When I manually build GCC (via SVN trunk) or LLVM (via GIT trunk) I
> use a symbolic link (/make/) to my development folder as part of the
> destination path.
>
> Both GCC and LLVM extract the “physical” target location of this
> symlink, so their default include paths etc use the physical location,
> which starts with (/media/<HOME>/<HDD>/...) instead of just
> (/make/...).
>
> This is annoying for a few reasons:
>
> 1. I’m capturing the header information (via -H), and I want to avoid
> having <HOME> and <HDD> included in this list.
> 2. <HDD> can change.
>
> I can choose to not use the default include paths (eg -nostdinc++
> etc), and just explicitly set them when I invoke clang, but that makes
> build setup a lot more complex.
>
> Is there any way I can build GCC (and LLVM / clang if you know) so
> that it remembers my symlinks instead of expanding them?
>
>
> (NOTE: Also asked for LLVM, here:
> https://llvm.discourse.group/t/maintaining-symlinks-when-installing/955)
>
>
> Thanks,
> Simon.
>
prev parent reply other threads:[~2020-05-07 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 8:44 xaxazak xak
2020-05-07 10:43 ` Jonathan Wakely
2020-05-07 19:37 ` xaxazak xak
2020-05-07 21:03 ` L A Walsh [this message]
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='CALOnQv7_aQSKbHwkt76ogMHXa1g0hmamfqQq66ZTRQd32J=j9A@mail.gmail.com' \
--to=gsuite@tlinx.org \
--cc=gcc-help@gcc.gnu.org \
--cc=xaxazak@gmail.com \
/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).