From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [arch/x86/vdso/vdso32-syms.lds] Error 1
Date: Thu, 13 Nov 2008 11:14:57 +0100 [thread overview]
Message-ID: <20081113101457.GA4793@gentoox2.trippelsdorf.de> (raw)
In-Reply-To: <20081112213459.GA2315@gentoox2.trippelsdorf.de>
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
prev parent reply other threads:[~2008-11-13 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 18:11 Markus Trippelsdorf
2008-11-07 18:52 ` H. Peter Anvin
2008-11-07 19:03 ` Markus Trippelsdorf
2008-11-07 18:57 ` H. Peter Anvin
2008-11-07 19:06 ` Markus Trippelsdorf
2008-11-12 18:56 ` Roland McGrath
2008-11-12 21:34 ` Markus Trippelsdorf
2008-11-13 10:14 ` Markus Trippelsdorf [this message]
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=20081113101457.GA4793@gentoox2.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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
all inboxes | Powered by JetHome®