[MIT-Scheme-devel] problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Arthur A. Gleckler
I'm re-sending this message with an abbreviated transcript because the first attempt bounced from . On Mon, Nov 9, 2009 at 5:50 PM, Arthur A. Gleckler wrote: > Has anyone tried the x86-64 build on OS X 10.5?  I've built from an > up-to-date, clean repository on a machine with the most recent > of

[MIT-Scheme-devel] Re: problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Taylor R Campbell
Date: Mon, 9 Nov 2009 17:50:51 -0800 From: "Arthur A. Gleckler" Has anyone tried the x86-64 build on OS X 10.5? I've built from an up-to-date, clean repository on a machine with the most recent official C build installed, and I'm getting this error: Microcode Error: No error

[MIT-Scheme-devel] Re: problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Arthur A. Gleckler
> I haven't tried building it on OS X at all, but did you build the C > distribution as i386 or as x86-64?  If i386, that will cause make.bin > to be a 32-bit fasl, which the 64-bit microcode won't know how to > read.  You may need to build the C distribution with > > sh etc/make-liarc.sh 'CFLAGS=-

[MIT-Scheme-devel] Re: problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Arthur A. Gleckler
> Thank you!  I didn't do that, but will try it now. Alas, I didn't get far. (See attached.) It appears that on OS X expects , or as the value of <-arch>. But that doesn't seem to be what this error is complaining about. I have machines running 10.6 at home. I'll see whether this works the

[MIT-Scheme-devel] Re: problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Taylor R Campbell
Date: Mon, 9 Nov 2009 18:26:52 -0800 From: "Arthur A. Gleckler" Alas, I didn't get far. (See attached.) It appears that on OS X expects , or as the value of <-arch>. Maybe GCC isn't set up to build x86-64 code on 10.5? That would be weird, since Apple machines have had x86-6

[MIT-Scheme-devel] Re: problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Arthur A. Gleckler
> There may be other lurking space-sensitive `pathname' arguments among > the scripts -- you could also try renaming the directory from `MIT > Scheme' to `mit-scheme' or something without any spaces in it. Gee whiz. Sorry to bother you with such a trivial problem. I had built successfully earlie

[MIT-Scheme-devel] Re: problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Chris Hanson
Just to clarify: 1. To build 64-bit native code from a liarc build, the liarc build must have been compiled as a 64-bit executable. Likewise with 32-bit. By default, Xcode generates 32-bit executables (though I think Xcode 3.2.x defaults to 64-bit), so it's necessary to override this during comp

[MIT-Scheme-devel] Re: problems with the x86-64 build on OS X 10.5

2009-11-09 Thread Arthur A. Gleckler
>    CFLAGS="-arch x86_64" LDFLAGS="-arch x86_64" etc/make-liarc.sh Hurrah! That did it. Once that built, I was able to build the native x64-64 version. Thanks again to you both. ___ MIT-Scheme-devel mailing list MIT-Scheme-devel@gnu.org http://list