From: Andrew Morton <akpm@digeo.com>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm9
Date: Sun, 25 May 2003 13:06:01 -0700 [thread overview]
Message-ID: <20030525130601.5a105fa8.akpm@digeo.com> (raw)
In-Reply-To: <3ED0CE0E.4080403@wmich.edu>
Ed Sweetman <ed.sweetman@wmich.edu> wrote:
>
> got this with my current config. Along with other misc gcc 3 warnings.
>
> Compiling with gcc (GCC) 3.3 (Debian)
>
> ld -m elf_i386 -T arch/i386/vmlinux.lds.s
> arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/built-in.o
> --start-group usr/built-in.o arch/i386/kernel/built-in.o
> arch/i386/mm/built-in.o arch/i386/mach-default/built-in.o
> kernel/built-in.o mm/built-in.o fs/built-in.o ipc/built-in.o
> security/built-in.o crypto/built-in.o lib/lib.a arch/i386/lib/lib.a
> drivers/built-in.o sound/built-in.o arch/i386/pci/built-in.o
> net/built-in.o --end-group -o vmlinux
> kernel/built-in.o(.text+0x1708e): In function `free_module':
> : undefined reference to `percpu_modfree'
> kernel/built-in.o(.text+0x17873): In function `load_module':
> : undefined reference to `find_pcpusec'
> kernel/built-in.o(.text+0x179a9): In function `load_module':
> : undefined reference to `percpu_modalloc'
> kernel/built-in.o(.text+0x17c52): In function `load_module':
> : undefined reference to `percpu_modcopy'
> kernel/built-in.o(.text+0x17d3d): In function `load_module':
> : undefined reference to `percpu_modfree'
Well that is strange. The functions are there, inlined, in the right
place.
static inline unsigned int find_pcpusec(Elf_Ehdr *hdr,
Elf_Shdr *sechdrs,
const char *secstrings)
{
return 0;
}
static inline void percpu_modcopy(void *pcpudst, const void *src,
unsigned long size)
{
/* pcpusec should be 0, and size of that section should be 0. */
BUG_ON(size != 0);
}
static inline void percpu_modfree(void *freeme)
{
}
It compiles OK here, uniproc and SMP. Possibly gcc-3.3 has done something
wrong, or differently.
Does your tree build OK with earlier compilers?
next prev parent reply other threads:[~2003-05-25 19:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 11:27 2.5.69-mm9 Andrew Morton
2003-05-25 12:56 ` 2.5.69-mm9 Rudmer van Dijk
2003-05-25 14:07 ` 2.5.69-mm9 Ed Sweetman
2003-05-25 20:06 ` Andrew Morton [this message]
2003-05-25 20:29 ` 2.5.69-mm9 Adrian Bunk
2003-05-25 16:47 ` 2.5.69-mm9 Nicholas Wourms
2003-05-25 17:06 ` 2.5.69-mm9 Adam Kropelin
2003-05-25 20:54 ` 2.5.69-mm9: undefined references to `router_devlist' Adrian Bunk
2003-05-26 13:15 ` Arnaldo Carvalho de Melo
2003-05-27 2:34 ` [PATCH] wanrouter: fix bug introduced by latest namespace fix Arnaldo Carvalho de Melo
2003-05-27 7:08 ` David S. Miller
2003-05-25 21:56 ` 2.5.69-mm9 Felipe Alfaro Solana
2003-05-25 22:48 ` 2.5.69-mm9 Andrew Morton
2003-05-25 23:16 ` 2.5.69-mm9 Neil Brown
2003-05-25 23:19 ` 2.5.69-mm9 Trond Myklebust
2003-05-25 15:19 2.5.69-mm9 Alistair J Strachan
2003-05-25 20:15 ` 2.5.69-mm9 Andrew Morton
2003-05-25 20:35 ` 2.5.69-mm9 Alistair J Strachan
2003-05-25 20:51 ` 2.5.69-mm9 Mike Fedyk
2003-05-25 20:55 ` 2.5.69-mm9 Andrew Morton
[not found] <20030525172746.43b9866d.akpm@digeo.com>
[not found] ` <20030529204324.GF25560@kroah.com>
2003-05-29 23:48 ` 2.5.69-mm9 Alistair J Strachan
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=20030525130601.5a105fa8.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).