public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marvin Stodolsky <stodolsk@rcn.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: Re: build -->/usr/src/linux
Date: Sun, 08 Apr 2001 12:30:17 -0500	[thread overview]
Message-ID: <3AD0A029.C17C3EFC@rcn.com> (raw)
In-Reply-To: <3AD079EA.50DA97F3@rcn.com> <20010408161620.A21660@flint.arm.linux.org.uk>

Russell

Thanks for responding.  But I would still like to understand what the
functionality is of the build --> /usr/src/linuc.  Is it dispensable,
once the module tree has been installed? 

Incidentally, per below, my own modutils is current, though some of the
folks using our ltmodem.o compiler/installer kits may indeed need to
update. 
> You need to update your modutils package - there have been a number of
> important bug fixes, including some which allow it to work properly with
> 2.4 kernels.

# insmod -V
insmod version 2.4.2
# grep " # " /usr/src/linux-2.4.3/Documentation/Changes
o  Gnu C                  2.91.66                 # gcc --version
o  Gnu make               3.77                    # make --version
o  binutils               2.9.1.0.25              # ld -v
o  util-linux             2.10o                   # fdformat --version
o  modutils               2.4.2                   # insmod -V
etc.

MarvS


> Russell King wrote:
> 
> On Sun, Apr 08, 2001 at 09:47:06AM -0500, Marvin Stodolsky wrote:
> > It's presence has required some gymnastics, per below, during module
> > installation for the Winmodem driver, ltmodem.o requiring a subsequent
> > "depmod -a"
> 
> You need to update your modutils package - there have been a number of
> important bug fixes, including some which allow it to work properly with
> 2.4 kernels.
> 
> --
> Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
>              http://www.arm.linux.org.uk/personal/aboutme.html

  reply	other threads:[~2001-04-08 17:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9aqmgo$8f6ol$1@fido.engr.sgi.com>
2001-04-08 14:47 ` build -->/usr/src/linux Marvin Stodolsky
2001-04-08 15:16   ` Russell King
2001-04-08 17:30     ` Marvin Stodolsky [this message]
2001-04-08 21:49       ` Miquel van Smoorenburg
2001-04-08 23:01         ` Jamie Lokier
2001-04-09 11:29           ` Miquel van Smoorenburg
2001-04-09 15:02             ` Jamie Lokier
2001-04-09 23:01       ` richard offer
2001-04-10 14:08         ` Jamie Lokier
2001-04-10 16:36           ` richard offer
2001-04-10 16:42             ` Jamie Lokier
2001-04-10 16:52               ` richard offer
2001-04-10 17:04                 ` Jamie Lokier

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=3AD0A029.C17C3EFC@rcn.com \
    --to=stodolsk@rcn.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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