mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Curt Howland <Howland@priss.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile error: arch/x86/kernel/entry_32.S:1422: Error: .size expression does not evaluate to a constant
Date: Thu, 17 Mar 2011 18:19:14 -0400	[thread overview]
Message-ID: <20110317221914.GG14675@home.goodmis.org> (raw)
In-Reply-To: <201103171741.39876.Howland@priss.com>

On Thu, Mar 17, 2011 at 05:41:39PM -0400, Curt Howland wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> arch/x86/kernel/entry_32.S: Assembler messages: 
> arch/x86/kernel/entry_32.S:1422: Error: .size expression does not 
> evaluate to a constant make[3]: *** [arch/x86/kernel/entry_32.o] 
> Error 1
> 
> I searched for this error and saw this had been posted to the LKML:
> 
> http://www.gossamer-threads.com/lists/linux/kernel/1347760
> 
> This was when the error happened in -rc7, but it was not fixed 
> for -rc8 or the released stable.
> 
> I'm just a user, not a developer, but I figure if its happening to me 
> with very generic tools it may be happening to other people who don't 
> use git, who don't apply patches, and such.
> 
> I don't have the warewithall to subscribe to the LKML, so I would be 
> obliged if you would copy me on any replies. I would be glad to 
> supply any further information if needed.

Thanks for reporting. This is a known problem. Unfortunately, it is due
to the new binutils (version 2.21) that decided to make something that
it use to ingore into something that is now an error.

The problem is that we have macros that create functions for us in
assembly:

ENTRY(foo)
	[ body of foo ]
END(foo)

But there also are some areas where we had a typo:

ENTRY(foo)
	[ body of foo ]
END(xfoo)

binutils version 2.20 and before ignored this little bug. Version 2.21
now fails with the error you get.

Sure we can go about fixing this bug, but because of this stupid
decision by the developers of binutils, older kernels will no longer
build. The correct thing for them to have done, was just to make it into
a warning and not fail the entire build.

-- Steve


  reply	other threads:[~2011-03-17 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 21:41 Curt Howland
2011-03-17 22:19 ` Steven Rostedt [this message]
2011-03-20 15:03 ` Patch: " Curt Howland

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=20110317221914.GG14675@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=Howland@priss.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

Powered by JetHome