From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Bill Cunningham <bill.cu1234@gmail.com>
Cc: gcc-help@gnu.org
Subject: Re: Native build that hopefully works!!
Date: Mon, 6 Dec 2021 11:42:23 +0000 [thread overview]
Message-ID: <CAH6eHdTh55imeP0u5WHocOxip0T_pubDmWNKL96XKf9i17VK2g@mail.gmail.com> (raw)
In-Reply-To: <08040eb8-5f5c-c21a-eb47-83d57e8b27d3@gmail.com>
On Sun, 5 Dec 2021 at 22:52, Bill Cunningham via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> I just wanted to share what I have been working on. I have of course my
> system gcc and binutils. I compiled a binutils for this new test
> compiler, which seemed to compile. This is all a native build. I used
> the switch --with-build-time-tools and set that to the directory with
> the new binutils. The makefile wanted a path for headers including
> stdio.h, so I created a soft link to the system compiler's headers. I
> would like to have a separate glibc, but that's another topic. Two
> compilers is what really matters.
>
> I used also --disable-bootstrap and disabled multilib and nls. So I
> believe this gcc is using some symbols from the system compiler and the
> binutils are too. I suppose this really doesn't matter. So changing the
> environment variables should let me be able to use this compiler.
If that's all you've been trying to achieve, it's trivial.
Configure binutils with --prefix=$SOMEWHERE then make && make install.
Configure gcc with --prefix=$SOMEWHERE then make && make install.
Just use the same $SOMEWHERE for binutils and gcc.
Then you can just run $SOMEWHERE/bin/gcc to use it, or add
$SOMEWHERE/bin to the start of your PATH to make it the default.
prev parent reply other threads:[~2021-12-06 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 22:44 Bill Cunningham
2021-12-06 11:42 ` Jonathan Wakely [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=CAH6eHdTh55imeP0u5WHocOxip0T_pubDmWNKL96XKf9i17VK2g@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=bill.cu1234@gmail.com \
--cc=gcc-help@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).