public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/39279] New: [lto] - Werror in ../lto_trunk/gcc/lto/lto.c Date: Mon, 23 Feb 2009 19:07:00 -0000 [thread overview] Message-ID: <bug-39279-13830@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2390 bytes --] # cat stage_current stage2 # gcc/xgcc -v Using built-in specs. COLLECT_GCC=gcc/xgcc Target: i386-pc-solaris2.11 Configured with: ../lto_trunk/configure --prefix=/usr/local/lto --enable-languages=lto,c++ --enable-shared --disable-static --enable-multilib --with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld --with-ld=/usr/local/bin/ld --with-gmp=/usr/local --with-mpfr=/usr/local --without-ppl --with-demangler-in-ld --enable-clocale=gnu --with-system-libunwind --with-libelf=/usr/local CPPFLAGS=-I/usr/local/include Thread model: posix gcc version 4.4.0 20090218 (experimental) [lto revision 144375] (lto merged with rev 144262) /usr/share/src/lto_build/./prev-gcc/xgcc -B/usr/share/src/lto_build/./prev-gcc/ -B/usr/local/lto/i386-pc-solaris2.11/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common -DHAVE_CONFIG_H -I. -Ilto -I../../lto_trunk/gcc -I../../lto_trunk/gcc/lto -I../../lto_trunk/gcc/../include -I../../lto_trunk/gcc/../libcpp/include -I/usr/local/include -I/usr/local/include -I../../lto_trunk/gcc/../libdecnumber -I../../lto_trunk/gcc/../libdecnumber/dpd -I../libdecnumber ../../lto_trunk/gcc/lto/lto.c -o lto/lto.o cc1: warnings being treated as errors ../../lto_trunk/gcc/lto/lto.c: In function free_section_data: ../../lto_trunk/gcc/lto/lto.c:497: error: request for implicit conversion from void * to caddr_t not permitted in C++ gmake[3]: *** [lto/lto.o] Error 1 gmake[3]: Leaving directory `/usr/share/src/lto_build/gcc' gmake[2]: *** [all-stage2-gcc] Error 2 gmake[2]: Leaving directory `/usr/share/src/lto_build' gmake[1]: *** [stage2-bubble] Error 2 gmake[1]: Leaving directory `/usr/share/src/lto_build' gmake: *** [all] Error 2 Rob -- Summary: [lto] - Werror in ../lto_trunk/gcc/lto/lto.c Product: gcc Version: lto Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rob1weld at aol dot com GCC build triplet: i386-pc-solaris2.11 GCC host triplet: i386-pc-solaris2.11 GCC target triplet: i386-pc-solaris2.11 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39279
next reply other threads:[~2009-02-23 19:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-23 19:07 rob1weld at aol dot com [this message] 2009-03-09 6:40 ` [Bug lto/39279] " rob1weld at aol dot com 2009-07-09 0:14 ` bje at gcc dot gnu dot org 2009-07-15 0:49 ` bje at gcc dot gnu dot org 2009-07-17 6:44 ` rob1weld at aol dot com
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-39279-13830@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: linkBe 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).