mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: linux-kernel@vger.kernel.org, debian-alpha@lists.debian.org
Subject: Re: [BUG] 2.6.32-rc5 build failure on Alpha
Date: Thu, 29 Oct 2009 06:57:21 +0100	[thread overview]
Message-ID: <20091029055721.GA20758@merkur.ravnborg.org> (raw)
In-Reply-To: <20091029053947.GA9872@gherkin.frus.com>

On Thu, Oct 29, 2009 at 12:39:47AM -0500, Bob Tracy wrote:
> On Wed, Oct 28, 2009 at 10:53:05PM -0500, Bob Tracy wrote:
> > Mainline 2.6.32-rc5 kernel build failure.  The last few lines of the kernel
> > build output are:
> > 
> >   LD      vmlinux.o
> >   MODPOST vmlinux.o
> > WARNING: "saved_config" [vmlinux] is COMMON symbol
> >   GEN     .version
> >   CHK     include/linux/compile.h
> >   UPD     include/linux/compile.h
> >   CC      init/version.o
> >   LD      init/built-in.o
> >   LD      .tmp_vmlinux1
> > arch/alpha/kernel/vmlinux.lds:241: undefined symbol `THREAD_SIZE' referenced in expression
> > make: *** [.tmp_vmlinux1] Error 1
> 
> > In arch/alpha/include/asm/thread_info.h, THREAD_SIZE is defined as
> > (2*PAGE_SIZE).
> 
> Ok.  Found it.  The THREAD_SIZE definition is inside a
> "#ifndef __ASSEMBLY__" block, so it never gets referenced (because
> "__ASSEMBLY__" is defined for the "vmlinux.lds" build).  The obvious
> suggested fix is to move the definition outside the block.

A patch doing this has been posted some time ago.
I think/hope it is in -mm if it is not yet in -linus.

	Sam

  reply	other threads:[~2009-10-29  5:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29  5:39 Bob Tracy
2009-10-29  5:57 ` Sam Ravnborg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-29  3:53 Bob Tracy
2009-10-29  5:10 ` Bob Tracy

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=20091029055721.GA20758@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.frus.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®