Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 20 Jan 2013 10:38:17 +0100
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: new clang 3.2 warnings

On 01/20/2013 04:35 AM, Dhiru Kholia wrote:
> Hi,
> 
> 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'

when building with

$ clang --version
clang version 2.9 (tags/RELEASE_29/final)
Target: i386-redhat-linux-gnu
Thread model: posix

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.

Frank

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ