Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 7 Feb 2001 04:15:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 7 Feb 2001 04:15:37 -0500 Received: from router-100M.swansea.linux.org.uk ([194.168.151.17]:4370 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Wed, 7 Feb 2001 04:15:18 -0500 Subject: Re: PCI-SCI Drivers v1.1-7 released To: jmerkey@vger.timpanogas.org (Jeff V. Merkey) Date: Wed, 7 Feb 2001 09:15:39 +0000 (GMT) Cc: linux-kernel@vger.kernel.org In-Reply-To: <20010206182501.A23454@vger.timpanogas.org> from "Jeff V. Merkey" at Feb 06, 2001 06:25:01 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > always assume a stock kernel layout and will point to > /usr/src/linux/include for modversioned includes and files. You can't assume that. The big problem is right now nobody has set an agreed location for kernel sources, you also cant assume they will be present. Its something the FHS needs to address eventually (where eventually is sooner not later) > Please also note that the RedHat 7.1 Fischer release with > the Linux 2.4.0 kernel will report bogus .modinfo relocation > warnings generated by the assembler while building some .c files > against the kernel source tree. These messages are a due to > severe bugs previously reported in the gcc 2.96 compiler and > assembler on RedHat versions 7.0 and above (the list for gcc 2.96 > keeps growing). Nope. They are due to bugs in the kernel source. The bug in question is intentionally left in the kernel sources to handle issues with older modutils. Keith posted 2.4.x patches to drop support for older modutils and in doing so remove the warning. Alan - 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/