public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/14315] [3.4 only]: Java compiler is not parallel make safe Date: Thu, 20 May 2004 16:06:00 -0000 [thread overview] Message-ID: <20040520160638.6735.qmail@sourceware.org> (raw) In-Reply-To: <20040227014057.14315.hjl@lucon.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-05-20 16:06 ------- Subject: Bug 14315 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-3_4-branch Changes by: hjl@gcc.gnu.org 2004-05-20 16:06:14 Modified files: gcc/java : ChangeLog jcf-write.c Log message: 2004-05-20 H.J. Lu <hongjiu.lu@intel.com> PR java/14315 Backport from mainline: 2004-03-23 Tom Tromey <tromey@redhat.com> * jcf-write.c (make_class_file_name): Don't report if mkdir failed with EEXIST. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.1315.2.15&r2=1.1315.2.16 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/java/jcf-write.c.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.140&r2=1.140.4.1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14315
next prev parent reply other threads:[~2004-05-20 16:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20040227014057.14315.hjl@lucon.org> 2004-03-23 17:49 ` [Bug java/14315] " pinskia at gcc dot gnu dot org 2004-03-23 17:54 ` cvs-commit at gcc dot gnu dot org 2004-03-23 17:55 ` tromey at gcc dot gnu dot org 2004-04-27 18:04 ` [Bug java/14315] [3.4]: " hjl at lucon dot org 2004-04-27 18:13 ` [Bug java/14315] [3.4 only]: " pinskia at gcc dot gnu dot org 2004-05-20 16:06 ` cvs-commit at gcc dot gnu dot org [this message] 2004-05-20 16:11 ` pinskia at gcc dot gnu dot 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=20040520160638.6735.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-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).