BigInteger build problem - again

Wed Apr 26 17:51:00 GMT 2000

Matt Welsh wrote:
> Turns out this is because it was picking up an older gcj on my PATH.
>> I propose that to avoid this, running 'gcc' and 'gcj' should not
> rely on the user's PATH, but should be executed directly from the install
> target of libgcj. This should be an easy Makefile fix, right?

I kind of like the behaviour as it is, because I can easily do builds of libgcj
using different versions of gcc just by changing my path. I would like to see
libgcj's configure automatically detect incompatible versions of gcc, though (like
trying to build the cvs libgcj with an unmodified 2.95.2).
regards
 [ bryce ]