OSX is better, handling checkone with no problem, but after checking these
new sources into my CVS repository, I ran into the known chicken and egg
problem.  Both cygwin and OSX need the their gforth executable, as I've had
to do before, but on OSX, that's not quite enough.  After I do the
configure, make gives me the following:

[Dennis-Ruffers-Computer:Tools/OSX/gforth] druffer% make
if test -r version && test x'0.5.9-20030201' = x`cat version` ; then true ;
else echo 0.5.9-20030201 > version ; fi
make gforth
aclocal
cd . && autoconf
configure.in:70: error: possibly undefined macro: AC_GNU_SOURCE
make[1]: *** [configure] Error 1
make: *** [kernel/version.fs] Error 2

I then have to update (without merging) configure again and then I can
execute it and make just fine.

Now that's weird! ;(

DaR

On 2/2/03 5:07 PM, "Dennis Ruffer" <[EMAIL PROTECTED]> wrote:

> Great job you all!  It looks like, on cygwin at least, you've gotten around
> the gcc 3.x problems and you've even beat the speed we had with gcc 2.95.
> I'm still doing more testing before I integrate it fully into our compiler
> environment, but straight out of the box I ran into the following:
> 
> Administrator@DRUFFER /usr/src/gforth-0.5.9-20030201
> $ make check
> cd engine && make gforth.exe gforth-fast.exe gforth-itc.exe gforth-ditc.exe
> #gforth-prof.exe gforth-native.exe
> make[1]: Entering directory `/usr/src/gforth-0.5.9-20030201/engine'
> make[1]: `gforth.exe' is up to date.
> make[1]: `gforth-fast.exe' is up to date.
> make[1]: `gforth-itc.exe' is up to date.
> make[1]: `gforth-ditc.exe' is up to date.
> make[1]: Leaving directory `/usr/src/gforth-0.5.9-20030201/engine'
> cp -p gforth.exe gforth~
> cp -p engine/gforth.exe gforth.exe
> cp -p engine/gforth-fast.exe gforth-fast.exe
> cp -p engine/gforth-itc.exe gforth-itc.exe
> cp -p engine/gforth-ditc.exe gforth-ditc.exe
> cp -p kernl32l.fi kernl32l.fi~
> cp -p kernl32l.fi- kernl32l.fi
> GFORTHD="./gforth-ditc -p .:." GFORTH="./gforth-ditc --die-on-signal -p
> .:. -i kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs
> arch/386/disasm.fs" ./gforthmi gforth.fi  --die-on-signal -p ".:~+:." -i
> kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs arch/386/disasm.fs
> data offset=-40FF20
> code offset=68
> xt offset=58
>      3C           E71000           A70000
>    1CE0          A0477D8          A047760
>    8D20         615B3B14         615B42B4
>    9408          A045160          A0450E8
>    A464          A046AC8          A046A50
>    EE00          A057B78          A057B00
>    EE60          A047A58          A0479E0
>   16060          A04E620          A04E5A8
> make checkone ENGINE="./gforth --no-dynamic" >/dev/null 2>&1
> make: *** [check] Interrupt
> 
> As you can maybe see, I had to hit a Ctrl-C to get out of checkone.  I tried
> playing with the flags I used to use and the CFLAGS=-D_WIN32 appears to be
> no longer necessary, but --enable-force-reg and --enable-indirect-threaded
> appear to still speed things up.  However, nothing I've tried yet seems to
> solve checkone.  The system does not appear to be dead, but taking a lot of
> CPU time to do nothing?
> 
> Everything else on cygwin looks good!
> 
> Now on to OSX.
> 
> DaR
> 
>> -----Original Message-----
>> From: Anton Ertl [mailto:[EMAIL PROTECTED]]
>> Sent: Sunday, February 02, 2003 3:16 AM
>> To: [EMAIL PROTECTED]
>> Subject: [gforth] New snapshot available
>> 
>> 
>> You can find the latest snapshot at
>> 
>> http://www.complang.tuwien.ac.at/forth/gforth/Snapshots/gforth
>> -0.5.9-20030201.tar.gz
>> 
>> This snapshot has been tested successfully on:
>> 
>> alpha-dec-osf4.0d
>> alpha-unknown-linux-gnu
>> hppa1.1-unknown-linux-gnu
>> hppa2.0w-hp-hpux11.11
>> i386-unknown-freebsd4.7
>> i486-pc-linux-gnulibc1
>> i686-pc-linux-gnu
>> mips-dec-ultrix4.3
>> mipsel-pc-linux-gnu
>> mips-sgi-irix6.5
>> powerpc-apple-darwin5.4
>> powerpc-unknown-linux-gnu
>> 
>> The main thing missing before the release is an update to the
>> documentation.
>> 
>> - anton
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to