All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Jan Beulich <JBeulich@novell.com>,
	"Seidel, Conny" <Conny.Seidel@amd.com>,
	"borislav.petkov" <borislav.petkov@amd.com>,
	"mingo@elte.hu" <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: current TIP/master doesn't build on SLES10
Date: Tue, 28 Sep 2010 09:52:04 -0700	[thread overview]
Message-ID: <4CA21D34.7010209@zytor.com> (raw)
In-Reply-To: <20100928161912.GF5003@loge.amd.com>

On 09/28/2010 09:19 AM, Andreas Herrmann wrote:
> On Tue, Sep 28, 2010 at 12:08:29PM -0400, Jan Beulich wrote:
>>>>> On 28.09.10 at 16:31, Conny Seidel <conny.seidel@amd.com> wrote:
>>> Hi
>>>
>>> compiling TIP/master (44bc8c4f500fce7263803b4acd016fa03cf8a91a) on
>>> SLES10 fails with the following build error:
>>>
>>> arch/x86/kernel/entry_64.S: Assembler messages:
>>> arch/x86/kernel/entry_64.S:1181: Error: too many positional arguments
>>> arch/x86/kernel/entry_64.S:1181: Error: too many positional arguments
>>> make[2]: *** [arch/x86/kernel/entry_64.o] Error 1
>>> make[1]: *** [arch/x86/kernel] Error 2
>>> make: *** [arch/x86] Error 2
>>>
>>> I've bisected it to commit df5d1874ce1a1f0e0eceff4fa3a9d45620243a68.
>>>
>>> Reverting it fixes the issue. 
>>>
>>> I know that this is caused by binutils 2.16.91.0.5 which is distributed
>>> with SLES10.
>>
>> I'm generally doing almost all of my work on SLE10, and have not run
>> into this issue. Are you sure you've got it fully updated?
> 
> BTW, the build error looks similar to the build problem fixed by
> 
>   commit e8a0e27662186f8856a0a6242e7a8386c9a64a53
>   Author: Ingo Molnar <mingo@elte.hu>
>   Date:   Fri Nov 21 15:11:32 2008 +0100
> 
>     x86: clean up after: move entry_64.S register saving out of the macros, fix
> 

Well, yes of course... it can be summarized as "macros in binutils 2.16
are broken beyond anyone's wildest beliefs".

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-09-28 16:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 14:31 current TIP/master doesn't build on SLES10 Conny Seidel
2010-09-28 16:08 ` Jan Beulich
2010-09-28 16:19   ` Andreas Herrmann
2010-09-28 16:52     ` H. Peter Anvin [this message]
2010-09-28 16:20   ` H. Peter Anvin
2010-09-28 17:14   ` Conny Seidel
2010-09-28 17:51     ` H. Peter Anvin

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=4CA21D34.7010209@zytor.com \
    --to=hpa@zytor.com \
    --cc=Conny.Seidel@amd.com \
    --cc=JBeulich@novell.com \
    --cc=andreas.herrmann3@amd.com \
    --cc=borislav.petkov@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.