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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 17 Oct 2007 10:03:14 -0700
From:	Dave Hansen <haveblue@...ibm.com>
To:	Badari Pulavarty <pbadari@...ibm.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, Andi Kleen <ak@....de>
Subject: Re: 2.6.23-git11 compile issues

On Wed, 2007-10-17 at 08:33 -0700, Badari Pulavarty wrote:
> Known issue ?
...
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   CC      arch/x86/kernel/asm-offsets.s
> In file included from arch/x86/kernel/asm-offsets_64.c:7,
>                  from arch/x86/kernel/asm-offsets.c:4:
> include/linux/crypto.h:20:24: error: asm/atomic.h: No such file or directory
> In file included from include/linux/types.h:14,
>                  from include/linux/prefetch.h:13,
>                  from include/linux/list.h:8,
>                  from include/linux/module.h:9,
>                  from include/linux/crypto.h:21,
>                  from arch/x86/kernel/asm-offsets_64.c:7,
>                  from arch/x86/kernel/asm-offsets.c:4:

I hit the same thing, and fixed it with mrproper as well.  I assume this
is a result of the x86 merge.

Andi, is there a way we can detect the old include directories, and
error out?  Otherwise, we're going to get a ton more of these reports
when people do incremental patching up to 2.6.24.  I've been doing
nightly incremental builds for a year or two, and I think this is the
first time it has actually required manual intervention.

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ