Quick GD compile question

Looking to compile PHP4b4pl1 with GD support. I've succesfully compilied zlib, libpng, and the gd library itself. I'd like to be able to compile PHP, linking against this gd library, rather then the ext/gd version. I use the following to make. ./configure --with-gd=/usr/home/adboink/august/gd-1.7.3/ --disable-rpath --d isable-inline --with-mysql --with-config-file-path=/usr/home/adboink/august/ .phpini --enable-debug=no --enable-force-cgi-redirect=yes -with-zlib=/usr/ho me/adboink/august make [snip] Making all in gd gcc -DHAVE_CONFIG_H -I. -I/usr/home/adboink/august/php-4.0b4pl1/ext/gd -I../ .. -I../../Zend -I/usr/home/adboink/august/php-4.0b4pl1 -I/usr/local/include -I/usr/home/adboink/august/gd-1.7.3/ -I/usr/local/include/mysql -I/usr/home /adboink/august/include -D_REENTRANT -g -O2 -c gd.c && touch gd.lo gcc -DHAVE_CONFIG_H -I. -I/usr/home/adboink/august/php-4.0b4pl1/ext/gd -I../ .. -I../../Zend -I/usr/home/adboink/august/php-4.0b4pl1 -I/usr/local/include -I/usr/home/adboink/august/gd-1.7.3/ -I/usr/local/include/mysql -I/usr/home /adboink/august/include -D_REENTRANT -g -O2 -c gdcache.c && touch gdcache.lo In file included from gdcache.h:44, from gdcache.c:47: /usr/local/include/malloc.h:81: parse error before `*' /usr/local/include/malloc.h:82: parse error before `*' /usr/local/include/malloc.h:87: parse error before `*' which is certainly unpleaseant. I'll file as a bug, but thought I'd to a quick check to make sure I am not missing something. August > -----Original Message----- > From: Andrei Zmievski [mailto:andrei@ispi.net] > Sent: Monday, March 06, 2000 11:57 AM > To: Shane Burrell > Cc: php4beta@lists.php.net > Subject: Re: [PHP4BETA] Intended use of session and HTTP_*_VARS. > > > On Mon, 06 Mar 2000, Shane Burrell wrote: > > We intend to migrate to using only the http_state_vars. > Checking things into > > the global scope automatically worked great till our projects > got big. Now we > > are faced with migrating to http_state_vars only. After our > migration it > > won't be an issue. I may try to re-associate state and global > until everything > > uses http_state_vars. I don't know which way it should work > but state vars > > are a little different that post or get as far as updating from > code. Would it > > make sense to offer a ini setting to control the behavior? > > I don't know. Generally an ini setting should be introduced if there is > a really good case for it. You might just one to change one 0 to 1 in > your local PHP source copy and compile that, if you want them to be > re-associated. > > -Andrei > > Any sufficiently advanced Operating System > is indistinguishable from Linux. > - Jim Dennis > > -- > PHP 4.0 Beta Mailing List <http://www.php.net/version4/> > To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net > For additional commands, e-mail: php4beta-help@lists.php.net > To contact the list administrators, e-mail: php4beta-admin@lists.php.net >