Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 14 Dec 2000 20:36:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 14 Dec 2000 20:36:03 -0500 Received: from leibniz.math.psu.edu ([146.186.130.2]:61852 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Thu, 14 Dec 2000 20:36:02 -0500 Date: Thu, 14 Dec 2000 20:05:34 -0500 (EST) From: Alexander Viro To: David Riley cc: Alan Cox , Miquel van Smoorenburg , linux-kernel@vger.kernel.org Subject: Re: Linus's include file strategy redux In-Reply-To: <3A396C39.798939C5@the-rileys.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 14 Dec 2000, David Riley wrote: > Alexander Viro wrote: > > > > Actually, I suspect that quite a few of us had done that since long - > > IIRC I've got burned on 1.2/1.3 and decided that I had enough. Bugger if I > > remember what exactly it was - ISTR that it was restore(8) built with > > 1.3. headers and playing funny games on 1.2, but it might be > > something else... > > So then what's the correct header tree to put in /usr/include/linux? I > could use the stock 2.2.14-patched headers that came with the dist, but > how often does it need to be updated? Or should I use the latest 2.2? Whatever your libc was built against. It shouldn't matter that much, but when shit hits the fan... you really don't want to be there. Look at it that way: you don't want to build some object files with one set of headers, some - with another and link them together. Now, s/some object files/libc/. With a minimal luck you will be OK, but it's easier not to ask for trouble in the first place. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/