From: Keith Owens <kaos@ocs.com.au>
To: Tomasz Motylewski <motyl@stan.chemie.unibas.ch>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: ide-probe.c:400: `rtc_lock' undeclared and /lib/modules/..../build
Date: Tue, 07 Nov 2000 14:24:45 +1100 [thread overview]
Message-ID: <9769.973567485@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 07 Nov 2000 01:20:36 BST." <Pine.LNX.4.21.0011070059120.24007-100000@crds.chemie.unibas.ch>
On Tue, 7 Nov 2000 01:20:36 +0100 (CET),
Tomasz Motylewski <motyl@stan.chemie.unibas.ch> wrote:
>2.2.18pre19:
>And , whose idea was that "make modules_install" should create
>/lib/modules/..../build symlink to the kernel sources?
>It really breakes depmod -a (modutils 2.3.11)(*)
>
>(*) I could find a workaround, but if it hits me, it will hit lots of other
>people not reading linux-kernel regularly. In my opinion upgrading stable
>kernels should work without any modifications to the existing system.
Agreed, I was unhappy that the build symlink was added to 2.2 kernels.
Now you need modutils >= 2.3.14 for 2.2 kernels :(. But nobody asks
me, I'm just the kernel module.[ch] and modutils maintainer.
-
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/
next prev parent reply other threads:[~2000-11-07 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 0:20 ide-probe.c:400: `rtc_lock' undeclared and /lib/modules/..../build Tomasz Motylewski
2000-11-07 0:24 ` Mark Cooke
2000-11-07 3:24 ` Keith Owens [this message]
2000-11-07 12:11 ` Alan Cox
2000-11-07 13:21 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2000-11-08 2:48 Mike A. Harris
2000-11-08 3:59 ` Keith Owens
2000-11-08 8:35 ` Mike A. Harris
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=9769.973567485@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=motyl@stan.chemie.unibas.ch \
/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