From: Martin Schlemmer <azarah@gentoo.org>
To: Valdis.Kletnieks@vt.edu
Cc: Boszormenyi Zoltan <zboszor@freemail.hu>,
Andrew Morton <akpm@osdl.org>, KML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test4-mm3
Date: Mon, 01 Sep 2003 22:23:30 +0200 [thread overview]
Message-ID: <1062447809.5275.7.camel@nosferatu.lan> (raw)
In-Reply-To: <200308291553.h7TFrcGG009390@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
On Fri, 2003-08-29 at 17:53, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 29 Aug 2003 16:55:47 +0200, Martin Schlemmer said:
>
> > Cannot think of one that is known. An quick solution
> > your (and not RH) side, might be something like below.
>
> What about something like this instead? I tested it with the module-init-tools
> and stock RH9 depmods...
>
> Only complain if the depmod actually fails:
>
> --- Makefile.hold 2003-08-27 01:52:20.000000000 -0400
> +++ Makefile 2003-08-29 11:52:15.542286300 -0400
> @@ -209,7 +209,7 @@
> RPM := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \
> else echo rpm; fi)
> GENKSYMS = scripts/genksyms/genksyms
> -DEPMOD = /sbin/depmod
> +DEPMOD = /sbin/depmod.old
> KALLSYMS = scripts/kallsyms
> PERL = perl
> CHECK = sparse
> @@ -612,7 +612,14 @@
> endif
> .PHONY: _modinst_post
> _modinst_post: _modinst_
> - if [ -r System.map ]; then $(DEPMOD) -ae -F System.map $(depmod_opts) $(KERNELRELEASE); fi
> + @if [ -r System.map ]; then \
> + if ! $(DEPMOD) -ae -F System.map $(depmod_opts) $(KERNELRELEASE) ; then \
> + echo "*** Depmod failed!!!"; \
> + echo "*** You may need to install a current version of module-init-tools"; \
> + echo "*** See http://www.codemonkey.org.uk/post-halloween-2.5.txt"; \
> + exit 1; \
> + fi \
> + fi
>
> else # CONFIG_MODULES
Hmm, this will only work with RH based systems (not using here). I
think the best way is how Andrew did it to just warn if depmod fails.
You may agree to disagree if need be :)
Regards,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-01 20:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 9:54 2.6.0-test4-mm3 Boszormenyi Zoltan
2003-08-29 12:52 ` 2.6.0-test4-mm3 Bas Mevissen
2003-08-29 13:00 ` 2.6.0-test4-mm3 Valdis.Kletnieks
[not found] ` <1062168946.19599.114.camel@workshop.saharacpt.lan>
2003-08-30 7:35 ` 2.6.0-test4-mm3 Martin Schlemmer
[not found] ` <200308291553.h7TFrcGG009390@turing-police.cc.vt.edu>
2003-09-01 20:23 ` Martin Schlemmer [this message]
2003-09-01 20:34 ` 2.6.0-test4-mm3 Sam Ravnborg
2003-09-01 23:52 ` 2.6.0-test4-mm3 Valdis.Kletnieks
2003-09-02 4:14 ` 2.6.0-test4-mm3 Martin Schlemmer
2003-09-02 14:31 ` 2.6.0-test4-mm3 Valdis.Kletnieks
2003-08-29 15:35 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 16:22 ` 2.6.0-test4-mm3 Valdis.Kletnieks
2003-08-29 16:27 ` 2.6.0-test4-mm3 Cliff White
2003-08-29 16:34 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-30 6:16 ` 2.6.0-test4-mm3 Martin Schlemmer
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 6:56 2.6.0-test4-mm3 Andrew Morton
2003-08-29 7:45 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:42 ` 2.6.0-test4-mm3 Ed Sweetman
2003-08-29 15:57 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:59 ` 2.6.0-test4-mm3 Felipe Alfaro Solana
2003-09-10 18:53 ` 2.6.0-test4-mm3 Mike Fedyk
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=1062447809.5275.7.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@freemail.hu \
/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