BJ> What default defines changed between versions?

 MK> I just started using 3.x about a week or so ago.  In fact other then a 
 MK> kernel for this partition the Maximus source is the 
 MK> only thing I've compiled with it.  I am actually 
 MK> suprised that 2.95.3 couldn't handle it.  Perhaps an 
 MK> upgrade of binutils?  I might give that a try but I am 
 MK> really starting to wonder.  I'd be inclined to think 
 MK> that whatever is causing the break really ought to be 
 MK> looked at as 2.95.3 is sitting on most of the Linux 
 MK> boxes these days.  It should work.

We do need to look into what causes stuff to barf between different GCC
compiler versions.  If a newer compiler causes problems, we definately need
to fix it.  If it is an older compiler, well, we can say
"upgrade"....  I haven't kept track of the compiler version
numbers.....

It is possible that you need to re-run ./configure when changing your
development environment (compiler version, bin-utils version, etc.), since
that is the script that sets up parameters for how things are processed. 
This includes testing compiler options, etc.  So, if you didn't do that,
that may be the problem.  If re-running ./configure doesn't fix the
problem, then we may need to update ./configure scripts and/or change code
to fix the problem.

Wes had the max and squish code compiling on a few different platforms, and
possibly using C instead of GCC on some of those Unix (not Linux)
platforms.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01