Re: Makefile Help?

Anant Narayanan wrote:

You might want to check out the /generator/* directory. generator.php does all the work of merging the .defs and .overrides to the gen_* files. Yup, I've been looking at that. The impression I get, however, is that generator/generator.php just never gets called.

Hmm, if its a PHP script after all, could it be that PHP itself is having trouble on FreeBSD? I don't think so. I've run other PHP test scripts and all seems to be well. The only time I get an error is when I have the php_gtk2.so extension activated. If I have it commented out, PHP runs fine and error-free.

A missing extension maybe? Hmm, that's a possibility, but with FreeBSD's port system, any dependencies should be dealt with during make/make install.

After a few days of digging and because of the output of config.log, I think the OS is being mis-identified at some point in the configuration process. When I compare config.log from my Linux to that of FreeBSD, it just doesn't make sense for a UNIX system in general or a FreeBSD system in particular. Here's what I see in the Linux config.log (after the preamble): ## --------- ## ## Platform. ## ## --------- ## hostname = beauty.tarrantland.com uname -m = i686 uname -r = 2.6.12-12mdksmp uname -s = Linux uname -v = #1 SMP Fri Sep 9 17:43:23 CEST 2005 Whereas in the FreeBSD config.log, I see this: configure:1668: checking for Cygwin environment configure:1684: cc -c conftest.c 1>&5 configure: In function `main': configure:1680: error: `__CYGWIN32__' undeclared (first use in this function) configure:1680: error: (Each undeclared identifier is reported only once configure:1680: error: for each function it appears in.) configure: failed program was: It just looks to me like ./configure thinks it's on a Windows box. There is no mention of FreeBSD anywhere in the config.log file. Andrei mentioned in his post that config.guess is where the OS is identified. I ran it on its own and here's the output: i386-unknown-freebsd6.1 That looks okay to me, so config.guess seems to know what environment it's in. At some point after that, this string must be getting mis-interpreted by another part of the config process. -Ron T.