From: Jeff Angielski <jeff@theptrgroup.com>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: module dependency files
Date: 21 Oct 2003 17:25:20 -0400 [thread overview]
Message-ID: <1066771519.3289.45.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.44.0310211717110.14194-100000@ares.mmc.atmel.com>
>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
>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Angielski <jeff@theptrgroup.com>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: module dependency files
Date: 21 Oct 2003 17:25:20 -0400 [thread overview]
Message-ID: <1066771519.3289.45.camel@localhost.localdomain> (raw)
Message-ID: <20031021212520.eGBNJWpaod2ceOtj5YLLCJlpXPi2txPUk9_fjhaqFFY@z> (raw)
In-Reply-To: <Pine.GSO.4.44.0310211717110.14194-100000@ares.mmc.atmel.com>
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
>
next prev parent reply other threads:[~2003-10-21 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 21:22 module dependency files David Kesselring
2003-10-21 21:25 ` Jeff Angielski [this message]
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
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=1066771519.3289.45.camel@localhost.localdomain \
--to=jeff@theptrgroup.com \
--cc=dkesselr@mmc.atmel.com \
--cc=linux-mips@linux-mips.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