Skip to contentSkip to conversation

Compiling with 2.6.25-rc2 with binutils 2.17 fails?

DISCUSSION Rob Landley 3 participants 7 messages Feb 16, 2008 – Feb 18, 2008

lore
Share & tools
lore
#0 lore raw

Is anybody else having trouble compiling the kernel with binutils 2.17?

The build does this:

Quoted 9 lines

VDSOSYM arch/x86/vdso/vdso32-syms.lds

x86/vdso/vdso32-int80-syms.lds Fri Feb 15 23:38:41 2008 renamed from - Fri Feb 15 23:38:41 2008 +5 -0
@@ -0,0 +1,5 @@
+VDSO32_PRELINK = 0x0;
+VDSO32_rt_sigreturn = 0x040c;
+VDSO32_sigreturn = 0x0400;
+VDSO32_vsyscall = 0x0414;
+VDSO32_vsyscall_eh_frame_size = 0x040;
Quoted 3 lines

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

Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
#1 lore raw
Quoted 18 lines · Rob Landley

The build does this:

Quoted 9 lines

VDSOSYM arch/x86/vdso/vdso32-syms.lds

x86/vdso/vdso32-int80-syms.lds Fri Feb 15 23:38:41 2008 renamed from - Fri Feb 15 23:38:41 2008 +5 -0
@@ -0,0 +1,5 @@
+VDSO32_PRELINK = 0x0;
+VDSO32_rt_sigreturn = 0x040c;
+VDSO32_sigreturn = 0x0400;
+VDSO32_vsyscall = 0x0414;
+VDSO32_vsyscall_eh_frame_size = 0x040;
Quoted 3 lines

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...

Quoted 2 lines

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.

#2 lore raw
In reply to Rob Landley
Quoted 3 lines

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

#3 lore raw
Quoted 7 lines · On Sunday 17 February 2008 21:09:10 Roland McGrath wrote:
Quoted 3 lines

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

x86/vdso/vdso32-int80-syms.lds Sun Feb 17 20:24:03 2008 renamed from - Sun Feb 17 20:24:03 2008 +5 -0
@@ -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...

Quoted 2 lines

Thanks,
Roland

Rob

Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
#4 lore raw
Quoted 4 lines

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.

Quoted 2 lines

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

#5 lore raw
Quoted 6 lines · On Monday 18 February 2008 12:40:37 Roland McGrath wrote:
Quoted 4 lines

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.

Quoted 4 lines
Quoted 2 lines

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

Signature · 2 lines
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

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

VDSO32_PRELINK = 0x0;
VDSO32_SYSENTER_RETURN = 0x0424;
VDSO32_rt_sigreturn = 0x040c;
VDSO32_sigreturn = 0x0400;
VDSO32_vsyscall = 0x0414;
VDSO32_vsyscall_eh_frame_size = 0x040;

#6 lore raw
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

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