From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dave Gittins <dave.gittins@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: libtool problems while building gcc
Date: Fri, 25 Apr 2014 09:33:00 -0000 [thread overview]
Message-ID: <CAH6eHdR8DvDW4tWJ=jZLLfqagFJGNQ3D8Z4R7r=ERJ+c32iK0Q@mail.gmail.com> (raw)
In-Reply-To: <CAB4NfKSfw_8h0qm9x=dg=6pu=GHp+Grs-5cCq6twGO_4FUgiYg@mail.gmail.com>
On 25 April 2014 04:33, Dave Gittins wrote:
> Hi,
>
> Recently I managed to build gcc 4.4.0 and 4.4.7 with binutils included
> (with some help here).
>
> Now I am trying to build gcc 4.5.4 and 4.6.4, with binutils. I keep
> getting an error:
> libtool: Version mismatch error. This is libtool 2.2.7a, but the
> libtool: definition of this LT_INIT comes from libtool 2.2.6.
>
> Here is the process I am going through:
> Untar gcc-4.5.4 source to gcc-4.5.4-src
> Copy the binutils 2.20.1a source into the same src dir but don't
> replace existing files
I think doing combined tree builds (with binutils and GCC in the same
source tree) is only guaranteed to work with the top-of-tree versions
of each, otherwise various configury files don't match.
The simplest way I know to achieve what you seem to want is to install
binutils first, separately, to $PREFIX, then configure and install GCC
to the same $PREFIX. During its configuration GCC will notice that
binutils is installed in its final destination and will be configured
to automatically use $PREFIX/bin/as and $PREFIX/bin/ld rather than the
usual versions in your $PATH.
next prev parent reply other threads:[~2014-04-25 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 3:33 Dave Gittins
2014-04-25 9:33 ` Jonathan Wakely [this message]
2014-04-28 0:57 ` Dave Gittins
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='CAH6eHdR8DvDW4tWJ=jZLLfqagFJGNQ3D8Z4R7r=ERJ+c32iK0Q@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=dave.gittins@gmail.com \
--cc=gcc-help@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).