From: Martin R. <fo...@ru...> - 2009-03-09 02:13:12
|
Dear Fooers, after long time of silence I tried to get back to this issue, after I already tried several months ago and also failed badly. I suspect that it really was a bug in automake of macports, as I did not have these problems again. I just automake-1.10-ified the bootstrap scripts and added some compile hints for fooelk and foo -- the rest seems to work. Of course, there were some bugs left ofter with the bpf functions, and I did not yet get back to these... Happy fooing so far, all the best! Martin On Mon, Jun 16, 2008 at 12:55:52AM +0200, Gerhard Eckel wrote: > Dear Foo developers, > > I was trying to install Foo on a OS X 10.5 system and failed badly. I > used autoconf 1.10 (through macports) and tried fixing the obvious > things. But there is some macro stuff going on which I don't > understand - even after RingTFM. Could some kind soul take a look at > this? I guess it has mainly to do with the new autoconf version. > Other problems are caused by the fact that the macports stuff is > installed under /opt/local and not /usr/local. > > I just ordered 3 Macs which will are delivered with 10.5 ... > > Best regards, > > Gerhard |