From: "Randy.Dunlap" <randy.dunlap@verizon.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: daniel@zonque.org, akpm <akpm@osdl.org>
Subject: Re: [PATCH] 2.6.4-rc2: scripts/modpost.c
Date: Thu, 4 Mar 2004 21:24:40 -0800 [thread overview]
Message-ID: <20040304212440.30fc8674.randy.dunlap@verizon.net> (raw)
In-Reply-To: <20040304172923.6045760e.rddunlap@osdl.org>
| (This is is a repost - now with a patch for 2.6.4-rc2).
|
| Hi,
|
| as I found out, it's impossible to use the build-chain tool scripts/modpost
| of the 2.6 kernel series to externally build modules from a directory that
| contains the character sequence '.o'. Weird things happen if you try to do
| so.
|
| With a directory structure like on my system here, building the current DVB
| driver in '/home/daniel/cvs.linuxtv.org/dvb-kernel/build-2.6i/' generates a
| file called '/home/daniel/cvs.linuxtv.mod.c' since modpost cuts every
| filename string at the first occurence of '.o', not only the 'trailing .o',
| as the comment says.
The comment and code certainly don't match, and your patch makes sense
to me. However, I can't reproduce the problem that you describe.
I built the kernel image and modules in "www.osdl.org/264rc2/build1",
and all *.mod.c and *.ko ended up there with no problems.
Then I modified modpost.c (from 2.6.4-rc1, without your patch) to
print the "stripped" module names (without the trailing ".o")
and saw a list like this:
modpost: stripped mod.name=[fs/jfs/jfs]
so where are the parent directory names that are causing problems
for you coming from?
Andrew, I applied the patch and didn't have any problems with
'make allyesconfig' like you alluded to.
| Here's the patch for 2.6.4-rc2:
|
|
| --- linux-2.6.4-rc2.orig/scripts/modpost.c 2004-03-04 11:40:21.000000000 +0100
| +++ linux-2.6.4-rc2/scripts/modpost.c 2004-03-04 11:23:08.000000000 +0100
| @@ -63,16 +63,16 @@
| new_module(char *modname)
| {
| struct module *mod;
| - char *p;
| + int len;
|
| mod = NOFAIL(malloc(sizeof(*mod)));
| memset(mod, 0, sizeof(*mod));
| mod->name = NOFAIL(strdup(modname));
|
| /* strip trailing .o */
| - p = strstr(mod->name, ".o");
| - if (p)
| - *p = 0;
| + len = strlen(mod->name);
| + if (len > 2 && mod->name[len-2] == '.' && mod->name[len-1] == 'o')
| + mod->name[len-2] = 0;
|
| /* add to list */
| mod->next = modules;
--
~Randy
next parent reply other threads:[~2004-03-05 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040304172923.6045760e.rddunlap@osdl.org>
2004-03-05 5:24 ` Randy.Dunlap [this message]
2004-03-05 6:16 ` Tony Breeds
2004-03-05 12:36 ` Daniel Mack
2004-03-04 11:37 Daniel Mack
2004-03-04 11:54 ` Andrew Morton
2004-03-04 13:01 ` Daniel Mack
2004-03-11 0:40 ` Rusty Russell
2004-03-11 5:53 ` Sam Ravnborg
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=20040304212440.30fc8674.randy.dunlap@verizon.net \
--to=randy.dunlap@verizon.net \
--cc=akpm@osdl.org \
--cc=daniel@zonque.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®