From: Peter Zijlstra <peterz@infradead.org>
To: Martin Knoblauch <spamtrap@knobisoft.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.27-rc1
Date: Tue, 29 Jul 2008 13:57:38 +0200 [thread overview]
Message-ID: <1217332658.7563.16.camel@twins> (raw)
In-Reply-To: <406267.89338.qm@web32605.mail.mud.yahoo.com>
On Tue, 2008-07-29 at 04:23 -0700, Martin Knoblauch wrote:
> ----- Original Message ----
>
> > From: Linus Torvalds <torvalds@linux-foundation.org>
> > To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> > Sent: Tuesday, July 29, 2008 5:23:21 AM
> > Subject: Linux v2.6.27-rc1
> >
> >
> > It's two weeks (and one day), and the merge window is over.
> >
>
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CALL scripts/checksyscalls.sh
> CHK include/linux/compile.h
> CC arch/x86/kernel/ldt.o
> arch/x86/kernel/ldt.c: In function `alloc_ldt':
> arch/x86/kernel/ldt.c:67: error: invalid lvalue in unary `&'
> make[1]: *** [arch/x86/kernel/ldt.o] Error 1
> make: *** [arch/x86/kernel] Error 2
>
> This is a x86_64 build on a RHEL4U3 userland (gcc version 3.4.5
> 20051201 (Red Hat 3.4.5-2)). Config is taken from 2.6.26.
Its due to your ancient compiler - fix can be found here:
http://lkml.org/lkml/2008/7/29/48
next prev parent reply other threads:[~2008-07-29 11:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 11:23 Linux v2.6.27-rc1 Martin Knoblauch
2008-07-29 11:57 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-29 12:08 Martin Knoblauch
2008-07-29 3:23 Linus Torvalds
2008-07-29 4:01 ` Nick Piggin
2008-07-29 16:27 ` Jesse Barnes
2008-07-29 16:59 ` Linus Torvalds
2008-07-29 17:31 ` Roland Dreier
2008-07-30 9:03 ` Andrew Morton
2008-07-29 21:37 ` Sam Ravnborg
2008-07-29 21:42 ` Linus Torvalds
2008-07-29 21:59 ` Sam Ravnborg
2008-07-29 22:03 ` Linus Torvalds
2008-07-29 22:30 ` Sam Ravnborg
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=1217332658.7563.16.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spamtrap@knobisoft.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.