public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/23499] [4.1 regression] libgcj/classpath create empty directory $PREFIX/share/classpath/api/
Date: Tue, 27 Sep 2005 18:21:00 -0000 [thread overview]
Message-ID: <20050927173836.3841.qmail@sourceware.org> (raw)
In-Reply-To: <20050820173142.23499.gerald@pfeifer.com>
------- Additional Comments From gerald at pfeifer dot com 2005-09-27 17:38 -------
Yes, and no. ;-)
My testing finished earlier today, and $PREFIX/share/classpath/api/ isn't
created any longer. Thanks!
Unfortunately, the parent directory $PREFIX/share/classpath/ still is created
even though it's empty.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23499
next prev parent reply other threads:[~2005-09-27 18:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 17:38 [Bug libgcj/23499] New: " gerald at pfeifer dot com
2005-08-20 18:40 ` [Bug libgcj/23499] " pinskia at gcc dot gnu dot org
2005-08-20 18:48 ` pinskia at gcc dot gnu dot org
2005-08-21 0:58 ` tromey at gcc dot gnu dot org
2005-08-22 5:15 ` mmitchel at gcc dot gnu dot org
2005-08-22 19:13 ` tromey at gcc dot gnu dot org
2005-08-22 20:02 ` cvs-commit at developer dot classpath dot org
2005-09-27 18:21 ` tromey at gcc dot gnu dot org
2005-09-27 18:21 ` gerald at pfeifer dot com [this message]
2005-09-30 20:49 ` tromey at gcc dot gnu dot org
[not found] <bug-23499-231@http.gcc.gnu.org/bugzilla/>
2005-10-05 20:06 ` pinskia at gcc dot gnu dot org
2005-10-30 23:25 ` gerald at pfeifer 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=20050927173836.3841.qmail@sourceware.org \
--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: link
Be 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).