Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752687AbYKMKPW (ORCPT ); Thu, 13 Nov 2008 05:15:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751235AbYKMKPJ (ORCPT ); Thu, 13 Nov 2008 05:15:09 -0500 Received: from smtp-out-45.synserver.de ([217.119.50.45]:1067 "HELO smtp-out-45.synserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1750728AbYKMKPI (ORCPT ); Thu, 13 Nov 2008 05:15:08 -0500 X-SynServer-TrustedSrc: 1 X-SynServer-AuthUser: markus@trippelsdorf.de X-SynServer-PPID: 7107 Date: Thu, 13 Nov 2008 11:14:57 +0100 From: Markus Trippelsdorf To: Roland McGrath Cc: linux-kernel@vger.kernel.org Subject: Re: [arch/x86/vdso/vdso32-syms.lds] Error 1 Message-ID: <20081113101457.GA4793@gentoox2.trippelsdorf.de> References: <20081107181117.GA29006@gentoox2.trippelsdorf.de> <20081112185617.4A1C71541FE@magilla.localdomain> <20081112213459.GA2315@gentoox2.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081112213459.GA2315@gentoox2.trippelsdorf.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2136 Lines: 53 On Wed, Nov 12, 2008 at 10:34:59PM +0100, Markus Trippelsdorf wrote: > On Wed, Nov 12, 2008 at 10:56:17AM -0800, Roland McGrath wrote: > > Sorry for the delay, I've been offline. > > > > > All of a sudden I get the following error when I build the kernel: > > > > Suddenly when? What changed to make this start happening? > > Is it recent kernel sources? If so, can you git-bisect to > > which change did it? If not, did something else change in > > your build environment that made this problem appear? > > Does it come or go with some .config change? > > > > > --- - 2008-11-07 18:51:36.392997346 +0100 > > > +++ arch/x86/vdso/vdso32-int80-syms.lds 2008-11-07 18:51:36.283820343 +0100 > > > @@ -3,5 +3,3 @@ > > > VDSO32_sigreturn = 0x0400; > > > VDSO32_vsyscall = 0x0420; > > > VDSO32_vsyscall_eh_frame_size = 0x040; > > > -VDSO32_vsyscall = 0x0420; > > > -VDSO32_vsyscall_eh_frame_size = 0x040; > > > make[1]: *** [arch/x86/vdso/vdso32-syms.lds] Error 1 > > > make: *** [arch/x86/vdso] Error 2 > > > > That sure looks odd. It looks like sort -u failed to uniquify those lines. > > > > Can you try something like this: > > > > > - else rm -f $(@D)/.tmp_$(@F); exit 1; \ > > > + else cat >&2 $(@D)/.tmp_$(@F); exit 1; \ > > > > and run make V=1 to see the full output on the failure? > > Something odd is going on with my system: > I will try to figure out what causes this behaviour, but it is not > kernel related I guess. So I apologize for the noise. It turned out that my version of glibc, which was compiled with a gcc-4.4.0 snapshot, was the cause of the problem. However simply compiling glibc again with gcc-4.3.2 did not work, because glibc uses "LC_ALL=C sort -u" in many Makefiles. So I had to find an old binary version of glibc, install that version in a chroot environment and finally compile glibc again with a sane compiler in that chroot. -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/