> This package uses Pure's new bitcode loader to ease porting, so you'll need
> Pure 0.45 or later and an LLVM-based C compiler installed. The Makefile is set
> up for clang (http://clang.llvm.org/) by default, because it's easier to
> install, but you can also use llvm-gcc if you set the CC make variable
> accordingly.
But the Makefile has no mention of clang or llvm-gcc.
pure-sockets 0.2's Makefile did use clang, and had commented-out options for llvm-gcc.
Did the clang / llvm-gcc requirement go away with version 0.3? It seems to compile fine for me with Mac OS X's usual gcc 4.2. Does the README need an update?
Oops, it looks like an old README slipped into that tarball. I fixed
that now. Get the latest one from:
http://pure-lang.googlecode.com/files/pure-sockets-0.3.tar.gz
(Same sources as before, only the README has been updated.)
> Did the clang / llvm-gcc requirement go away with version 0.3?
Yes, the module is now built as a shared library like the others. clang
or llvm-gcc isn't required any more.
Albert
--
Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email: Dr.G...@t-online.de, a...@muwiinfa.geschichte.uni-mainz.de
WWW: http://www.musikinformatik.uni-mainz.de/ag
Some glitches in the Makefile have been fixed as well, per
http://code.google.com/p/pure-lang/issues/detail?id=57.
It seems that GC doesn't let me update the tarball once again, so I just
bumped the version number and uploaded a new one:
http://pure-lang.googlecode.com/files/pure-sockets-0.4.tar.gz