I'm just using ubuntu. Lucid, I think. I installed check and pkg-config, no problems. But I still see the same error.
On a second machine I'm using linux mint which tracks the debian rolling release. There:
$ ./configure
..
checking gmp.h usability... no
checking gmp.h presence... no
checking for gmp.h... no
configure: error: in `/home/akkartik/arcueid':
configure: error: Bignum (libgmp) test failed (--disable-bignum to disable)
See `config.log' for more details
$ sudo apt-get install libgmp10
libgmp10 is already the newest version.
Have you got libgmp-dev installed? It cannot find the development headers which you'll obviously need to compile it. Anyhow, you can use --disable-bignum if that still doesn't help. If you're still having problems you can download a tarball of Arcueid 0.0.1 in the files section of the github page. That has a configure script so you ought to be able to ./configure && make && make install from there. I should try building the thing on a clean install of Ubuntu to fully identify all the dependencies for building straight from the cloned sources.
Still unclear why ubuntu lucid is having trouble. It's a pretty vanilla server distro. I'll keep pottering with it, see what I can find out.
What do I do after building it? I tried running src/arcueid, both from the top-level dir, and from the arc dir. It segfaulted each time. Poking around with gdb now.. oh, do I have to make install before I can use it?
(I never realized how complex the makefiles get when you use autotools..)
Well, the arcueid binary expects to find arc.arc in /usr/local/share/arcueid, and like I said there's practically no error handling. You can either do a make install (which should copy arc.arc to that place where the arc binary can find it), or you can run it as src/arcueid arc/arc.arc (explicitly specifying the path to arc.arc on the command line). Oh, and do a git pull!
You don't, at least not for now. I found it faster to just write a version of the compiler in C using compiler.arc as a prototype (the fact that I've done this should be obvious by comparing compiler.c and compiler.arc). Seems there are a few more bugs in the compiler: the or macro seems to be expanding all wrong, and anything but nil crashes it. I need to take a closer look.
