public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "julius at zgod dot cjb dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/25912] Problem compiling Asterisk 1.2.2 with Debian 3.1 (Sarge) gcc (3.3.5 (Debian 1:3.3.5-13)) Date: Sat, 04 Feb 2006 23:50:00 -0000 [thread overview] Message-ID: <20060204235021.18466.qmail@sourceware.org> (raw) In-Reply-To: <bug-25912-12055@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from julius at zgod dot cjb dot net 2006-02-04 23:50 ------- I just tried: env LANG=C gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i586 -fomit-frame-pointer -c -o channel.o channel.c and then make which seems to get further now, but stops again with: gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i586 -fomit-frame-pointer -c -o rtp.o rtp.c rtp.c: In function `ast_rtp_bridge': rtp.c:1741: internal compiler error: Segmentatie fout Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. For Debian GNU/Linux specific bug reporting instructions, see <URL:file:///usr/share/doc/gcc-3.3/README.Bugs>. make: *** [rtp.o] Fout 1 which the env LANG=C gcc trick, it again seems to get further. Then I again got an error for ast_expr2.c. Same trick allowed it to go further. With channels/chan_sip.c, I got the error too, but env LANG=C gcc gave me: julius@montenegro:~/asterisk-1.2.2/channels$ env LANG=C gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i586 -fomit-frame-pointer -Wno-missing-prototypes -Wno-missing-declarations -DZAPATA_PRI -DCRYPTO -fPIC -c -o chan_sip.o chan_sip.c chan_sip.c: In function `get_destination': chan_sip.c:6497: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. For Debian GNU/Linux specific bug reporting instructions, see <URL:file:///usr/share/doc/gcc-3.3/README.Bugs>. I hope am I doing the correct thing with your suggestion. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25912
next prev parent reply other threads:[~2006-02-04 23:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-22 17:04 [Bug c/25912] New: " julius at zgod dot cjb dot net 2006-01-22 17:41 ` [Bug c/25912] " julius at zgod dot cjb dot net 2006-01-24 13:41 ` [Bug middle-end/25912] " pinskia at gcc dot gnu dot org 2006-02-04 23:50 ` julius at zgod dot cjb dot net [this message] 2006-02-18 20:37 ` julius at zgod dot cjb dot net [not found] <bug-25912-4@http.gcc.gnu.org/bugzilla/> 2012-02-01 20:12 ` pinskia 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=20060204235021.18466.qmail@sourceware.org \ --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).