linux-kernel - Re: [klibc] [PATCH] build: Define __EXPORTED_HEADER_

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]

Message-Id: <201102272107.48934.arnd@arndb.de>
Date:	Sun, 27 Feb 2011 21:07:48 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	klibc@...or.com
Cc:	Sam Ravnborg <sam@...nborg.org>, Mike Waychison <mikew@...gle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [klibc] [PATCH] build: Define __EXPORTED_HEADER__

On Saturday 26 February 2011, Sam Ravnborg wrote:
> > 
> > What you are proposing seems to me like a step towards giving up on
> > this noble goal :(
> You seem to be confusing something here. Even if klibc is one day
> included in the kernel source then we should continue to use
> the headers generated using "make headers_install" for building klibc.

Absolutely, yes.

Mike, just think of the generated header files as intermediate files
required for building, just like the .o files that are use to build
the library.

	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/