Re: Matlisp on OS X

Hi again

Thanks to those who have taken the time to offer me some help. In reply to
Raymond's email about checking the C compiler is working, I have been able
to build a C helloworld app fine, and the binary produced using the "gcc
-c -O2 helloworld.c" syntax is called helloworld. So, I don't know where
the name b.out is coming from.

In reply to Tunc's email, I guess there are greater forces at play than my
non-mainstream OS and lack of experience hacking it.

I'd love to get Matlisp going on OS X if possible, and I'm more than
willing to help out in any way I can, but I guess you guys have more
experience getting Matlisp to play nice on UNIX.

As an aside, I'm seeing more and more people 'switch' over to OS X (if
you'll excuse the marketing victim speak), particularly for scientific
work. I know two academic in my dept. who have moved from Linux to OS X,
and several others who have fallen in love with Apple's line of laptops
and are going to 'switch' when they next get a new computer. So, that
being said, I'd encourage support of OS X by the OSS crowd as far as
possible.

Most people use fink (fink.sourceforge.net) to install UNIX apps for OS X,
so perhaps they might be a useful resource to tap into if there is
significant work to be done to port Matlisp to OS X *and* you guys think
this is worth doing.</my .10c>

Thanks again

Chris


On 21 Apr 2003, Raymond Toy wrote:

> >>>>> "Chris" == junk2  <[email protected]> writes:
>
>     Chris> So, again, b.out appears, although I can't actually see that file on my
>     Chris> system (nor the conftest.c file) -- perhaps these get cleaned up in the
>     Chris> ./configure... script?
>
> Yes, configure will clean it up.  Before we can make progress, we'll
> have to solve this problem.  (I do have an iMac running OSX at home,
> but don't have acl.)
>
> Try looking through the generated configure script.  Find the place
> where conftest.c is created.  And try to compile that up by hand.
>
> Or you could just do a simple "Hello world!" program, and compile it
> using "gcc -c -O2 hello.c" and see where the output goes.  It seems
> that b.out is ok.  Then try to run it.
>
>     Chris> One thing I have just remembered: When writing C++ code for OS X, one has
>     Chris> to explicitly link against libstdc++.a, which, as far as I understand, is
>     Chris> not the case on Linux, say. Could a similar problem be to blame here?
>
> Matlisp doesn't use any C++ code.
>
> Ray
>