From: Frederik Deweerdt <deweerdt@free.fr>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.27-rc1: fails to compile
Date: Wed, 30 Jul 2008 00:40:49 +0200 [thread overview]
Message-ID: <20080729224049.GA7325@slug> (raw)
In-Reply-To: <g54v84t6rgqplte4tvjrlh4r8g3m6n8kms@4ax.com>
Hello Grant,
On Wed, Jul 30, 2008 at 08:03:42AM +1000, Grant Coady wrote:
> On Mon, 28 Jul 2008 20:23:21 -0700 (PDT), Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> >
> >It's two weeks (and one day), and the merge window is over.
> >
> >Finally. I don't know why, but this one really did feel pretty dang busy.
> >And the size of the -rc1 patch bears that out - at 12MB, it's about 50%
> >bigger than 26-rc1 (but not that much bigger than 24/25-rc1, so it's not
> >like it's anything unheard of).
>
> Couple machines failed to compile with same error in different place:
>
> CC arch/x86/kernel/acpi/cstate.o
> arch/x86/kernel/acpi/cstate.c: In function `acpi_processor_ffh_cstate_probe':
> arch/x86/kernel/acpi/cstate.c:94: error: invalid lvalue in unary `&'
> make[2]: *** [arch/x86/kernel/acpi/cstate.o] Error 1
> make[1]: *** [arch/x86/kernel/acpi] Error 2
> make: *** [arch/x86/kernel] Error 2
> grant@peetoo:~/linux/linux-2.6.27-rc1a$
>
This issue has been reported, this is due to your old compiler.
Fix here:
http://lkml.org/lkml/2008/7/29/48
Regards,
Frederik
next prev parent reply other threads:[~2008-07-29 22:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 3:23 Linux v2.6.27-rc1 Linus Torvalds
2008-07-29 4:01 ` Nick Piggin
2008-07-29 9:49 ` 2.6.27-rc1: zd1211rw association fails Alistair John Strachan
2008-07-29 10:09 ` Johannes Berg
2008-07-29 11:25 ` Alistair John Strachan
2008-07-29 11:26 ` Johannes Berg
2008-07-29 11:37 ` Hugh Dickins
2008-07-29 11:46 ` Kalle Valo
2008-07-29 11:55 ` Alistair John Strachan
2008-07-29 12:04 ` Theodore Tso
2008-07-29 12:09 ` Johannes Berg
2008-07-29 12:15 ` Johannes Berg
2008-07-29 15:18 ` Theodore Tso
2008-07-29 17:52 ` John W. Linville
2008-07-30 4:48 ` David Miller
2008-07-29 13:57 ` Oops in microcode sysfs registration, Alistair John Strachan
2008-07-29 16:22 ` Pekka Paalanen
2008-07-29 16:50 ` Alistair John Strachan
2008-07-30 9:07 ` Dmitry Adamushko
2008-07-30 10:35 ` Dmitry Adamushko
2008-07-30 13:28 ` Peter Oruba
2008-07-31 12:49 ` Alistair John Strachan
2008-07-31 16:56 ` Ingo Molnar
2008-07-31 19:52 ` Dmitry Adamushko
2008-07-31 19:55 ` Dmitry Adamushko
2008-07-29 16:27 ` Linux v2.6.27-rc1 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-31 22:22 ` Linux v2.6.27-rc1: linux-next Rafael J. Wysocki
2008-07-29 20:49 ` Linux v2.6.27-rc1: problem with firmware stuff Rafael J. Wysocki
2008-07-29 21:01 ` Rafael J. Wysocki
2008-07-29 21:01 ` Linus Torvalds
2008-07-29 22:26 ` David Woodhouse
2008-07-29 21:37 ` Linux v2.6.27-rc1 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
2008-07-29 22:03 ` Linux v2.6.27-rc1: fails to compile Grant Coady
2008-07-29 22:40 ` Frederik Deweerdt [this message]
2008-07-29 23:46 ` Grant Coady
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=20080729224049.GA7325@slug \
--to=deweerdt@free.fr \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox