DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=google.com; s=beta;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=gjouWUsKteMsOz2219Mc3t8v+Mckg8V2GYKmPCxm2grb1pe3ZaqJiXr8dPTUWMTU7R
         InNBXETpDGji3CPYNXCw==
MIME-Version: 1.0
In-Reply-To: <201102272107.48934.arnd@arndb.de>
References: <1298506377-16796-1-git-send-email-mikew@google.com>
 <AANLkTi=8S4=vEUNHR6zD8d1or6BS_o9k4nPg4he+Kik2@mail.gmail.com>
 <20110226222255.GB24028@merkur.ravnborg.org> <201102272107.48934.arnd@arndb.de>
From: Mike Waychison <mikew@google.com>
Date: Sun, 27 Feb 2011 15:54:47 -0800
Message-ID: <AANLkTikijjZwQp6Fer9TqRqQe=2WhSCPcDv5mczcGD8g@mail.gmail.com>
Subject: Re: [klibc] [PATCH] build: Define __EXPORTED_HEADER__
To: Arnd Bergmann <arnd@arndb.de>
Cc: klibc@zytor.com, Sam Ravnborg <sam@ravnborg.org>,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1015
Lines: 23

On Sun, Feb 27, 2011 at 12:07 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> 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.

How is one expected to test if the files should be rebuild or not?
Forcing a headers_install as part of a build will cause the entire
userland to be rebuilt.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/