linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Ing.Gianfranco Morandi" <gianfranco.morandi@euro-studio.it>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: make module_install
Date: Tue, 17 Dec 2002 18:37:39 +0100	[thread overview]
Message-ID: <20021217173744.78C63C6139@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 17 Dec 2002 17:55:33 +0100." <001301c2a5ed$1d546ea0$0700a8c0@pc005>


In message <001301c2a5ed$1d546ea0$0700a8c0@pc005> you wrote:
>
> > make modules_install INSTALL_MOD_PATH=/opt/eldk/ppc_8xx
>
> By doing that I have solved only the 50% of the problem. In fact now the
> files are moved in the right place but the message still exist.

I know. I tend to simply ignore it ;-)

> It seems that the architecture of the ELF files was wrong or the depmod runs
> for an i386 architecture.

The latter is the case: you are running a host-depmod  but  a  cross-
depmod  is  needed.  Feel  free to change the defintiion of DEPMOD in
your top-level makefile to your liking.

IMHO this is overkill, though. For  standard  desktop/server  systems
modules are used to be able to run the same kernel version for a wide
range  of  hardware  configurations;  but the situation is completely
different for embedded systems: modules are  usually  only  used  for
driver  development,  and  then you will manually load and unload the
driver anyway. I will even go so far to say that if you need  to  run
"depmod"  for  your embedded system you should fix your system design
because you are doing something wrong.

Of course, YMMV.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
In theory, there is no difference between  theory  and  practice.  In
practice, however, there is.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2002-12-17 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001301c2a5ed$1d546ea0$0700a8c0@pc005>
2002-12-17 17:37 ` Wolfgang Denk [this message]
2002-12-17 18:12   ` make module_install Marius Groeger
2002-12-17 18:33     ` Wolfgang Denk
     [not found] <NCBBIINEHIPFGJPLBEIFGEEOEAAA.acurtis@onz.com>
2002-12-18 16:11 ` Marius Groeger
     [not found] <002301c2a5fd$918c5fc0$0700a8c0@pc005>
2002-12-17 19:06 ` Wolfgang Denk
2002-12-17 21:10   ` Wolfgang Denk
     [not found] <000701c2a5e5$30b5a660$0700a8c0@pc005>
2002-12-17 16:39 ` Wolfgang Denk

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=20021217173744.78C63C6139@atlas.denx.de \
    --to=wd@denx.de \
    --cc=gianfranco.morandi@euro-studio.it \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).