[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dd5aa1544ad6f9fecae1c0b881bf7e31@smtp.hushmail.com>
Date: Sun, 20 Jan 2013 10:55:30 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: new clang 3.2 warnings
On 20 Jan, 2013, at 10:38 , Frank Dittrich <frank_dittrich@...mail.com> wrote:
> On 01/20/2013 04:35 AM, Dhiru Kholia wrote:
>> I am getting tons of warnings which look like "clang: warning:
>> argument '-faddress-sanitizer' is deprecated, use '-fsanitize=address'
>> instead" when using clang 3.2.
>>
>> These warnings are harmless (but ugly) and are emitted only during
>> *-clang-debug target builds.
>>
>> Is adding something like "HAVE_CLANG_3_2" to Makefile the only
>> solution to fix this problem?
>
> I am getting warnings
>
> clang: warning: argument unused during compilation: '-faddress-sanitizer'
>
> I just assumed that my clang version was too old to know this switch.
> Since only the -clang-debug target was affected, I didn't care.
>
> I would prefer -clang-debug just using the option name that is required
> for the newest clang version(s), instead of having to adjust one more
> config variable.
> But when I change the option name in Makefile, I get
> clang: warning: argument unused during compilation: '-fsanitize=address'
> instead, for 2.9 and for 3.1.
>
> This is bad. May be HAVE_CLANG_3_2 is a good enough solution right now?
> How widespread is clang 3.2? Fedora 18 still uses 3.1.
Adding "HAVE_something" won't be any better than adding a few comments around that build target.
The icc targets normally have to be manually edited depending on version too.
Bull's clang is 3.0-6ubuntu3. It doesn't seem to understand either of the variants.
magnum
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.
