On Sun, 2002-05-19 at 14:25, J.A. Magallon wrote:
> It can be because gcc just does that, It 'fixes' system headers to
> correct some odd things, and stores its modified versions in, say,
> /usr/lib/gcc-lib/3.1.0/include. So default includepath for gcc is
> really -I/usr/lib/gcc-lib/3.1.0/include
On 2002.05.17 Lonnie Borntreger wrote:
>On Thu, 2002-05-16 at 16:19, Gwenole Beauchesne wrote:
>> Hi,
>>
>> > cc1: warning: changing search order for system directory "/usr/include"
>> > cc1: warning: as it has already been specified as a non-system
>> > directory
>>
>> Package is (badly) ad
On Fridayen den 17 May 2002 13.02, Gwenole Beauchesne wrote:
> Hi,
>
> > Ok. Can you please give hints how to fix it?
>
> If the package is autoconf'iscated, then check config.log. If grep
> "changing search order" yields something, then you will have to track
> CPPFLAGS additions.
>
> Look for ex
Hi,
> Ok. Can you please give hints how to fix it?
If the package is autoconf'iscated, then check config.log. If grep
"changing search order" yields something, then you will have to track
CPPFLAGS additions.
Look for example *no-locincpth* patches for cfengine, ical, TiMidity++,
imlib.
Bye,
On Fridayen den 17 May 2002 10.34, Gwenole Beauchesne wrote:
> On Fri, 17 May 2002, Oden Eriksson wrote:
> > > Solution: fix the package so that it doesn't -I/usr/include, or
> > > -I/usr/local/include explicitly.
> >
> > I guess most mandrake packages needs fixing then?
>
> At most 22 in failure
On Fri, 17 May 2002, Oden Eriksson wrote:
> > Solution: fix the package so that it doesn't -I/usr/include, or
> > -I/usr/local/include explicitly.
>
> I guess most mandrake packages needs fixing then?
At most 22 in failure state, 115 in sucess state. At most because that
falls only in particul
On 17 May 2002 00:47:01 -0500 Lonnie Borntreger <[EMAIL PROTECTED]> wrote:
> On Thu, 2002-05-16 at 16:19, Gwenole Beauchesne wrote:
> > Hi,
> >
> > > cc1: warning: changing search order for system directory "/usr/include"
> > > cc1: warning: as it has already been specified as a non-system
>
On Thu, 2002-05-16 at 16:19, Gwenole Beauchesne wrote:
> Hi,
>
> > cc1: warning: changing search order for system directory "/usr/include"
> > cc1: warning: as it has already been specified as a non-system
> > directory
>
> Package is (badly) adding system include dir to include search path.
On Thursdayen den 16 May 2002 23.19, Gwenole Beauchesne wrote:
> Hi,
>
> > cc1: warning: changing search order for system directory "/usr/include"
> > cc1: warning: as it has already been specified as a non-system
> > directory
>
> Package is (badly) adding system include dir to include search p
On 2002.05.16 Gwenole Beauchesne wrote:
>Hi,
>
>> cc1: warning: changing search order for system directory "/usr/include"
>> cc1: warning: as it has already been specified as a non-system
>> directory
>
>Package is (badly) adding system include dir to include search path. In
>some occasions,
Hi,
> cc1: warning: changing search order for system directory "/usr/include"
> cc1: warning: as it has already been specified as a non-system
> directory
Package is (badly) adding system include dir to include search path. In
some occasions, that would inhibit features to be found by config
Hi,
Why is it that I now get loads of the following:
cc1: warning: changing search order for system directory "/usr/include"
cc1: warning: as it has already been specified as a non-system directory
cpp0: warning: changing search order for system directory "/usr/include"
cpp0: warning: as it
12 matches
Mail list logo