From: "Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>
To: linux-kernel@vger.kernel.org
Subject: _proxy_pda still makes linking modules fail
Date: Thu, 08 Mar 2007 01:57:59 +0100 [thread overview]
Message-ID: <1173315479.12472.9.camel@qrnik> (raw)
This is linux-2.6.20.1 with lots of patches from PLD Linux (I believe
the patches don't affect the issue), compiled with gcc-4.1.2 and
binutils-2.17.50.0.12 on x86.
Linking the kernel causes warnings:
RELOCS arch/i386/boot/compressed/vmlinux.relocs
WARNING: Absolute relocations present
Offset Info Type Sym.Value Sym.Name
c0102cd7 00450601 R_386_32 00000000 _proxy_pda
c0104922 00450601 R_386_32 00000000 _proxy_pda
c0110623 00450601 R_386_32 00000000 _proxy_pda
c011bdc5 00450601 R_386_32 00000000 _proxy_pda
c0125fc1 00450601 R_386_32 00000000 _proxy_pda
c016c0e2 00450601 R_386_32 00000000 _proxy_pda
c016c2ab 00450601 R_386_32 00000000 _proxy_pda
c016f91c 00450601 R_386_32 00000000 _proxy_pda
Linking modules fails:
Building modules, stage 2.
MODPOST 1970 modules
WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params from .text between '_text' (at offset 0xc0100036) and 'checkCPUtype'
WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params from .text between '_text' (at offset 0xc0100044) and 'checkCPUtype'
WARNING: vmlinux - Section mismatch: reference to .init.data:init_pg_tables_end from .text between '_text' (at offset 0xc01000a6) and 'checkCPUtype'
[...]
WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .paravirtprobe between '__start_paravirtprobe' (at offset 0xc03bc660) and '__stop_paravirtprobe'
WARNING: "_proxy_pda" [fs/nfsd/nfsd.ko] undefined!
WARNING: "_proxy_pda" [fs/lockd/lockd.ko] undefined!
WARNING: "_proxy_pda" [fs/fuse/fuse.ko] undefined!
WARNING: "_proxy_pda" [drivers/net/irda/toim3232-sir.ko] undefined!
WARNING: "_proxy_pda" [drivers/media/video/saa5249.ko] undefined!
make[1]: *** [__modpost] Error 1
I've heard that it now builds with gcc-4.2.0 snapshots. This is strange:
if the problem has been fixed for gcc-4.2.0, why doesn't it work for
gcc-4.1.2? arch/i386/kernel/vmlinux.lds.S does contain _proxy_pda = 0;
I'm not subscribed to the list.
--
__("< Marcin Kowalczyk
\__/ qrczak@knm.org.pl
^^ http://qrnik.knm.org.pl/~qrczak/
next reply other threads:[~2007-03-08 1:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 0:57 Marcin 'Qrczak' Kowalczyk [this message]
2007-03-10 15:03 ` _proxy_pda still makes linking modules fail Adrian Bunk
2007-03-11 14:06 ` Marcin 'Qrczak' Kowalczyk
2007-03-12 1:19 ` Andi Kleen
2007-03-12 0:25 ` Jeremy Fitzhardinge
2007-03-12 9:48 ` Andi Kleen
2007-03-12 14:45 ` Jeremy Fitzhardinge
2007-03-12 15:45 ` Andi Kleen
2007-03-12 21:58 ` Rusty Russell
2007-03-13 6:23 ` Rusty Russell
2007-03-13 9:04 ` Paul Mackerras
2007-03-13 15:31 ` Jeremy Fitzhardinge
2007-03-13 23:50 ` Paul Mackerras
2007-03-14 1:12 ` Rusty Russell
2007-03-13 15:57 ` Andi Kleen
2007-03-14 2:17 ` Rusty Russell
2007-03-12 18:47 ` Marcin 'Qrczak' Kowalczyk
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=1173315479.12472.9.camel@qrnik \
--to=qrczak@knm.org.pl \
--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