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

on 4/30/03 12:37 PM, Michael Mauch at michael.mauch@gmx.de uttered the following: > 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... Actually, thinking about it, it isn't too strange and even understandable, as the tru64 standard stuff is already in /usr and everything else such as rpms and other non-tru64 packages are in /usr/local, so as some of those packages comes with their own headers and libs, we're bound to have a second set of headers.. The key is to find the right way to make the compiler choose the right ones and not confuse them. So far I've never been able to properly track this, we don't get a good report of what's being used and from where... > 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. That's an interesting thing to explore... In the mean time, I ended up not using the option unixodbc which triggered those errors, so it went fine after that. There are several options I really was hoping to include but couldn't use them because of such errors. I guess the rest of the options used aren't causing any need for the headers causing trouble.. -- Didier Godefroy mailto:dg@ulysium.net