From: Dennis Clarke <dclarke@blastwave.org>
To: gcc-help@gcc.gnu.org
Cc: ebotcazou@adacore.com, ryan.johnson@cs.utoronto.ca,
iant@google.com, jwakely.gcc@gmail.com
Subject: A not so stellar result on Solaris 10
Date: Sat, 17 Nov 2012 22:02:00 -0000 [thread overview]
Message-ID: <fb5622416a8a.50a7c308@blastwave.org> (raw)
Gentlemen :
So after a pile of noises made I was ableto finally posts ome sort of result :
http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01367.html
Not exactly what I was hoping for but it seems to be a step in the right direction. Notice
that I gave up on the --disable-multilib option and did embrace the --disable-nls which allowed
stage 1 to complete.
Not too sure what to make of all those failures with g++ or gcc for that matter.
Everything else was flawless.
My builds on old old Solaris 8 are still going .. no end in sight yet.
Dennis
next reply other threads:[~2012-11-17 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 22:02 Dennis Clarke [this message]
2012-11-17 23:41 ` Eric Botcazou
2012-11-18 0:12 ` Dennis Clarke
2012-11-18 7:25 ` Eric Botcazou
2012-11-20 6:07 ` gcc 4.7.2 fails to bootstrap in stage 1 Dennis Clarke
2012-11-20 8:31 ` Eric Botcazou
2012-11-20 17:47 ` 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=fb5622416a8a.50a7c308@blastwave.org \
--to=dclarke@blastwave.org \
--cc=ebotcazou@adacore.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=jwakely.gcc@gmail.com \
--cc=ryan.johnson@cs.utoronto.ca \
/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).