Re: libjava regressions in r140713

2008-09-30 Thread Andreas Tobler
Andreas Tobler wrote: Hi Peter, Peter O'Gorman wrote: Andreas Tobler wrote: Jack Howarth wrote: On i686-apple-darwin9, I am seeing massive regressions in the libjava testsuite in revision 140713 compared to my previous test on 20080925. Since the libtool updates went in (which would see t

Re: libjava regressions in r140713

2008-09-27 Thread Andreas Tobler
Hi Peter, Peter O'Gorman wrote: Andreas Tobler wrote: Jack Howarth wrote: On i686-apple-darwin9, I am seeing massive regressions in the libjava testsuite in revision 140713 compared to my previous test on 20080925. Since the libtool updates went in (which would see the likely culprit), we w

Re: libjava regressions in r140713

2008-09-27 Thread Peter O'Gorman
Andreas Tobler wrote: > Jack Howarth wrote: >>On i686-apple-darwin9, I am seeing massive regressions in the libjava >> testsuite in revision 140713 compared to my previous test on 20080925. >> Since the libtool updates went in (which would see the likely culprit), >> we went from zero to 835 un

Re: libjava regressions in r140713

2008-09-27 Thread Andreas Tobler
Jack Howarth wrote: On i686-apple-darwin9, I am seeing massive regressions in the libjava testsuite in revision 140713 compared to my previous test on 20080925. Since the libtool updates went in (which would see the likely culprit), we went from zero to 835 unexpected failures. http://gcc.gnu

RE: libjava regressions in r140713

2008-09-27 Thread Jack Howarth
These new libjava failures all seem to be of the form... set_ld_library_path_env_vars: ld_library_path=.:/sw/src/fink.build/gcc44-4.3.999-20080926/darwin_objdir/i686-apple-darwin9/./libjava/.libs Executing on host: /sw/src/fink.build/gcc44-4.3.999-20080926/darwin_objdir/i686-apple-darwin9/lib

libjava regressions in r140713

2008-09-27 Thread Jack Howarth
On i686-apple-darwin9, I am seeing massive regressions in the libjava testsuite in revision 140713 compared to my previous test on 20080925. Since the libtool updates went in (which would see the likely culprit), we went from zero to 835 unexpected failures. http://gcc.gnu.org/ml/gcc-testresult