Re: environment and compiling with jikes

2002-03-08 Thread Mark Wielaard
Hi, On Fri, 2002-03-08 at 17:53, Eric Blake wrote: > Someone with a little more autoconf knowledge than me should figure out > how to make the default command-line arguments to Jikes include an > explicit -bootclasspath to override any environment variable. The > cleanest way to guarantee that J

Re: Please keep Classpath in a working state (Was: cvs commitsandjava.util.regex)

2002-03-08 Thread Eric Blake
Mark Wielaard wrote: > > It came in with this commit although the changelog entry does > not mention it, so you probably comitted from the wrong working > directory: > > 2002-03-07 Eric Blake <[EMAIL PROTECTED]> > > * java/lang/String.java: Improve Javadoc and formatting. >

Re: Please keep Classpath in a working state (Was: cvs commits and java.util.regex)

2002-03-08 Thread Wes Biggs
>>How long before this work will be finished? Would it be possible to >>create stubs from your code at the moment? If yes, then please send them >>to me and I will do it and check them in so the tree at least builds >>again. >> > > I'll check my stub classes in now. Hmm.. after reading that the

Re: Please keep Classpath in a working state (Was: cvs commits andjava.util.regex)

2002-03-08 Thread Mark Wielaard
Hi, On Fri, 2002-03-08 at 21:36, Eric Blake wrote: > But I am not planning on committing anything which will break > the build. It came in with this commit although the changelog entry does not mention it, so you probably comitted from the wrong working directory: 2002-03-07 Eric Blak

Re: Please keep Classpath in a working state (Was: cvs commits and java.util.regex)

2002-03-08 Thread John Leuner
On Fri, Mar 08, 2002 at 01:43:49PM -0800, Wes Biggs wrote: > > >>How long before this work will be finished? Would it be possible to > >>create stubs from your code at the moment? If yes, then please send them > >>to me and I will do it and check them in so the tree at least builds > >>again. > >

Re: Please keep Classpath in a working state (Was: cvs commits and java.util.regex)

2002-03-08 Thread John Leuner
> > > How should we build Classpath without regex? > > > > I think the short answer right now is that Classpath doesn't support > > regex, so those classes would have to come from rt.jar. > > Please no. Classpath is now at a point that it can be compiled with > only free tools. Please keep it t

Re: Please keep Classpath in a working state (Was: cvs commits andjava.util.regex)

2002-03-08 Thread Eric Blake
Mark Wielaard wrote: > > > Please no. Classpath is now at a point that it can be compiled with > only free tools. Please keep it that way. I think the String changes > should not have been checked in. No String changes that depend on java.util.regex were checked in. My conversation started bec

Please keep Classpath in a working state (Was: cvs commits andjava.util.regex)

2002-03-08 Thread Mark Wielaard
Hi, On Fri, 2002-03-08 at 20:15, Wes Biggs wrote: > John Leuner wrote: > >>they didn't appear in Classpath, and gave me a clean compile even though > >>I was expecting failure (because I referenced java.util.regex, which is > >>not yet in Classpath). > > > > How should we build Classpath without

Re: cvs commits and java.util.regex

2002-03-08 Thread John Leuner
> >>they didn't appear in Classpath, and gave me a clean compile even though > >>I was expecting failure (because I referenced java.util.regex, which is > >>not yet in Classpath). > > > >How should we build Classpath without regex? > > I think the short answer right now is that Classpath doesn't

Re: cvs commits and java.util.regex

2002-03-08 Thread Wes Biggs
John Leuner wrote: >>they didn't appear in Classpath, and gave me a clean compile even though >>I was expecting failure (because I referenced java.util.regex, which is >>not yet in Classpath). > > How should we build Classpath without regex? I think the short answer right now is that Classpath d

cvs commits and java.util.regex

2002-03-08 Thread John Leuner
> I ran into a problem when compiling with Jikes. I had set the > environment variable BOOTCLASSPATH to Sun's rt.jar, so that I could use > jikes as a dropin replacement to javac, without specifying -classpath, > for regular Java files (ie. not from the Classpath project). When I > back went to

environment and compiling with jikes

2002-03-08 Thread Eric Blake
I ran into a problem when compiling with Jikes. I had set the environment variable BOOTCLASSPATH to Sun's rt.jar, so that I could use jikes as a dropin replacement to javac, without specifying -classpath, for regular Java files (ie. not from the Classpath project). When I back went to compile Cl