From: Ian Lance Taylor <iant@google.com>
To: Uri Moszkowicz <uri@4refs.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Trouble building AR
Date: Tue, 18 Jun 2013 23:16:00 -0000 [thread overview]
Message-ID: <CAKOQZ8xfuHxd8bnWPDjvz4Ycm12mFz+QSo2sYkc0ufv8QF2b4w@mail.gmail.com> (raw)
In-Reply-To: <CAMJd5ARjw26rFsWyYk+me+3mCK5Tj_UjWfzaFcitCORReymNAg@mail.gmail.com>
On Tue, Jun 18, 2013 at 1:07 PM, Uri Moszkowicz <uri@4refs.com> wrote:
> I'm having trouble building GCC. I've decompressed GCC 4.7.2 source
> into a directory and binutils 2.21.1 into a directory in parallel with
> symbolic links to all subdirectories. I ran the contrib script to get
> all other dependencies and then ran GCC's configure in a parallel
> directory, following all installation instructions. It builds just
> fine but when I install it AR seems to be missing. Any idea what
> happened to it and how to get it?
>
> Looks like it's supposed to be built with binutils and I'm getting
> other tools from it like LD just not that one. There is a program
> called gcc-ar that seems to exist but not sure if it's the same tool?
> It may appear if I build binutils by itself but I'm trying to build
> them together so that I can get -flto optimization to work, as
> apparently GCC balks at using the linker plugin if they weren't built
> together.
Tell us exactly how you ran configure.
It's not clear from the above: did you build the binutils also, or did
you only build GCC?
Ian
next prev parent reply other threads:[~2013-06-18 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 20:08 Uri Moszkowicz
2013-06-18 23:16 ` Ian Lance Taylor [this message]
2013-06-19 19:10 ` Uri Moszkowicz
2013-06-19 19:25 ` Ian Lance Taylor
2013-06-19 21:21 ` Uri Moszkowicz
2013-06-19 21:38 ` Ian Lance Taylor
2013-06-19 22:04 ` Uri Moszkowicz
2013-06-19 23:06 ` Ian Lance Taylor
2013-06-21 19:19 ` Uri Moszkowicz
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=CAKOQZ8xfuHxd8bnWPDjvz4Ycm12mFz+QSo2sYkc0ufv8QF2b4w@mail.gmail.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=uri@4refs.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).