Re: sbcl on linux/x86

Raymond Toy wrote:
> 
> However, configure fails later saying it can't build something with
> Fortran.  I tracked it down to the fact that configure builds a test
> program like
> 
>     int MAIN () { return 1; }
> 
>     int main () { return 0; }
> 
> and expects that to return 1 if MAIN is the correct name for the
> Fortran MAIN subprogram.  Unfortunately on powerpc, the main here
> overrides the main given in -lcrt0 (or wherever it's defined).  If I
> leave out the definition of main, then 1 is returned as expected.
> (Linker errors if MAIN isn't the correct name.)

Yeah, this must be the problem that I had too.  I didn't get as far in 
figuring out exactly what was breaking.

> At this point, I gave up on trying to get configure to work.

Yeah, well, as it appears to be a bug in configure, what do you think we 
should do?  A couple of months ago I generated the files that configure 
is supposed to generate by hand and that lead to a working matlisp, so 
once we get through this problem it should work.

I don't really want to delve into how autoconf works too much to get it 
to work.  Maybe there is some simple change to the configure.in file 
that we can make to skip this check on OS X.  I'll look into that tonight.

I guess there arn't many projects that run on OS X that use both fortran 
and autoconf.....

--Robbie


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504