linux-kernel - Re: linux-next: sparc tree build warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Jan 2010 10:25:43 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	David Miller <davem@...emloft.net>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: sparc tree build warning

Hi Dave,

On Thu, 28 Jan 2010 05:24:32 -0800 (PST) David Miller <davem@...emloft.net> wrote:
>
> From: Stephen Rothwell <sfr@...b.auug.org.au>
> Date: Thu, 28 Jan 2010 18:44:23 +1100
> 
> > I am still seeing these.  Is it my compiler version (gcc4.4.0)?
> 
> You can't turn on DEBUG_STRICT_USER_COPY_CHECKS and
> expect a successful build.  It's for developers to
> look at the errors that are generated and audit those
> cases in detail.

These are defconfig builds and CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is
not set in either case.

> You'll get the same exact errors as on i386.

I only do an i386 defconfig build and I don't get these warnings.

> Please just elide the option from your test builds.

I would if I could :-)

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped