This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
- From: Cyd Haselton <chaselton 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: Tue, 18 Nov 2014 14:05:25 -0600
- Subject: Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
- Authentication-results: sourceware.org; auth=none
- References: <CAHu5PrZzf7wa1Y1mWjyb_XrLkksCw04PLRKQNNBvy-tsogGWdw at mail dot gmail dot com> <alpine dot DEB dot 2 dot 11 dot 1411162341210 dot 1590 at laptop-mg dot saclay dot inria dot fr> <CAHu5Prb3OUk3SyDkwzzJ7NxVvh=2uNYeV4ch2O4Q1moACS-N=w at mail dot gmail dot com> <CAH6eHdS--Rd8WKedsCpwFyVF__xbaKda6FQLVxpkUM1maMogDw at mail dot gmail dot com>
On Sun, Nov 16, 2014 at 7:38 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 16 November 2014 23:51, Cyd Haselton wrote:
*snip*
>> Additionally, a bootstrap guide I read suggested bootstrapping
>> versions at max, one version level later.
>
> I'm not sure what that means, but if the authors intended to say don't
> try to build 4.9.1 with 4.8.0 they're giving bad advice, and even if
> you want to follow it, if you don't make the mistake of staring with
> 4.8.0 then you're not forced to use 4.9.0
Unfortunately, 4.9.1 exhibits the same behavior in the same part of
the build process (what I think is the target libgcc linking, but I
could very well be wrong).
Attempt 4.9.2 or troubleshoot 4.9.1?