Re: Re: tru64 5.1b & php4.3.2rc1

From: Date: Wed, 30 Apr 2003 16:37:46 +0000
Subject: Re: Re: tru64 5.1b & php4.3.2rc1
References: 1 2  Groups: php.install 
Request: Send a blank email to php-install+get-10763@lists.php.net to get a copy of this message
ldg@ulysium.net wrote: > on 4/29/03 1:56 PM, Michael Mauch at michael.mauch@gmx.de uttered the > following: > >>> I get lots of errors, and some of them I was able to get rid of by doing >>> something I shouldn't be doing: >>> I have duplicate header files like stdio.h and unistd.h (several others), >>> because they are in the standard system area /usr/include but also in >>> /usr/local/include because they were installed by some rpm packages I >>> needed. >> >> Oops, that sounds ugly - I don't think that it is a good idea to have >> different system header files in /usr/include and /usr/local/include. >> It's just asking for trouble. > > Unfortunately, this couldn't be avoided, as most of what's in /usr/local was > put there by the rpms I needed, but those add such dupes of headers and > they're needed... Strange... >> You can also try if >> >> env CC="cc -I/usr/include" ./configure your_configure_options >>> cc: Error: /usr/include/dlfcn.h, line 59: Missing ";". (nosemi) >>> extern int dladdr __((void *, Dl_info *)); >>> -------------------------------^ >> [Lots of similar problems with "__"] >> >> I don't know what's happening there - what was your configure line? > > See above. I don't think /usr/include needs to be specified, it seems to > find those things by itself, and the stuff in /usr/local seems found fine > with adding that to the cflags, I guess because the --with options tells it > where to get that stuff... > The thing is, I was able to build 4.3.0 all the way before... > I'll give a shot at rc2 right now... I proposed the CC="cc -I/usr/include" thing because then these system headers will be first in your include path, maybe this changes these "__" problems. Regards... Michael

« previous php.install (#10763) next »