From: Michael Grimborounis <mgry@intracom.gr>
To: t.vanremortel@ha.be
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: RTAI module install problem
Date: Wed, 14 May 2003 13:11:29 +0300 [thread overview]
Message-ID: <3EC21651.FA433F3B@intracom.gr> (raw)
In-Reply-To: 1052901595.7115.5.camel@toni
Hi,
Try googling arround for depmod.pl by David Schleef, Erik Andersen and
Stuart Hughes. This is a Perl script you can run on your host system
(sort of a cross-platform depmod.) You will have to modify your makefile
to use that instead of depmod. I get some warnings from it, but
otherwise it works just fine for me. HTH.
Bye,
Michael
Toni Van Remortel wrote:
>
> Hi all.
>
> I'll first tell you in short what I use.
>
> Kernel: linuxppc_2_4_devel (from CVS on may 7th 2003)
> RTAI Patch: ppc_devel_patch_2003_05_04_1125
> Patch went perfect.
>
> Cross-compiler: ELDK ppc_4xx
> Target: EP405
> Host: x86
> INSTALL_MOD_PATH: /tmp/rmdisk_large
>
> Config and vmlinux-compile don't give errors, RTAI is enabled.
> Modules compile OK.
> When installing the modules, I get this error:
>
> cd /tmp/rmdisk_large/lib/modules/2.4.20-rthal5; \
> mkdir -p pcmcia; \
> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{}
> pcmcia
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b
> /tmp/rmdisk_large -r 2.4.20-rthal5; fi
> depmod: ELF file
> /tmp/rmdisk_large/lib/modules/2.4.20-rthal5/kernel/drivers/i2c/i2c-core.o not for this architecture
> depmod: ELF file
> /tmp/rmdisk_large/lib/modules/2.4.20-rthal5/kernel/drivers/i2c/i2c-dev.o
> not for this architecture
> depmod: ELF file
> /tmp/rmdisk_large/lib/modules/2.4.20-rthal5/kernel/drivers/i2c/i2c-proc.o not for this architecture
> ...
> depmod: ELF file
> /tmp/rmdisk_large/lib/modules/2.4.20-rthal5/kernel/net/ipv4/netfilter/iptable_filter.o not for this architecture
> depmod: ELF file
> /tmp/rmdisk_large/lib/modules/2.4.20-rthal5/kernel/net/ipv4/netfilter/iptable_nat.o not for this architecture
> make: *** [_modinst_post] Error 1
>
> OK, this tells me that I'm using a somewhat wrong architecture (probably
> wrong configured).
> Does anybody know how I can solve this?
>
> Thnx.
> --
> Toni Van Remortel <t.vanremortel@ha.be>
> D-science lab
>
--
Michael G. Grimborounis <mgry@intracom.gr>
Intracom S.A.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-05-14 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 8:39 RTAI module install problem Toni Van Remortel
2003-05-14 9:07 ` wolfgang.grandegger
2003-05-14 9:36 ` Alex Zeffertt
2003-05-14 9:37 ` Wolfgang Denk
2003-05-14 10:11 ` Michael Grimborounis [this message]
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=3EC21651.FA433F3B@intracom.gr \
--to=mgry@intracom.gr \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=t.vanremortel@ha.be \
/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).