From: Daniel Ann <ktdann@gmail.com>
To: Rupesh S <rupeshs@myw.ltindia.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Issue with running depmod after cross compiling
Date: Wed, 3 Aug 2005 17:49:55 +0900 [thread overview]
Message-ID: <9b7ca65705080301497740d901@mail.gmail.com> (raw)
In-Reply-To: <s2f08948.038@EMAIL>
Rupesh,
I've tried it with module-init-tools version 3.2-pre8 (since it was
latest), it works like a charm. Thanks.
On 8/3/05, Rupesh S <rupeshs@myw.ltindia.com> wrote:
> Daniel,
>=20
> Assuming your kernel is 2.6 based, you might want to try module-init-tool=
s version 3.2-pre7. Also, it would be better to have the existing depmod re=
named as depmod.old. This is for the new depmod to use in case it fails to =
execute.
>=20
> --
> Rupesh S
>=20
> >>> Daniel Ann <ktdann@gmail.com> 08/03/05 06:57AM >>>
> Hey folks,
>=20
> For certain, I understand why running make module_install fails if I
> run it after cross compiling the kernel+module.
> What I'm doing now is, I've just commented out the bit in Makefile
> (where it exec's depmod), and everythings cool.
>=20
> BUT, problem with this method is, I get none of the module.dep and
> many related files for auto loading of module.
>=20
> What would be considered reasonable if I was to solve this ?
>=20
> Thanks for your thought on this in advance.
>=20
> --
> Daniel
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
--=20
Daniel
next parent reply other threads:[~2005-08-03 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s2f08948.038@EMAIL>
2005-08-03 8:49 ` Daniel Ann [this message]
2005-08-03 3:36 Issue with running depmod after cross compiling Rupesh S
-- strict thread matches above, loose matches on Subject: below --
2005-08-03 1:27 Daniel Ann
2005-08-03 5:55 ` Matej Kupljen
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=9b7ca65705080301497740d901@mail.gmail.com \
--to=ktdann@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rupeshs@myw.ltindia.com \
/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).