This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: BigInteger build problem - again
- To: Matt Welsh <mdw at CS dot Berkeley dot EDU>
- Subject: Re: BigInteger build problem - again
- From: Bryce McKinlay <bryce at albatross dot co dot nz>
- Date: Thu, 27 Apr 2000 12:52:35 +1200
- CC: java-discuss at sourceware dot cygnus dot com
- References: <200004262336.QAA02794@mnemosyne.CS.Berkeley.EDU>
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 ]