[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-smalltalk] help-smalltalk post from address@hidden requires ap
From: |
Stephen Compall |
Subject: |
Re: [Help-smalltalk] help-smalltalk post from address@hidden requires approval |
Date: |
Thu, 31 May 2007 21:47:25 -0500 |
On Thu, 2007-05-31 at 13:48 +0200, Paolo Bonzini wrote:
> > I tried to compile smalltalk--devo--2.2--patch-364 on my intel core 2
> > duo macbook. This attempt proved unsuccessful.
> > I attached a bzip containing the config.log for this first configure.
> >
> > I then ran ./configure CFLAGS='-D__i386__=1 -Wall -pipe -O2' and
> > followed up with make which exited giving me a lot of messages
> > like src/x86/darwin.S:41:Invalid mnemonic 'pushl'
>
> This is weird, as other people have compiled it successfully (and even
> before the recent fixes, the problems were not in compilation, but in
> execution).
>
> You should anyway use "-m32" and "-m64" instead of -D__i386__=1 vs.
> -D__x86_64__=1, if I remember correctly.
http://rafb.net/p/gE0Arh11.html is what Raevel (the reporter) got with
-m32 (which made the most sense to me as OOPs are 4 bytes by default
there.)
For the x86 ffitarget.h to compile, either __i386__ or __x86_64__ must
be defined. Neither of these seem to be defined by that compiler (gcc
4.0.1 20050625 (prerelease)).
This is a Core 2 Duo; my machine (and I assume that of most other
Darwin/x86 testers) is a Core Duo. What kinds of breakage might there
be?
Raevel also said that '-D__i386__=1 -m32' broke while compiling, but I
didn't get an error log from that.
--
;;; Stephen Compall ** http://scompall.nocandysw.com/blog **
Failure to imagine vast possibilities usually stems from a lack of
imagination, not a lack of possibility.
signature.asc
Description: This is a digitally signed message part