From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: motyl@stan.chemie.unibas.ch (Tomasz Motylewski),
linux-kernel@vger.kernel.org
Subject: Re: ide-probe.c:400: `rtc_lock' undeclared and /lib/modules/..../build
Date: Wed, 08 Nov 2000 00:21:22 +1100 [thread overview]
Message-ID: <13554.973603282@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 07 Nov 2000 12:11:57 -0000." <E13t7ba-0007KF-00@the-village.bc.nu>
On Tue, 7 Nov 2000 12:11:57 +0000 (GMT),
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> 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.
>
>Actually they do. I agree that it wants sorting. Im just wondering what the
>best approach is - maybe check modutils rev and only add the link if its high
>enough ?
Against 2.2.18-pre19, only create build symlink if insmod exists and
has version >= 2.3.14.
Index: 18-pre19.1/Makefile
--- 18-pre19.1/Makefile Sat, 04 Nov 2000 21:35:33 +1100 kaos (linux-2.2/G/b/14_Makefile 1.3.2.2.1.1.1.5.1.3.6.1.5.1.1.1.1.16.1.4 644)
+++ 18-pre19.1(w)/Makefile Wed, 08 Nov 2000 00:13:19 +1100 kaos (linux-2.2/G/b/14_Makefile 1.3.2.2.1.1.1.5.1.3.6.1.5.1.1.1.1.16.1.4 644)
@@ -335,6 +335,7 @@ modules_install:
MODLIB=$(INSTALL_MOD_PATH)/lib/modules/$(KERNELRELEASE); \
mkdir -p $$MODLIB; \
rm -f $$MODLIB/build; \
+ [ `/sbin/insmod -V 2>&1 | awk '/^insmod version /{split($3, a, /\./); printf "%d%03d%03d\n", a[1], a[2], a[3];}'`0 -ge 20030140 ] && \
ln -s `pwd` $$MODLIB/build; \
cd modules; \
MODULES=""; \
-
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 13:21 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
2000-11-07 12:11 ` Alan Cox
2000-11-07 13:21 ` Keith Owens [this message]
-- 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=13554.973603282@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.