Re: [Tack-devel] K&R vs ANSI C

[David G. <dg...@co...>]

On Monday 25 July 2005 09:38, Simon Waite wrote:
> I think half the point of ACK is that it can be compiled by itself.

Well, the ACK does come with an ANSI C compiler, and I've had it compiling =
on=20
Minix, which uses a (ANSI-only) subset of the ACK as it's native cc.=20

Currently the ACK won't generate runnable code for any platform that can ru=
n=20
the ACK, with the possible exception of SPARC Solaris (I need to try that),=
=20
so I haven't been able to try compiling the ACK with the *actual* ACK.

> My last problems with OSX compiling seems to stem from it not being
> able to link properly which is beyond my abilities to debug as I'm not
> that up to speed with developing on OSX (though I guess if I used a gnu
> binutils toolchain rather than using OSXs native mach-o linker I'd have
> better luck)

I've had a brief play on SourceForge's OSX compiler box. I have *no idea*=20
what's going on --- it's complaining about missing symbols which are quite=
=20
clearly in the libraries. Changing the library order doesn't help.

Does OSX require symbols to be explicitly exported in the source files, do =
you=20
know?

=2D-=20
+- David Given --McQ-+ "I don't like the thought of her hearing what I'm
|  dg...@co...    | thinking." "*No-one* likes the thought of hearing
| (dg...@ta...) | what you're thinking." --- Firefly, _Objects in
+- www.cowlark.com --+ Space_