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
compilation; I normally use
CFLAGS="-arch x86_64" LDFLAGS="-arch x86_64" etc/make-liarc.sh
These flags are automatically supplied when building native
executables; it's only necessary to specify them in the case of liarc
executables that differ from the default.
2. MacOS 10.5.x definitely supports "-arch x86_64", but that's a
function of the Xcode install rather than the operating system. Using
recent Xcode 3.1.x I have had no trouble using this arch.
3. Spaces in directory names are supposed to be OK, but I think we
need more quoting in the makefiles to get that working. At some point
I'll put that effort in.
On Mon, Nov 9, 2009 at 6:40 PM, Taylor R Campbell <campb...@mumble.net> wrote:
> Date: Mon, 9 Nov 2009 18:26:52 -0800
> From: "Arthur A. Gleckler" <a...@speechcode.com>
>
> Alas, I didn't get far. (See attached.)
>
> It appears that <gcc> on OS X expects <i386>, <ppc> or <ppc64> 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-64 processors inside them
> since about a month after I got my MacBook, which was several years
> ago.
>
> But that doesn't seem to be what this error is
> complaining about.
>
> Argh. Edit etc/make-liarc.sh to wrap the backticked arguments to
> configure in double-quotes:
>
> run_configure "--prefix=`pwd`/boot-root" ...
>
> 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.
>
_______________________________________________
MIT-Scheme-devel mailing list
MIT-Scheme-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/mit-scheme-devel
