RE: [PHP-QA] Build Problem with latest CVS Version under OpenBSD2.7

Sascha Schumann wrote: > > > > It would perhaps be worth trying to detect the m4 version from > > > autoconf and alerting the user if it doesn't have esyscmd capability. > > > > That makes sense to me. ...maybe we could write a little m4 script that > > checks for the existence of the needed m4 macros with ifdef??? > > Nope, just let them fix their build tools. If a user depends > on being able to run buildconf on a broken system, she shall > install GNU m4 (it is probably easily available through the > OpenBSD ports mechanism). > Fair enough ... it has been fixed in -current but not back-applied since it isn't a critical -stable fix, so that means that it's not possible to rebuild the configuration using OpenBSD-2.7. The user can't use GNU m4 though - although it exists in ports, the OpenBSD m4 has a GNU compat mode which is used by autoconf. So OpenBSD-2.7 will always be broken, but -current or 2.8 will work fine when it is released (in about 2-3 months). More annoying is the libtool bug with the 100000000000 warnings that are spewed ... it's on my TODO list to take a closer look at that when I get a chance, if noone else does. -- Anil Madhavapeddy, <anil@recoil.org>