Re: the same gcc binary emits warnings on one machine but not on another

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: john smith <wempwer@xxxxxxxxx>
Subject: Re: the same gcc binary emits warnings on one machine but not on another
From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
Date: Thu, 20 Oct 2016 19:01:55 +0100
Cc: gcc-help <gcc-help@xxxxxxxxxxx>
In-reply-to: <CAKmQUfbwxhVrP8xiQvd1XeD_peK5n=O76JZndf9bewxz-M3saw@mail.gmail.com>
References: <CAKmQUfZnzT9AMG5wE7fnePA4mzUmSN-C6aMNs6RFN1+LZDrz2w@mail.gmail.com> <CAH6eHdRESw69vNWK1nPCt6ZPMSV-uB5wFia51MSaj1eEDYgkCg@mail.gmail.com> <CAKmQUfbwxhVrP8xiQvd1XeD_peK5n=O76JZndf9bewxz-M3saw@mail.gmail.com>

On 20 October 2016 at 19:00, john smith wrote:
> Since it's a cross-compiler do headers in /usr/include matter?

Sorry, you're right, but the ones in "$sysroot/usr/include do.

References:
- the same gcc binary emits warnings on one machine but not on another
  - From: john smith
- Re: the same gcc binary emits warnings on one machine but not on another
  - From: Jonathan Wakely
- Re: the same gcc binary emits warnings on one machine but not on another
  - From: john smith

Prev by Date: Re: the same gcc binary emits warnings on one machine but not on another
Next by Date: Re: the same gcc binary emits warnings on one machine but not on another
Previous by thread: Re: the same gcc binary emits warnings on one machine but not on another
Next by thread: Re: the same gcc binary emits warnings on one machine but not on another
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux