We're going to get an Intel-based OS X machine next week, but I heard that other people have already experimented with compiling Pike for it. Any patches to e.g. configure scripts that can be checked in? Getting machine code to work shouldn't be too hard either I believe.
I've spent 15min on it, made the following patch and then ran out of time when it hit another problem.
% cvs diff src/configure.in ..ino/hack/Pike/7.6 Index: src/configure.in =================================================================== RCS file: /pike/data/cvsroot/Pike/7.6/src/configure.in,v retrieving revision 1.857 diff -u -r1.857 configure.in --- src/configure.in 13 Jan 2006 16:28:27 -0000 1.857 +++ src/configure.in 17 Mar 2006 17:30:30 -0000 @@ -7414,6 +7414,11 @@ extra_configure_args="${extra_configure_args} --build=${cpu}-unknown-winnt`uname -r|sed -e 's/-/_/g'` --disable-assembler" fi
+ # Nettle doesn't support assembler on Darwin x86 yet. + if [ "`uname -m`" = "i386" -a "`uname -s`" = "Darwin" ]; then + extra_configure_args="${extra_configure_args} --disable-assembler" + fi + echo "${CONFIG_SHELL-/bin/sh} "$bundle_source_dir/configure"" \ "--prefix="$pike_bundle_prefix"" ${extra_configure_args} \ "--disable-shared --cache-file=config.cache"
On Fri, 17 Mar 2006 17:10:11 +0000 (UTC) "Jonas Walld_n @ Pike developers forum" 10353@lyskom.lysator.liu.se wrote:
We're going to get an Intel-based OS X machine next week, but I heard that other people have already experimented with compiling Pike for it. Any patches to e.g. configure scripts that can be checked in? Getting machine code to work shouldn't be too hard either I believe.
If I recall correctly all I had to do was disable machine code and it worked fine. With machine code enabled nasm ends up producing some ELF object files which doesn't work so well.
Adam
pike-devel@lists.lysator.liu.se
-
Adam Montague -
Jonas Walld�n ＠ Pike developers forum -
Peter Bortas (nu med mindre Opera) ＠ Pike (-) developers forum