LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Compiling with 2.6.25-rc2 with binutils 2.17 fails?
@ 2008-02-16 23:27 Rob Landley
2008-02-17 0:04 ` Jan Engelhardt
2008-02-18 3:09 ` Roland McGrath
0 siblings, 2 replies; 7+ messages in thread
From: Rob Landley @ 2008-02-16 23:27 UTC (permalink / raw)
To: linux-kernel
Is anybody else having trouble compiling the kernel with binutils 2.17?
The build does this:
> VDSOSYM arch/x86/vdso/vdso32-syms.lds
> --- - Fri Feb 15 23:38:41 2008
> +++ arch/x86/vdso/vdso32-int80-syms.lds Fri Feb 15 23:38:41 2008
> @@ -0,0 +1,5 @@
> +VDSO32_PRELINK = 0x0;
> +VDSO32_rt_sigreturn = 0x040c;
> +VDSO32_sigreturn = 0x0400;
> +VDSO32_vsyscall = 0x0414;
> +VDSO32_vsyscall_eh_frame_size = 0x040;
> make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1
> make: *** [arch/x86/vdso] Error 2
> make: *** Waiting for unfinished jobs....
Still trying to track down why, but it works on a toolchain built from
binutils 2.18 and gcc 4.1.3, but not with a toolchain from binutils 2.17 and
gcc 4.1.2. And considering where it's failing...
If binutils 2.18 is the only version that now builds the kernel, could we
update Documentaiton/Changes to say that instead of 2.12?
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Compiling with 2.6.25-rc2 with binutils 2.17 fails?
2008-02-16 23:27 Compiling with 2.6.25-rc2 with binutils 2.17 fails? Rob Landley
@ 2008-02-17 0:04 ` Jan Engelhardt
2008-02-18 3:09 ` Roland McGrath
1 sibling, 0 replies; 7+ messages in thread
From: Jan Engelhardt @ 2008-02-17 0:04 UTC (permalink / raw)
To: Rob Landley; +Cc: linux-kernel
On Feb 16 2008 17:27, Rob Landley wrote:
>The build does this:
>> VDSOSYM arch/x86/vdso/vdso32-syms.lds
>> --- - Fri Feb 15 23:38:41 2008
>> +++ arch/x86/vdso/vdso32-int80-syms.lds Fri Feb 15 23:38:41 2008
>> @@ -0,0 +1,5 @@
>> +VDSO32_PRELINK = 0x0;
>> +VDSO32_rt_sigreturn = 0x040c;
>> +VDSO32_sigreturn = 0x0400;
>> +VDSO32_vsyscall = 0x0414;
>> +VDSO32_vsyscall_eh_frame_size = 0x040;
>> make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1
>> make: *** [arch/x86/vdso] Error 2
>> make: *** Waiting for unfinished jobs....
>
>Still trying to track down why, but it works on a toolchain built from
>binutils 2.18 and gcc 4.1.3, but not with a toolchain from binutils 2.17 and
>gcc 4.1.2. And considering where it's failing...
>
>If binutils 2.18 is the only version that now builds the kernel, could we
>update Documentaiton/Changes to say that instead of 2.12?
I have, as part of opensuse, binutils 2.17.50 and gcc 4.2.1 and that
works fine.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Compiling with 2.6.25-rc2 with binutils 2.17 fails?
2008-02-16 23:27 Compiling with 2.6.25-rc2 with binutils 2.17 fails? Rob Landley
2008-02-17 0:04 ` Jan Engelhardt
@ 2008-02-18 3:09 ` Roland McGrath
2008-02-18 10:39 ` Rob Landley
1 sibling, 1 reply; 7+ messages in thread
From: Roland McGrath @ 2008-02-18 3:09 UTC (permalink / raw)
To: Rob Landley; +Cc: linux-kernel
> Still trying to track down why, but it works on a toolchain built from
> binutils 2.18 and gcc 4.1.3, but not with a toolchain from binutils 2.17 and
> gcc 4.1.2. And considering where it's failing...
I don't think the vdso magic should require so new a binutils. Please try
to figure out which of the steps is producing different results between the
two tool setups.
Thanks,
Roland
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Compiling with 2.6.25-rc2 with binutils 2.17 fails?
2008-02-18 3:09 ` Roland McGrath
@ 2008-02-18 10:39 ` Rob Landley
2008-02-18 18:40 ` Roland McGrath
0 siblings, 1 reply; 7+ messages in thread
From: Rob Landley @ 2008-02-18 10:39 UTC (permalink / raw)
To: Roland McGrath; +Cc: linux-kernel
On Sunday 17 February 2008 21:09:10 Roland McGrath wrote:
> > Still trying to track down why, but it works on a toolchain built from
> > binutils 2.18 and gcc 4.1.3, but not with a toolchain from binutils 2.17
> > and gcc 4.1.2. And considering where it's failing...
>
> I don't think the vdso magic should require so new a binutils. Please try
> to figure out which of the steps is producing different results between the
> two tool setups.
I'm poking at it. Something in my cross compiling setup is driving this bit
screwy:
i686-nm arch/x86/vdso/vdso32-sysenter.so.dbg |
sed -n -e 's/^00*/0/' -e 's/^\([0-9a-fA-F]*\) . \(VDSO[a-zA-Z0-9_]*\)$/ =
0x;/p' | LC_ALL=C sort > arch/x86/vdso/vdso32-sysenter-syms.lds
if LC_ALL=C sort -u arch/x86/vdso/vdso32-int80-syms.lds
arch/x86/vdso/vdso32-sysenter-syms.lds > arch/x86/vdso/.tmp_vdso32-syms.lds
&& if grep -q VDSO32_SYSENTER_RETURN arch/x86/vdso/vdso32-int80-syms.lds;
then diff -u arch/x86/vdso/.tmp_vdso32-syms.lds
arch/x86/vdso/vdso32-int80-syms.lds; else sed /VDSO32_SYSENTER_RETURN/d
arch/x86/vdso/.tmp_vdso32-syms.lds | diff -u -
arch/x86/vdso/vdso32-int80-syms.lds; fi && if grep -q VDSO32_SYSENTER_RETURN
arch/x86/vdso/vdso32-sysenter-syms.lds; then diff -u
arch/x86/vdso/.tmp_vdso32-syms.lds arch/x86/vdso/vdso32-sysenter-syms.lds;
else sed /VDSO32_SYSENTER_RETURN/d arch/x86/vdso/.tmp_vdso32-syms.lds |
diff -u - arch/x86/vdso/vdso32-sysenter-syms.lds; fi && : ; then mv -f
arch/x86/vdso/.tmp_vdso32-syms.lds arch/x86/vdso/vdso32-syms.lds; else rm -f
arch/x86/vdso/.tmp_vdso32-syms.lds; exit 1; fi
--- - Sun Feb 17 20:24:03 2008
+++ arch/x86/vdso/vdso32-int80-syms.lds Sun Feb 17 20:24:03 2008
@@ -0,0 +1,5 @@
+VDSO32_PRELINK = 0x0;
+VDSO32_rt_sigreturn = 0x040c;
+VDSO32_sigreturn = 0x0400;
+VDSO32_vsyscall = 0x0414;
+VDSO32_vsyscall_eh_frame_size = 0x040;
make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1
make: *** [arch/x86/vdso] Error 2
If binutils is involved, it's due to i686-nm...
I'm still trying to puzzle out the "if thing && thing &&:; then" syntax above.
Never encountered that one before... A colon? I'll try to bang on it some
more tomorrow, it's gone 4am on me...
> Thanks,
> Roland
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Compiling with 2.6.25-rc2 with binutils 2.17 fails?
2008-02-18 10:39 ` Rob Landley
@ 2008-02-18 18:40 ` Roland McGrath
2008-02-18 21:53 ` Rob Landley
0 siblings, 1 reply; 7+ messages in thread
From: Roland McGrath @ 2008-02-18 18:40 UTC (permalink / raw)
To: Rob Landley; +Cc: linux-kernel
> I'm poking at it. Something in my cross compiling setup is driving this bit
> screwy:
>
> i686-nm arch/x86/vdso/vdso32-sysenter.so.dbg |
Show me the output of just this.
> sed -n -e 's/^00*/0/' -e 's/^\([0-9a-fA-F]*\) . \(VDSO[a-zA-Z0-9_]*\)$/ =
> 0x;/p' | LC_ALL=C sort > arch/x86/vdso/vdso32-sysenter-syms.lds
Also show me the vdso32-sysenter-syms.lds file.
Thanks,
Roland
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Compiling with 2.6.25-rc2 with binutils 2.17 fails?
2008-02-18 18:40 ` Roland McGrath
@ 2008-02-18 21:53 ` Rob Landley
2008-02-18 22:26 ` Roland McGrath
0 siblings, 1 reply; 7+ messages in thread
From: Rob Landley @ 2008-02-18 21:53 UTC (permalink / raw)
To: Roland McGrath; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
On Monday 18 February 2008 12:40:37 Roland McGrath wrote:
> > I'm poking at it. Something in my cross compiling setup is driving this
> > bit screwy:
> >
> > i686-nm arch/x86/vdso/vdso32-sysenter.so.dbg |
>
> Show me the output of just this.
Attached.
> > sed -n -e 's/^00*/0/' -e 's/^\([0-9a-fA-F]*\) . \(VDSO[a-zA-Z0-9_]*\)$/ =
> > 0x;/p' | LC_ALL=C sort > arch/x86/vdso/vdso32-sysenter-syms.lds
>
> Also show me the vdso32-sysenter-syms.lds file.
Attached.
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
[-- Attachment #2: nm-out.txt --]
[-- Type: text/plain, Size: 449 bytes --]
0000000000000360 a _DYNAMIC
00000000000003d8 a _GLOBAL_OFFSET_TABLE_
000000000000040c T __kernel_rt_sigreturn
0000000000000400 T __kernel_sigreturn
0000000000000414 T __kernel_vsyscall
0000000000000000 A LINUX_2.5
0000000000000000 a VDSO32_PRELINK
000000000000040c t VDSO32_rt_sigreturn
0000000000000400 t VDSO32_sigreturn
0000000000000424 t VDSO32_SYSENTER_RETURN
0000000000000414 t VDSO32_vsyscall
0000000000000040 a VDSO32_vsyscall_eh_frame_size
[-- Attachment #3: vdso32-sysenter-syms.lds --]
[-- Type: text/plain, Size: 177 bytes --]
VDSO32_PRELINK = 0x0;
VDSO32_SYSENTER_RETURN = 0x0424;
VDSO32_rt_sigreturn = 0x040c;
VDSO32_sigreturn = 0x0400;
VDSO32_vsyscall = 0x0414;
VDSO32_vsyscall_eh_frame_size = 0x040;
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Compiling with 2.6.25-rc2 with binutils 2.17 fails?
2008-02-18 21:53 ` Rob Landley
@ 2008-02-18 22:26 ` Roland McGrath
0 siblings, 0 replies; 7+ messages in thread
From: Roland McGrath @ 2008-02-18 22:26 UTC (permalink / raw)
To: Rob Landley; +Cc: linux-kernel
> > > sed -n -e 's/^00*/0/' -e 's/^\([0-9a-fA-F]*\) . \(VDSO[a-zA-Z0-9_]*\)$/ =
> > > 0x;/p' | LC_ALL=C sort > arch/x86/vdso/vdso32-sysenter-syms.lds
> >
> > Also show me the vdso32-sysenter-syms.lds file.
>
> Attached.
The contents of this file are fine. If all the vdso32-*-syms.lds files
look sane, then your problem is just with the shell commands (cmd_vdso32sym)
that compare them.
Thanks,
Roland
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2008-02-18 22:26 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-16 23:27 Compiling with 2.6.25-rc2 with binutils 2.17 fails? Rob Landley
2008-02-17 0:04 ` Jan Engelhardt
2008-02-18 3:09 ` Roland McGrath
2008-02-18 10:39 ` Rob Landley
2008-02-18 18:40 ` Roland McGrath
2008-02-18 21:53 ` Rob Landley
2008-02-18 22:26 ` Roland McGrath
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).