public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
	       Ian Lance Taylor <iant@google.com>,
	gcc-help@gcc.gnu.org,        ebotcazou@adacore.com
Subject: Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
Date: Mon, 12 Nov 2012 21:41:00 -0000	[thread overview]
Message-ID: <50A16CF5.4080609@cs.utoronto.ca> (raw)
In-Reply-To: <fb50f92518ae.50a124b8@blastwave.org>

On 12/11/2012 4:32 PM, Dennis Clarke wrote:
>
> ----- Original Message -----
> From: Jonathan Wakely <jwakely.gcc@gmail.com>
> Date: Monday, November 12, 2012 4:26 pm
> Subject: Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
> To: Dennis Clarke <dclarke@blastwave.org>
> Cc: Ryan Johnson <ryan.johnson@cs.utoronto.ca>, Ian Lance Taylor <iant@google.com>, gcc-help@gcc.gnu.org, ebotcazou@adacore.com
>
>
>> On 12 November 2012 21:20, Dennis Clarke wrote:
>>>> I'm still really unclear on why you're having so much trouble with
>>>> this.
>>>> Have you tried bootstrapping with SunCC like I did? Granted, I'm only
>>>> on
>>>> 5.9, but if newer versions fall down that's Oracle's fault, not gcc's.
>>> Since this is a purely gcc 4.7.2 bootstrapped with gcc 4.5.1 as the
>> compiler then it would be
>>> entirely in GCC land and not Oracle.
>> Except that the system headers which declare the problem function come
>> from Oracle.  And that doesn't answer the question.
> No .. I have gone digging to see what is going on in there but it is deep, wide and dark.
>
> I did file a bug report :
>
>      http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55293
>
> I hope I don't have to go fire up my old Solaris 8 server but, it did always result in a good looking GCC bootstrap.
You still didn't say why starting with the Solaris compiler is so 
undesirable... you do realize that the gcc you finally end up with 
(stage 3) will have been built by a gcc (stage 2) that was itself built 
by the gcc (stage 1) produced by suncc, right? Bootstrapping a separate 
version of gcc yourself just to build that stage 1 gcc with adds extra 
(and painful and unnecessary) steps to the process.

In the time you've spent writing these emails, a sunc-based bootstrap 
could have completed several times, modulo those funky CFLAGS you added. 
Heck, you could have bootstrapped 4.7.2 and then used *that* to 
bootstrap a "clean" 4.7.2 in the time these emails have taken so far.

  reply	other threads:[~2012-11-12 21:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 16:10 Dennis Clarke
2012-11-12 16:53 ` Ryan Johnson
2012-11-12 17:09   ` Dennis Clarke
2012-11-12 17:54 ` Ian Lance Taylor
2012-11-12 21:00   ` Dennis Clarke
2012-11-12 21:17     ` Ryan Johnson
2012-11-12 21:20       ` Dennis Clarke
2012-11-12 21:26         ` Jonathan Wakely
2012-11-12 21:33           ` Dennis Clarke
2012-11-12 21:41             ` Ryan Johnson [this message]
2012-11-12 21:57               ` Dennis Clarke
2012-11-12 22:13                 ` Jonathan Wakely
2012-11-12 22:22                   ` Dennis Clarke
2012-11-12 22:32                     ` Jonathan Wakely
2012-11-12 22:37                       ` Dennis Clarke
2012-11-12 22:49                         ` Jonathan Wakely
2012-11-12 22:49                           ` Jonathan Wakely
2012-11-12 22:55                             ` Dennis Clarke
2012-11-12 23:26                               ` Jonathan Wakely
2012-11-15  1:01                                 ` Dennis Clarke
2012-11-12 23:04                             ` Dennis Clarke
2012-11-12 23:17                     ` Ryan Johnson
2012-11-12 23:19                       ` Dennis Clarke
2012-11-12 23:15                   ` Ryan Johnson
2012-11-12 23:17                     ` Dennis Clarke
2012-11-12 23:25                       ` Ryan Johnson
2012-11-12 21:29       ` Marc Glisse
2012-11-12 21:34         ` Ryan Johnson
2012-11-12 21:36         ` Dennis Clarke

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=50A16CF5.4080609@cs.utoronto.ca \
    --to=ryan.johnson@cs.utoronto.ca \
    --cc=dclarke@blastwave.org \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=jwakely.gcc@gmail.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).