public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Danny Smith <dannysmith@clear.net.nz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/5620: [3.1] GCC -save-temps foo.c fails to build foo.o Date: Tue, 10 Dec 2002 17:16:00 -0000 [thread overview] Message-ID: <20021211011601.30045.qmail@sources.redhat.com> (raw) The following reply was made to PR other/5620; it has been noted by GNATS. From: Danny Smith <dannysmith@clear.net.nz> To: bangerth@dealii.org, danny_r_smith_2001@yahoo.co.nz, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/5620: [3.1] GCC -save-temps foo.c fails to build foo.o Date: Wed, 11 Dec 2002 01:04:56 +0000 ----- Original Message ----- From: <bangerth@dealii.org> To: <danny_r_smith_2001@yahoo.co.nz>; <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <nobody@gcc.gnu.org> Sent: Wednesday, 11 December 2002 01:01 Subject: Re: other/5620: [3.1] GCC -save-temps foo.c fails to build foo.o > Synopsis: [3.1] GCC -save-temps foo.c fails to build foo.o > > State-Changed-From-To: open->analyzed > State-Changed-By: bangerth > State-Changed-When: Tue Dec 10 17:01:11 2002 > State-Changed-Why: > The patch you mention has not been reverted, as far as I can > tell. Can you say whether the problem persists with > present mainline? Yes. The bug is host (mingw) specific and is due to the msvcrt implementation of stat. I have a patch that fixes for host, but have been putting off submitting because it is so ugly I'll work on it. Danny > > Thanks > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=g cc&pr=5620
next reply other threads:[~2002-12-11 1:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-10 17:16 Danny Smith [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-13 1:16 Dara Hazeghi 2002-12-10 17:16 Wolfgang Bangerth 2002-12-10 17:01 bangerth 2002-06-09 12:56 hp 2002-05-11 10:17 rodrigc 2002-02-06 18:06 danny_r_smith_2001
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=20021211011601.30045.qmail@sources.redhat.com \ --to=dannysmith@clear.net.nz \ --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).