This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: libtool problems while building gcc
- From: Dave Gittins <dave dot gittins at gmail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Mon, 28 Apr 2014 10:57:07 +1000
- Subject: Re: libtool problems while building gcc
- Authentication-results: sourceware.org; auth=none
- References: <CAB4NfKSfw_8h0qm9x=dg=6pu=GHp+Grs-5cCq6twGO_4FUgiYg at mail dot gmail dot com> <CAH6eHdR8DvDW4tWJ=jZLLfqagFJGNQ3D8Z4R7r=ERJ+c32iK0Q at mail dot gmail dot com>
Perfect, this is definitely what I should have been doing. I was
advised elsewhere to go for the combined builds but this sequence is
much better.
Thanks
D
On Fri, Apr 25, 2014 at 7:33 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> 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.