This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: warning about classpath import
- From: Tom Tromey <tromey at redhat dot com>
- To: "Dave Korn" <dave dot korn at artimi dot com>
- Cc: "'GCJ Hackers'" <java at gcc dot gnu dot org>, "'GCC Mailing List'" <gcc at gcc dot gnu dot org>
- Date: 22 Sep 2005 08:24:53 -0600
- Subject: Re: warning about classpath import
- References: <SERRANOtgLzhVOJwnzs0000019c@SERRANO.CAM.ARTIMI.COM>
- Reply-to: tromey at redhat dot com
>>>>> "Dave" == Dave Korn <dave.korn@artimi.com> writes:
>> I'm finally ready to do another classpath import, and near the last
>> minute I realized that the import may temporarily break the build, due
>> to an unfortunate interaction between the classpath Makefile and the
>> way cvs import works. FWIW I'd prefer to continue using cvs import
>> since it does seem to help the process a little.
Dave> Is this anything that could be fixed with a "cvs admin -b"
Dave> immediately after the import?
I've never used that, but based on the manual, I don't think so.
The problem is that files that are new on the vendor branch will show
up on HEAD immediately, and classpath will try to build them.
Tom