I think what may be happening is gcc is trying to build a universal =20
executable and can't find any ia64 stuff.
Try this change in Makefile:
from:
ifeq ($(shell uname), Darwin)
OS =3D Darwin
PICOLISP-FLAGS =3D -lc -lm -ldl
to:
ifeq ($(shell uname), Darwin)
OS =3D Dar
Hi Jon,
> But will the 64-bit Pico Lisp run on a machine (my Mac) that is "32-bit
> only" ???
Oops, no. But in another thread we had this discussion about Snow
Leopard, and we expect this to be fully 64 bits.
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
btw a Intel Core 2 Duo can do both 32bit and 64bit. So maybe your MAC
runs it on 64bit ??
>
> But will the 64-bit Pico Lisp run on a machine (my Mac) that is
> "32-bit only" ???
>
> /Jon
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
On 9/7/09 7:53 AM, Alexander Burger wrote:
On Sun, Sep 06, 2009 at 10:48:17PM +0200, Jon Kleiser wrote:
I've just installed Mac OS X 10.6, aka "Snow Leopard", on a partition on
my Mac (Intel Core 2 Duo, which probably means 32 bit only), and I was
...
picolisp)". The results weren't too nice, bu
Hi Robert,
> maybe remove the -m32 switch in the makefile and see what happens.
This might not be a good idea, because then it will compile for the
64-bit architecture where the 32-bit interpreter will choke.
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
On Sun, Sep 06, 2009 at 10:48:17PM +0200, Jon Kleiser wrote:
> I've just installed Mac OS X 10.6, aka "Snow Leopard", on a partition on
> my Mac (Intel Core 2 Duo, which probably means 32 bit only), and I was
> ...
> picolisp)". The results weren't too nice, but I'm not sure what the
As I'm going
can you use the "type" command on some of those .o files you get ?
also what is a typical "type" output on a working binary in your os.
maybe remove the -m32 switch in the makefile and see what happens.
rob
Jon Kleiser schrieb:
Hi,
I've just installed Mac OS X 10.6, aka "Snow Leopard", on a p
Hi,
I've just installed Mac OS X 10.6, aka "Snow Leopard", on a partition on
my Mac (Intel Core 2 Duo, which probably means 32 bit only), and I was
curious to see what the consequences might be for Pico Lisp. I downloaded
the ongoing dev. version of Pico Lisp and did the usual "(cd src; make
picol
