public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6488: GCC Release 3.0.4 fails with Segmentation fault when compiling the vmware driver which is included in XFree86 4.2.0 Release. Date: Mon, 07 Apr 2003 14:36:00 -0000 [thread overview] Message-ID: <20030407143601.7553.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6488; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: Matthew Williams <mw01@uow.edu.au> Cc: gcc-gnats@gcc.gnu.org Subject: Re: c/6488: GCC Release 3.0.4 fails with Segmentation fault when compiling the vmware driver which is included in XFree86 4.2.0 Release. Date: Mon, 7 Apr 2003 09:27:03 -0500 (CDT) > The Alpha machine wasn't mine. It belonged to a bloke in Melbourne who I was > working for. I caught up with him and he's told me that the HDD in the alpha > has died and it will be awhile before he replaces it. If he gets the alpha > up and running again I will try again and see if it still fails. OK, thanks. > What > options do I pass to configure in order to produce preprocessed sources? None to configure, but use -save-temps when call gcc/g++. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ices.utexas.edu www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2003-04-07 14:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-07 14:36 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-07 2:34 bangerth 2002-04-27 7:56 mw01
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=20030407143601.7553.qmail@sources.redhat.com \ --to=bangerth@ices.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).