public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tim dot vanholder at anubex dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/26688] New: Classpath Makefiles assume CVS source control
Date: Wed, 15 Mar 2006 08:38:00 -0000 [thread overview]
Message-ID: <bug-26688-1258@http.gcc.gnu.org/bugzilla/> (raw)
The makefiles for classpath, as included in the libjava tree, run find to
gather lists of specific files (for META-INF etc). The matched files are then
copied to the build tree.
However, the command lines used for the find invocations specifically mention
'CVS' as a directory to exclude; since gcc has switched to subversion, '.svn'
should be excluded instead.
I /think/ this only impacts the list of files in the build tree, and as such is
fairly trivial, but I suppose the files may end up being included in some jar
file too.
--
Summary: Classpath Makefiles assume CVS source control
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tim dot vanholder at anubex dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26688
next reply other threads:[~2006-03-15 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 8:38 tim dot vanholder at anubex dot com [this message]
2006-03-15 19:45 ` [Bug libgcj/26688] " tromey at gcc dot gnu dot org
2006-03-15 23:00 ` pinskia at gcc dot gnu dot org
2006-03-16 0:19 ` [Bug classpath/26688] " tromey at gcc dot gnu dot org
2006-03-16 1:54 ` tromey at gcc dot gnu dot org
2006-03-16 1:58 ` tromey at gcc dot gnu dot org
2006-03-16 1:59 ` tromey at gcc dot gnu dot org
2006-04-27 12:13 ` gnu_andrew at member dot fsf 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=bug-26688-1258@http.gcc.gnu.org/bugzilla/ \
--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: 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).