Re: build update

[Brian Jones]

Mark Wielaard <address@hidden> writes:

> Hi.
> 
> On Fri, Oct 26, 2001 at 11:17:26PM -0400, Brian Jones wrote:
> > Jeff Sturm <address@hidden> writes:
> > 
> > > On 26 Oct 2001, Tom Tromey wrote:
> > > > Between 3.0 and 3.1, Per changed gcj so that it can compile multiple
> > > > .java files to .class files at once.
> > > 
> > > 3.0.2 can as well, and maybe earlier... I don't remember exactly when Per
> > > added that feature.
> > 
> > Thanks, I'll upgrade to the latest 3.0.x version soon.
>
> You should. It is not as fast as jikes but even on my 300 Mhz machine it
> takes less then a minute to compile Classpath completely to bytecode.
> (jikes takes 
> 
> I finally found a way to get gcj to compile Classpath with our build
> scripts. You have to make sure that no classes are defined twice on the
> command lince. So I changed the gen-classlist script to only look in
> the srcdir for java files and to get the gnu/classpath/Configuration.java
> file explicitly from the builddir. (You have add it to the standard.omit
> list in case you configure in the srcdir.) 

Well, there is the distinct possibility that we need to generate more
classes than just Configuration.java so I'd rather not single it out.

> And gcj goes crazy when it finds classes on its classpath that are
> also on its commandline (somehow it gets confused because it cannot
> see that ../X.java is the same as ./../X.java).  

Sounds like a bug.

> But if you don't give it any classpath options at all then it
> compiles just fine. (I also made sure that all needed files are
> actually compiled by changing standard.omit to include some AWT
> files that have a different definition in Claspath from the one in
> libgcj.jar. Already committed.)
> 
> Attached is a diff against your patch (and standard.omit against CVS).
> Could you include these if you commit your build changes?

I'll take a look.
 
-- 
Brian Jones <address@hidden>