linux-kernel - Re: tools: Consolidate types.h

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-next>] [day] [month] [year] [list]

Message-ID: <20150506165400.GA9327@redhat.com>
Date:	Wed, 6 May 2015 18:54:00 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Borislav Petkov <bp@...e.de>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Jiri Olsa <jolsa@...nel.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: tools: Consolidate types.h

Hi,

I can't build the kernel after "git pull",

	In file included from /usr/include/asm/types.h:4,
			 from ./tools/include/linux/types.h:9,
			 from ./include/uapi/linux/elf.h:4,
			 from arch/x86/vdso/vdso2c.c:66:
	./include/uapi/asm-generic/int-ll64.h:11:29: error: asm/bitsperlong.h: No such file or directory

I am not 100% sure but it seems that this was broken by
d944c4eebcf4c0d5e5d9728fec110cbf0047ad7f "tools: Consolidate types.h"

Don't we need the patch below? Or should I finally update my (very old)
distro which doesn't have /usr/include/asm/bitsperlong.h ?

Oleg.


diff --git a/arch/x86/vdso/Makefile b/arch/x86/vdso/Makefile
index 275a3a8..e970320 100644
--- a/arch/x86/vdso/Makefile
+++ b/arch/x86/vdso/Makefile
@@ -51,7 +51,7 @@ VDSO_LDFLAGS_vdso.lds = -m64 -Wl,-soname=linux-vdso.so.1 \
 $(obj)/vdso64.so.dbg: $(src)/vdso.lds $(vobjs) FORCE
 	$(call if_changed,vdso)
 
-HOST_EXTRACFLAGS += -I$(srctree)/tools/include -I$(srctree)/include/uapi
+HOST_EXTRACFLAGS += -I$(srctree)/tools/include -I$(srctree)/include/uapi -I$(srctree)/arch/x86/include/uapi
 hostprogs-y			+= vdso2c
 
 quiet_cmd_vdso2c = VDSO2C  $@

--
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/