public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dclarke at blastwave dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/55293] bootstrap failure: invalid conversion from 'char**' to 'const char**' [-fpermissive]
Date: Tue, 13 Nov 2012 07:40:00 -0000	[thread overview]
Message-ID: <bug-55293-4-PItejbycmX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55293-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55293

Dennis Clarke <dclarke at blastwave dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|bootstrap                   |c

--- Comment #12 from Dennis Clarke <dclarke at blastwave dot org> 2012-11-13 07:40:05 UTC ---
(In reply to comment #11)
> > Actually I just tried this : 
> > 
> > $ pwd
> > /usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10
> > $ date -u
> > Tue Nov 13 03:37:19 GMT 2012
> > 
> > $ CC='gcc -m64 -g -mno-app-regs -mcpu=v9 -D_TS_ERRNO' \
> > > CXX='g++ -m64 -g -mno-app-regs -mcpu=v9 -D_TS_ERRNO' \
> > > ../gcc-4.7.2/configure --prefix=/usr/local/gcc4 \
> > > --build=sparc64-sun-solaris2.10 --without-gnu-as --without-gnu-ld \
> > > --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local \
> > > --with-ld=/usr/ccs/bin/ld --disable-nls --enable-threads=posix --enable-shared \
> > > --libdir=/usr/local/gcc4/lib --with-local-prefix=/usr/local/gcc4 \
> > > --with-cpu=v9 --enable-stage1-languages=c --disable-multilib \
> > > --libexecdir=/usr/local/gcc4/lib \
> > > --with-pkgversion=Blastwave.org\ Inc.\ Tues\ Nov\ 13\ 03\:37\:19\ GMT\ 2012 \
> > > --with-bugurl=http\:\/\/www.blastwave.org\/support \
> > > --enable-languages=c,c++,objc,fortran,ada --enable-bootstrap
> 
> Why on Earth are you *again* using all these flags?  Remove all the flags you
> added back to CC and CXX.  Remove --with-cpu=v9 --enable-stage1-languages=c and
> -enable-bootstrap as well.
> 
> > The end result of the long long experiment is that there is something wrong in
> > gcc 4.7.2 that make it near impossible to bootstrap.  
> > 
> > OR 
> > 
> > There is something wrong with the headers in Oracle Solaris 10 that makes it
> > impossible ( or near impossible ) to bootstrap GCC 4.7.2. 
> 
> Neither of course, people do it routinely and this works fine *if you follow
> the documented procedures*.

Just to annoy you?  No. 

I have gcc 4.7.2 bootstrapping on a few Solaris 8 servers, flawlessly. 
At least thus far. Every attempt and incantation of attempts on Solaris 10,
within or without the "documented" approach has failed. So, go easy on me. 
I have in fact, done this before. Just never on Solaris 10.


  parent reply	other threads:[~2012-11-13  7:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 21:29 [Bug c/55293] New: Attempt to bootstrap 7.7.2 on Solaris 10 Sparc fails with gcc/pretty-print.c:954:28: error: " dclarke at blastwave dot org
2012-11-12 21:49 ` [Bug c/55293] Attempt to bootstrap GCC 4.7.2 " redi at gcc dot gnu.org
2012-11-12 21:50 ` redi at gcc dot gnu.org
2012-11-12 22:07 ` dclarke at blastwave dot org
2012-11-12 22:10 ` dclarke at blastwave dot org
2012-11-12 22:44 ` dclarke at blastwave dot org
2012-11-12 23:07 ` dclarke at blastwave dot org
2012-11-12 23:58 ` [Bug bootstrap/55293] bootstrap failure: " ebotcazou at gcc dot gnu.org
2012-11-13  0:15 ` redi at gcc dot gnu.org
2012-11-13  0:21 ` ebotcazou at gcc dot gnu.org
2012-11-13  6:01 ` [Bug c/55293] " dclarke at blastwave dot org
2012-11-13  7:21 ` [Bug bootstrap/55293] " ebotcazou at gcc dot gnu.org
2012-11-13  7:40 ` dclarke at blastwave dot org [this message]
2012-11-13  8:07 ` ebotcazou at gcc dot gnu.org
2012-11-13  9:43 ` redi at gcc dot gnu.org
2012-11-14  8:34 ` mikpe at it dot uu.se
2012-11-14  8:50 ` ebotcazou at gcc dot gnu.org
2013-04-11  7:59 ` rguenth at gcc dot gnu.org
2014-06-12 13:53 ` rguenth at gcc dot gnu.org
2021-05-26 14:49 ` ebotcazou at gcc dot gnu.org

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=bug-55293-4-PItejbycmX@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).