| 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
| ||
|
Message-Id: <200910221629.59818.arnd@arndb.de> Date: Thu, 22 Oct 2009 16:29:59 +0200 From: Arnd Bergmann <arndbergmann@...glemail.com> To: Stephan von Krawczynski <skraw@...net.com> Cc: "linux-kernel" <linux-kernel@...r.kernel.org> Subject: Re: include/asm-generic/int-ll64.h kernel 2.6.31.4 On Tuesday 20 October 2009, Stephan von Krawczynski wrote: > I lately compiled some app that stumbled across this, and someone smarter than > me should judge if this is right or wrong: > > > * asm-generic/int-ll64.h > * > * Integer declarations for architectures which use "long long" > * for 64-bit types. > */ > > #ifndef _ASM_GENERIC_INT_LL64_H > #define _ASM_GENERIC_INT_LL64_H > > #include <asm/bitsperlong.h> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > Is it correct to include from linked "asm" instead of asm-generic ? > > My link goes to "asm-x86" but for some reason asm-generic/types.h is included > which ends at int-ll64.h trying to include a not existing bitsperlong.h from > directory asm-x86. Hi Stephan, Most likely you are using the kernel headers in an unsupported way, like trying to point to $(HOME)/linux-2.6/include for include files when building an application. Please see http://kernelnewbies.org/KernelHeaders for how to fix that. Arnd <>< -- 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