On 2 October 2012 16:50, McClintock Matthew-B29882 wrote:
>> Yea, I suppose the the host compiler should be checked by autotools
>> if it supports these warning flags.
>
> Should this block applying this patch to oe-core or will there be
> upstream fixes before 1.3?
This is the right fix for the
On Fri, Sep 28, 2012 at 10:03 AM, Matthew McClintock wrote:
> On Fri, Sep 28, 2012 at 9:52 AM, Burton, Ross wrote:
>> On 28 September 2012 02:33, Matthew McClintock wrote:
>>> Fixes these sorts of issues present on older gcc (CentOS 5.x in this case)
>>>
>>> | cc1: error: unrecognized command li
On Fri, Sep 28, 2012 at 9:52 AM, Burton, Ross wrote:
> On 28 September 2012 02:33, Matthew McClintock wrote:
>> Fixes these sorts of issues present on older gcc (CentOS 5.x in this case)
>>
>> | cc1: error: unrecognized command line option "-Werror=implicit"
>> | cc1: error: unrecognized command
FWIW, I've just filed #55423 and #55424 upstream for these issues.
Ross
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
On 28 September 2012 02:33, Matthew McClintock wrote:
> Fixes these sorts of issues present on older gcc (CentOS 5.x in this case)
>
> | cc1: error: unrecognized command line option "-Werror=implicit"
> | cc1: error: unrecognized command line option "-Werror=nonnull"
Took me a minute to realise w
Fixes these sorts of issues present on older gcc (CentOS 5.x in this case)
| cc1: error: unrecognized command line option "-Werror=implicit"
| cc1: error: unrecognized command line option "-Werror=nonnull"
| cc1: error: unrecognized command line option "-Werror=init-self"
| cc1: error: unrecognize
