public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@gcc.gnu.org To: tromey@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libgcj/2338 Date: Wed, 21 Mar 2001 08:46:00 -0000 [thread overview] Message-ID: <20010321164602.3957.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libgcj/2338; it has been noted by GNATS. From: tromey@gcc.gnu.org To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, pedro@vis.ethz.ch, tromey@gcc.gnu.org Cc: Subject: Re: libgcj/2338 Date: 21 Mar 2001 16:42:29 -0000 Synopsis: RandomAccessFile does not create the file if not found Responsible-Changed-From-To: unassigned->tromey Responsible-Changed-By: tromey Responsible-Changed-When: Wed Mar 21 08:42:29 2001 Responsible-Changed-Why: I'm fixing it. State-Changed-From-To: open->analyzed State-Changed-By: tromey State-Changed-When: Wed Mar 21 08:42:29 2001 State-Changed-Why: I believe the correct fix is to add O_CREAT to the O_RDWR case in natFileDescriptorPosix.cc. I'm testing the fix. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2338&database=gcc
next reply other threads:[~2001-03-21 8:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-03-21 8:46 tromey [this message] 2001-03-21 9:26 libgcj/2338 tromey 2001-03-21 9:26 libgcj/2338 tromey 2001-03-21 9:26 libgcj/2338 tromey
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=20010321164602.3957.qmail@sourceware.cygnus.com \ --to=tromey@gcc.gnu.org \ --cc=gcc-prs@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).