From: Gary Oblock <gary@amperecomputing.com>
To: Alan Modra <amodra@gmail.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Installation question
Date: Thu, 25 Feb 2021 19:40:21 +0000 [thread overview]
Message-ID: <BYAPR01MB5464E0CD335D6D6778BEE561C69E9@BYAPR01MB5464.prod.exchangelabs.com> (raw)
In-Reply-To: <20210224233919.GP6042@bubble.grove.modra.org>
Alan,
Actually, building gcc second seems to result in gcc cleaning out
the binutils content from the install directory!
Does anybody out there know how I'd go about debugging the
linker myself? I ask this because the one who tried to help
can't seem to duplicate the problem on their machine...
Gary
________________________________
From: Alan Modra <amodra@gmail.com>
Sent: Wednesday, February 24, 2021 3:39 PM
To: Gary Oblock <gary@amperecomputing.com>
Cc: binutils@sourceware.org <binutils@sourceware.org>
Subject: Re: Installation question
[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]
It is better to build and install binutils first, so that the gcc
configure sees an up-to-date assembler and linker. New gcc features
might not be enabled otherwise.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2021-02-25 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 21:07 Gary Oblock
2021-02-23 22:50 ` Albert Chin
2021-02-24 1:28 ` Alan Modra
2021-02-24 6:16 ` Gary Oblock
2021-02-24 23:39 ` Alan Modra
2021-02-25 19:40 ` Gary Oblock [this message]
2021-02-26 11:57 ` Alan Modra
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=BYAPR01MB5464E0CD335D6D6778BEE561C69E9@BYAPR01MB5464.prod.exchangelabs.com \
--to=gary@amperecomputing.com \
--cc=amodra@gmail.com \
--cc=binutils@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).