I'm working with the cURL project (http://curl.haxx.se), and I setup a daily build on my 4.9-RELEASE machine. Things were going fine until I upgraded to 4.9-STABLE. At that point the daily builds started failing. As far as I can tell the reason for that was that /usr/bin/m4 was somehow different from the same version on the FSF web site. I downloaded and built m4 from the FSF web site and installed it in /usr/local/bin (which is at the beginning of my PATH) and then the build started working again. Can anyone here confirm or deny my hypothesis? Any information would be welcome as I'd like to understand what happened. Thanks Joe
On Sun, Mar 14, 2004 at 04:07:11PM -0600, Joe Halpin wrote:> I'm working with the cURL project (http://curl.haxx.se), and I setup a > daily build on my 4.9-RELEASE machine. Things were going fine until I > upgraded to 4.9-STABLE. At that point the daily builds started failing. > > As far as I can tell the reason for that was that /usr/bin/m4 was > somehow different from the same version on the FSF web site. I > downloaded and built m4 from the FSF web site and installed it in > /usr/local/bin (which is at the beginning of my PATH) and then the build > started working again. > > Can anyone here confirm or deny my hypothesis? Any information would be > welcome as I'd like to understand what happened.FreeBSD does not use GNU m4. Tim
On Sun, 14 Mar 2004, Joe Halpin wrote:> I'm working with the cURL project (http://curl.haxx.se), and I setup a > daily build on my 4.9-RELEASE machine. Things were going fine until I > upgraded to 4.9-STABLE. At that point the daily builds started failing. > > As far as I can tell the reason for that was that /usr/bin/m4 was > somehow different from the same version on the FSF web site. I > downloaded and built m4 from the FSF web site and installed it in > /usr/local/bin (which is at the beginning of my PATH) and then the build > started working again. > > Can anyone here confirm or deny my hypothesis? Any information would be > welcome as I'd like to understand what happened.If you are working on code that depends on GNU-isms in m4, you will indeed need GNU m4. Install the port (devel/m4), and look at how other ports handle this requirement, for example autoconfuse^Wautoconf. $.02, /Mikko