public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zaniyah at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/29183] New: cc1: internal compiler error: Segmentation Fault Date: Fri, 22 Sep 2006 14:53:00 -0000 [thread overview] Message-ID: <bug-29183-13289@http.gcc.gnu.org/bugzilla/> (raw) titan sydev :: EG >make -f unix26.mak gcc -g -Wall -D -I . -I ../Common/MemMgmt -I ../Common/StringMgmt -I ../Common/DateTime -I ../Common/FileMgmt -I ../Common/OSWrapper -I ../Common/ProcessMgmt -I ../Common/ErrorLog -I ../Common/SocketBase -I ../Common/MiscMgmt -I ../Common/LinkedList ReqFile.c -c -o Unix/ReqFile.o gcc: .: linker input file unused because linking not done cc1: .: No such file or directory cc1: 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. make: *** [Unix/ReqFile.o] Error 1 FYI: titan sydev :: EG >uname -a SunOS titan 5.7 Generic_106541-34 sun4u sparc SUNW,Ultra-4 I can truss/strace it if necessary, but I'm afraid that I can't provide the source as it is for a proprietry product. -- Summary: cc1: internal compiler error: Segmentation Fault Product: gcc Version: 3.4.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: zaniyah at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29183
next reply other threads:[~2006-09-22 14:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-22 14:53 zaniyah at gmail dot com [this message] 2006-09-22 16:08 ` [Bug c/29183] " pinskia at gcc dot gnu dot org 2006-09-23 10:05 ` rguenth at gcc dot gnu dot org 2006-09-26 12:53 ` zaniyah at gmail 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-29183-13289@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).