From: Sam Ravnborg <sam@ravnborg.org>
To: Hollis Blanchard <hollisb@us.ibm.com>, rusty@rustcorp.com.au
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: cross-depmod?
Date: Fri, 6 Aug 2004 17:42:11 +0200 [thread overview]
Message-ID: <20040806154211.GB7331@mars.ravnborg.org> (raw)
In-Reply-To: <1091742716.28466.27.camel@localhost>
On Thu, Aug 05, 2004 at 04:51:56PM -0500, Hollis Blanchard wrote:
> Hi Sam, would you take a patch like this:
>
> --- 1.509/Makefile Tue Aug 3 16:11:35 2004
> +++ edited/Makefile Thu Aug 5 17:12:07 2004
> @@ -790,7 +790,11 @@
> endif
> .PHONY: _modinst_post
> _modinst_post: _modinst_
> - if [ -r System.map ]; then $(DEPMOD) -ae -F System.map $(depmod_opts) $(KERNELRELEASE); fi
> + if [ -z "$(CROSS_COMPILE)" -o "$(DEPMOD)" != "/sbin/depmod" ] ; then \
> + if [ -r System.map ]; then \
> + $(DEPMOD) -ae -F System.map $(depmod_opts) $(KERNELRELEASE); \
> + fi \
> + fi
>
> else # CONFIG_MODULES
>
> (I don't like hardcoding /sbin/depmod; this is just for conversation.)
>
> My problem is that I cross-build my kernels, and 'make rpm' is very
> unhappy when it can't use depmod. I know that I can do 'make
> DEPMOD=/bin/true rpm', but can't we figure that out automatically?
I assume the problem arises from the fact that depmod are only capable of
reading elf files for the host it is compiled for.
OK, took a look at depmod.
It handles both 32 and 64 bit but assumes same endian.
Rusty: Would it make sense to extend module-init-tools to support
endian as specified in elf file?
Sam
next prev parent reply other threads:[~2004-08-06 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 21:51 cross-depmod? Hollis Blanchard
2004-08-06 8:40 ` cross-depmod? David Vrabel
2004-08-06 13:45 ` cross-depmod? Geert Uytterhoeven
2004-08-06 15:17 ` cross-depmod? Sam Ravnborg
2004-08-06 15:42 ` Sam Ravnborg [this message]
2004-08-08 23:05 ` cross-depmod? Rusty Russell
2004-08-09 6:15 ` cross-depmod? Greg KH
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=20040806154211.GB7331@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hollisb@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®