Linux MIPS Architecture development
 help / color / mirror / Atom feed
* module dependency files
@ 2003-10-21 21:22 David Kesselring
  2003-10-21 21:25 ` Jeff Angielski
  0 siblings, 1 reply; 7+ messages in thread
From: David Kesselring @ 2003-10-21 21:22 UTC (permalink / raw)
  To: linux-mips

I have now gotten the modules to build but there is one part of the
process that doesn't work. On my pc I want to build all of the files which
are to be installed on the mips board. I am trying to create the files
which can be copied onto (or into) the redhat 7.3 miniport. "make modules"
works fine. It seems like I need to run "make modules_install" but it
complains about the .o files being the wrong architecture. So the basic
question seems to be how can I run depmod on the pc for mips?
Thanks again.

David Kesselring
Atmel MMC
dkesselr@mmc.atmel.com
919-462-6587

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: module dependency files
  2003-10-21 21:22 module dependency files David Kesselring
@ 2003-10-21 21:25 ` Jeff Angielski
  2003-10-21 21:25   ` Jeff Angielski
  2003-10-21 22:15   ` David Kesselring
  0 siblings, 2 replies; 7+ messages in thread
From: Jeff Angielski @ 2003-10-21 21:25 UTC (permalink / raw)
  To: David Kesselring; +Cc: linux-mips

>From the Linux kernel Makefile...

#
# INSTALL_MOD_PATH specifies a prefix to MODLIB for module directory
# relocations required by build roots.  This is not defined in the
# makefile but the arguement can be passed to make if needed.
#
                                                                                Just set this to the location of your target filesystem when you do the modules_install.

Jeff Angielski
The PTR Group

On Tue, 2003-10-21 at 17:22, David Kesselring wrote:
> I have now gotten the modules to build but there is one part of the
> process that doesn't work. On my pc I want to build all of the files which
> are to be installed on the mips board. I am trying to create the files
> which can be copied onto (or into) the redhat 7.3 miniport. "make modules"
> works fine. It seems like I need to run "make modules_install" but it
> complains about the .o files being the wrong architecture. So the basic
> question seems to be how can I run depmod on the pc for mips?
> Thanks again.
> 
> David Kesselring
> Atmel MMC
> dkesselr@mmc.atmel.com
> 919-462-6587
> 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: module dependency files
  2003-10-21 21:25 ` Jeff Angielski
@ 2003-10-21 21:25   ` Jeff Angielski
  2003-10-21 22:15   ` David Kesselring
  1 sibling, 0 replies; 7+ messages in thread
From: Jeff Angielski @ 2003-10-21 21:25 UTC (permalink / raw)
  To: David Kesselring; +Cc: linux-mips

From the Linux kernel Makefile...

#
# INSTALL_MOD_PATH specifies a prefix to MODLIB for module directory
# relocations required by build roots.  This is not defined in the
# makefile but the arguement can be passed to make if needed.
#
                                                                                Just set this to the location of your target filesystem when you do the modules_install.

Jeff Angielski
The PTR Group

On Tue, 2003-10-21 at 17:22, David Kesselring wrote:
> I have now gotten the modules to build but there is one part of the
> process that doesn't work. On my pc I want to build all of the files which
> are to be installed on the mips board. I am trying to create the files
> which can be copied onto (or into) the redhat 7.3 miniport. "make modules"
> works fine. It seems like I need to run "make modules_install" but it
> complains about the .o files being the wrong architecture. So the basic
> question seems to be how can I run depmod on the pc for mips?
> Thanks again.
> 
> David Kesselring
> Atmel MMC
> dkesselr@mmc.atmel.com
> 919-462-6587
> 

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: module dependency files
  2003-10-21 21:25 ` Jeff Angielski
  2003-10-21 21:25   ` Jeff Angielski
@ 2003-10-21 22:15   ` David Kesselring
  2003-10-22  6:57     ` Jan-Benedict Glaw
  1 sibling, 1 reply; 7+ messages in thread
From: David Kesselring @ 2003-10-21 22:15 UTC (permalink / raw)
  To: Jeff Angielski; +Cc: linux-mips

That's what I did. I defined INSTALL_MOD_PATH as $(TOPDIR)/modules. The
modules get put there but depmod fails.

On 21 Oct 2003, Jeff Angielski wrote:

> >From the Linux kernel Makefile...
>
> #
> # INSTALL_MOD_PATH specifies a prefix to MODLIB for module directory
> # relocations required by build roots.  This is not defined in the
> # makefile but the arguement can be passed to make if needed.
> #
>                                                                                 Just set this to the location of your target filesystem when you do the modules_install.
>
> Jeff Angielski
> The PTR Group
>
> On Tue, 2003-10-21 at 17:22, David Kesselring wrote:
> > I have now gotten the modules to build but there is one part of the
> > process that doesn't work. On my pc I want to build all of the files which
> > are to be installed on the mips board. I am trying to create the files
> > which can be copied onto (or into) the redhat 7.3 miniport. "make modules"
> > works fine. It seems like I need to run "make modules_install" but it
> > complains about the .o files being the wrong architecture. So the basic
> > question seems to be how can I run depmod on the pc for mips?
> > Thanks again.
> >
> > David Kesselring
> > Atmel MMC
> > dkesselr@mmc.atmel.com
> > 919-462-6587
> >
>
>

David Kesselring
Atmel MMC
dkesselr@mmc.atmel.com
919-462-6587

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: module dependency files
  2003-10-21 22:15   ` David Kesselring
@ 2003-10-22  6:57     ` Jan-Benedict Glaw
  2003-10-22  8:02       ` Wolfgang Denk
  0 siblings, 1 reply; 7+ messages in thread
From: Jan-Benedict Glaw @ 2003-10-22  6:57 UTC (permalink / raw)
  To: linux-mips

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Tue, 2003-10-21 18:15:56 -0400, David Kesselring <dkesselr@mmc.atmel.com>
wrote in message <Pine.GSO.4.44.0310211814340.14473-100000@ares.mmc.atmel.com>:
> That's what I did. I defined INSTALL_MOD_PATH as $(TOPDIR)/modules. The
> modules get put there but depmod fails.

depmod works on it's own architecture and I don't recall a way that
would make it work on cross-compiled modules. Maybe you should just copy
over the modules (INSTALL_MOD_PATH is a good start here) and execute
depmod on the target system...

Apart from that, insmod (instead of modprobe) should always work,
though...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: module dependency files
@ 2003-10-22  7:14 Colin.Helliwell
  0 siblings, 0 replies; 7+ messages in thread
From: Colin.Helliwell @ 2003-10-22  7:14 UTC (permalink / raw)
  To: linux-mips


You'd need to do a MIPS cross-compile of modutils, I guess. As an
alternative there is a perl script (depmod.pl) out there that can handle
'foreign' binaries. I haven't had cause to use it on MIPS yet, but have
used it ok PPC. I think it comes with the busybox package.

Col





                                                                                                                                           
                      Jan-Benedict Glaw                                                                                                    
                      <jbglaw@lug-owl.de>          To:       linux-mips@linux-mips.org                                                     
                      Sent by:                     cc:                                                                                     
                      linux-mips-bounce@lin        Subject:  Re: module dependency files                                                   
                      ux-mips.org                                                                                                          
                                                                                                                                           
                                                                                                                                           
                      10/22/03 07:57 AM                                                                                                    
                                                                                                                                           
                                                                                                                                           




On Tue, 2003-10-21 18:15:56 -0400, David Kesselring
<dkesselr@mmc.atmel.com>
wrote in message
<Pine.GSO.4.44.0310211814340.14473-100000@ares.mmc.atmel.com>:
> That's what I did. I defined INSTALL_MOD_PATH as $(TOPDIR)/modules. The
> modules get put there but depmod fails.

depmod works on it's own architecture and I don't recall a way that
would make it work on cross-compiled modules. Maybe you should just copy
over the modules (INSTALL_MOD_PATH is a good start here) and execute
depmod on the target system...

Apart from that, insmod (instead of modprobe) should always work,
though...

MfG, JBG

--
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen
Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM |
TCPA));


<< Attachment removed : attxmd4r.dat >>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: module dependency files
  2003-10-22  6:57     ` Jan-Benedict Glaw
@ 2003-10-22  8:02       ` Wolfgang Denk
  0 siblings, 0 replies; 7+ messages in thread
From: Wolfgang Denk @ 2003-10-22  8:02 UTC (permalink / raw)
  To: Jan-Benedict Glaw; +Cc: linux-mips

In message <20031022065732.GP20846@lug-owl.de> you wrote:
> 
> depmod works on it's own architecture and I don't recall a way that
> would make it work on cross-compiled modules. Maybe you should just copy
> over the modules (INSTALL_MOD_PATH is a good start here) and execute
> depmod on the target system...

Busybox contains a  platform-independend  depmod  perl  script  which
works fine even in a cross development environment.

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
"A witty saying proves nothing."                           - Voltaire

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2003-10-22  8:03 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-10-21 21:22 module dependency files David Kesselring
2003-10-21 21:25 ` Jeff Angielski
2003-10-21 21:25   ` Jeff Angielski
2003-10-21 22:15   ` David Kesselring
2003-10-22  6:57     ` Jan-Benedict Glaw
2003-10-22  8:02       ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-10-22  7:14 Colin.Helliwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox