Re: Problem

[Mark Mitchell <mark at codesourcery dot com>]

>>>>> "Alexandre" == Alexandre Petit-Bianco <apbianco@cygnus.com> writes:

    Alexandre> Mark Mitchell writes:

    >> I'm having trouble building libgcj, and I'm not sure whether I
    >> broke it or it was already broken.

OK, the test problems are coming from a loop in libtool:

+ trap  rm -f Case.o .libs/Case.o Case.lo Case.loT -g.o -g.o.lock; exit 1 1 2 15
+ test yes = yes
+ ln /mnt/u2/mitchell/dev/gcc-3/objdir/i686-pc-linux-gnu/libjava/testsuite/../libtool -g.o.lock
+ : Waiting for -g.o.lock to be removed
+ sleep 2
+ ln /mnt/u2/mitchell/dev/gcc-3/objdir/i686-pc-linux-gnu/libjava/testsuite/../libtool -g.o.lock
+ : Waiting for -g.o.lock to be removed
+ sleep 2
+ ln /mnt/u2/mitchell/dev/gcc-3/objdir/i686-pc-linux-gnu/libjava/testsuite/../libtool -g.o.lock

What's that about?  The `ln' command is bogus; `ln' treats `-g.o.lock'
as an option, not a file name.

I'm going to assume this has nothing to do with me, since it seems to
be in the test script stuff itself.

Can you confirm?

Also, if the testsuite is broken, we should turn it off for now;
otherwise, everyone will be confused, and it takes forever to get each
of these tests to time out.

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com