public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI-SCI Drivers v1.1-7 released
Date: Wed, 7 Feb 2001 11:13:45 -0700	[thread overview]
Message-ID: <20010207111345.D27089@vger.timpanogas.org> (raw)
In-Reply-To: <20010206182501.A23454@vger.timpanogas.org> <E14QQhS-0008Ar-00@the-village.bc.nu>
In-Reply-To: <E14QQhS-0008Ar-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 07, 2001 at 09:15:39AM +0000

On Wed, Feb 07, 2001 at 09:15:39AM +0000, Alan Cox wrote:
> > 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.
> 

I need a way from the RPM utility to determine this without writing some 
huge ugly bash script.  The 7.1 release is not putting it where uname 
will return the correct name string.

> 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

Hummm.  Where are the patches for 2.4 to correct this?  They are not posted
with the 7.1 release.  They need to be.  The compiler not supporting 
#ident for CVS is a show stopper, and needs correcting ASAP.  How can 
someone use CVS properly with this, Alan?

:-)

Jeff

-
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/

  reply	other threads:[~2001-02-07 17:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07  1:25 PCI-SCI Drivers v1.1-7 released Jeff V. Merkey
2001-02-07  2:06 ` Jeff V. Merkey
2001-02-07  2:07   ` [OT] " Gregory Maxwell
2001-02-07 18:08     ` Jeff V. Merkey
2001-02-07 17:32       ` Jakub Jelinek
2001-02-07 18:31         ` Jeff V. Merkey
2001-02-07 18:37           ` Tim Wright
2001-02-07 20:14             ` Jeff V. Merkey
2001-02-07 19:22               ` Alan Cox
2001-02-07 20:24                 ` Jeff V. Merkey
2001-02-07 20:35                   ` PCI-SCI Build Problems on RedHat 7.1 Jeff V. Merkey
2001-02-07 19:52                     ` Larry
2001-02-07  9:01   ` PCI-SCI Drivers v1.1-7 released David Howells
2001-02-07 18:10     ` Jeff V. Merkey
2001-02-07  9:22   ` Alan Cox
2001-02-07 18:19     ` Jeff V. Merkey
2001-02-07 19:06       ` Alan Cox
2001-02-07 20:03         ` Jeff V. Merkey
2001-02-07 19:12           ` Alan Cox
2001-02-07  9:15 ` Alan Cox
2001-02-07 18:13   ` Jeff V. Merkey [this message]
2001-02-07 19:02     ` Alan Cox
2001-02-07 20:02       ` Jeff V. Merkey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010207111345.D27089@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox