From: Ian Lance Taylor <iant@google.com>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gcc-help@gcc.gnu.org, ebotcazou@adacore.com,
ryan.johnson@cs.utoronto.ca, jwakely.gcc@gmail.com
Subject: Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
Date: Mon, 12 Nov 2012 17:54:00 -0000 [thread overview]
Message-ID: <CAKOQZ8xJ37xobw2phuRO8crFjsnpvg_eZMujCou2VzzGjoCcWg@mail.gmail.com> (raw)
In-Reply-To: <fb7fa594132.50a0d908@blastwave.org>
On Mon, Nov 12, 2012 at 8:10 AM, Dennis Clarke <dclarke@blastwave.org> wrote:
>
> /usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/./prev-gcc/g++ -B/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/./prev-gcc/ -B/usr/local/gcc4/sparc64-sun-solaris2.10/bin/ -nostdinc++ -B/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/prev-sparc64-sun-solaris2.10/libstdc++-v3/src/.libs -B/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/prev-sparc64-sun-solaris2.10/libstdc++-v3/libsupc++/.libs -I/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/prev-sparc64-sun-solaris2.10/libstdc++-v3/include/sparc64-sun-solaris2.10 -I/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/prev-sparc64-sun-solaris2.10/libstdc++-v3/include -I/usr/local/build/gcc-4.7.2/libstdc++-v3/libsupc++ -L/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/prev-sparc64-sun-solaris2.10/libstdc++-v3/src/.libs -L/usr/local/build/gcc-4.7.2_sparc64-sun-solaris2.10.ebotcazou/prev-sparc64-sun-solaris2.10/libstdc++-v3/libsupc++/.libs -c
> -g -O2 -DIN_GCC -fno-exceptions -fno-rtti -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.7.2/gcc -I../../gcc-4.7.2/gcc/. -I../../gcc-4.7.2/gcc/../include -I./../intl -I../../gcc-4.7.2/gcc/../libcpp/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I../../gcc-4.7.2/gcc/../libdecnumber -I../../gcc-4.7.2/gcc/../libdecnumber/dpd -I../libdecnumber -I/usr/local/include:/opt/csw/gcc4/include ../../gcc-4.7.2/gcc/pretty-print.c -o pretty-print.o
> ../../gcc-4.7.2/gcc/pretty-print.c: In function 'const char* identifier_to_locale(const char*)':
> ../../gcc-4.7.2/gcc/pretty-print.c:954:28: error: invalid conversion from 'char**' to 'const char**' [-fpermissive]
> gmake[3]: *** [pretty-print.o] Error 1
Looks a lot like http://gcc.gnu.org/PR49794 , although that is said to
have been fixed in 4.7. Other than that I don't know, but it may
suggest the people to talk to.
Ian
next prev parent reply other threads:[~2012-11-12 17:54 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 [this message]
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
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=CAKOQZ8xJ37xobw2phuRO8crFjsnpvg_eZMujCou2VzzGjoCcWg@mail.gmail.com \
--to=iant@google.com \
--cc=dclarke@blastwave.org \
--cc=ebotcazou@adacore.com \
--cc=gcc-help@gcc.gnu.org \
--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).