Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPfzE3YdqOJ1GMd16FQfyZxW0mxVw3cy=Nq3k6BENp=a92jeSA@mail.gmail.com>
Date: Wed, 10 Jul 2013 15:11:01 +1200
From: Andre Renaud <andre@...ewatersys.com>
To: musl@...ts.openwall.com
Subject: Re: endian.h warnings

Hi Rich,
> I really don't understand why gcc is generating warnings for these; I
> thought it automatically suppressed warnings for system include
> directories, and even macro expansion text generated from macros
> defined in these headers. If that suppression is not working
> correctly, maybe we should work around these warnings. I agree it's
> problematic for users to get spammed with irrelevant warnings that
> decrease the signal to noise ratio of the compiler's warning
> generation.

You're right, this was caused because I wasn't correctly using the
musl-gcc wrapper script, so gcc wasn't aware that they were system
includes.

Regards,
Andre

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.