From: "François Bissey" <francois.bissey@canterbury.ac.nz>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Restructuring the bootstrap (or: getting rid of gcc 4.2)
Date: Tue, 04 Feb 2014 09:35:36 +1300 [thread overview]
Message-ID: <1914805.X6e3JF6jAN@qcd-nzi3> (raw)
In-Reply-To: <201402022141.13754.redlizard@gentoo.org>
On Sun, 02 Feb 2014 21:41:13 Ruud Koolen wrote:
> On Sunday 02 February 2014 20:55:04 Francois Bissey wrote:
> > On 3/02/2014, at 6:34, Ruud Koolen <redlizard@gentoo.org> wrote:
> > >But gcc and friends are specifically designed to be buildable on any
> > >ridiculous old system, and the use of other tools hasn't changed between
> > >
> > > my bootstrap process and the current one. Again, can you elaborate and
> > > give a concrete example?
> >
> > Ridiculously old systems? AIX will come with gcc 4.2 if you are lucky. I
> > never managed to compile a recent gcc with an IBM compiler.
>
> Interesting; this should be possible. I'll see whether I can test this.
>
The gcc page on the subject may be out of date. May be you can bootstrap
gcc-4.2 with xlc but I never tried that since I had it already.
> > gcc 4.8 has raised the bar significantly in terms of how new your compiler
> > needs to be.
>
> That is a very good point. My plans and tests so far were in terms of gcc
> 4.7, but gcc 4.8 and later require a C++ compiler to build, which is not
> something we want to rely on. Thus, upgrading the bootstrap compiler would
> upgrade to 4.7 only and no further, and I don't see a way to change that in
> the future.
> > In the case of AIX I had to build and use a more recent gcc (4.6.x or
> > 4.7.x
> > I don’t remember) before being able to gcc 4.8.1. I also manage some SLES
> > 11SP1 ppc64 boxes, gcc 4.8.1 will not build with the gcc 4.3.4 that come
> > as
> > default. I don’t think it even compile with the alternate gcc 4.5
> > toolchain
> > they provide.
> >
> > François
>
> What about gcc 4.7?
>
gcc-4.7 is not provided by SLES 11SP1 you may be thinking of SP2 or SP3.
Francois
next prev parent reply other threads:[~2014-02-03 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 2:31 [gentoo-alt] Restructuring the bootstrap (or: getting rid of gcc 4.2) Ruud Koolen
2014-02-02 9:04 ` Fabian Groffen
2014-02-02 17:34 ` Ruud Koolen
2014-02-02 19:35 ` Fabian Groffen
2014-02-03 9:16 ` Fabian Groffen
2014-02-03 9:43 ` heroxbd
2014-02-03 9:48 ` Fabian Groffen
2014-02-03 9:52 ` Ruud Koolen
2014-02-05 23:55 ` Ruud Koolen
2014-02-06 0:03 ` heroxbd
2014-02-06 8:37 ` Fabian Groffen
2014-02-02 19:55 ` Francois Bissey
2014-02-02 20:41 ` Ruud Koolen
2014-02-03 20:35 ` François Bissey [this message]
2014-02-02 20:12 ` Jeremy Olexa
2014-02-02 20:24 ` Ruud Koolen
2014-02-03 13:11 ` Michael Haubenwallner
2014-02-06 0:03 ` Ruud Koolen
2014-02-03 1:23 ` heroxbd
2014-02-03 1:57 ` Ruud Koolen
2014-02-03 9:40 ` heroxbd
2014-02-03 9:44 ` Fabian Groffen
2014-04-28 4:52 ` Ruud Koolen
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=1914805.X6e3JF6jAN@qcd-nzi3 \
--to=francois.bissey@canterbury.ac.nz \
--cc=gentoo-alt@lists.gentoo.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