Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265084AbUFRJ3m (ORCPT ); Fri, 18 Jun 2004 05:29:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265082AbUFRJ3T (ORCPT ); Fri, 18 Jun 2004 05:29:19 -0400 Received: from mail.dif.dk ([193.138.115.101]:10135 "EHLO mail.dif.dk") by vger.kernel.org with ESMTP id S265092AbUFRJ25 (ORCPT ); Fri, 18 Jun 2004 05:28:57 -0400 Date: Fri, 18 Jun 2004 11:27:59 +0200 (CEST) From: Jesper Juhl To: Nick Bartos Cc: linux-kernel@vger.kernel.org Subject: Re: Using kernel headers that are not for the running kernel In-Reply-To: <53712.192.168.1.12.1087514884.squirrel@192.168.1.12> Message-ID: References: <53712.192.168.1.12.1087514884.squirrel@192.168.1.12> 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 Content-Length: 815 Lines: 26 On Thu, 17 Jun 2004, Nick Bartos wrote: > I have a little distro that I am trying to upgrade to 2.6.x. > > The problem is that when I use the headers for 2.6.x, glibc 2.2.5 won't > compile. Eventually I want to upgrade glibc/gcc, but not at the moment. > If I use the headers from 2.4.26 for the system, but just compile the > 2.6.7 kernel, things do compile fine for everything. > [snip] > > Comments? > - I think this covers the issues you are having pretty well : http://www.linuxmafia.com/faq/Kernel/usr-src-linux-symlink.html -- Jesper Juhl - 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/