public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ia64@vger.kernel.org
Subject: Re: linux-next: ia64 allmodconfig
Date: Thu, 21 Aug 2008 16:30:19 +0000	[thread overview]
Message-ID: <20080821093019.5e770029.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080820233526.14c44ea6.akpm@linux-foundation.org>

On Thu, 21 Aug 2008 08:04:23 -0500 Robin Holt <holt@sgi.com> wrote:

> On Thu, Aug 21, 2008 at 07:59:58AM -0500, Robin Holt wrote:
> > On Wed, Aug 20, 2008 at 11:35:26PM -0700, Andrew Morton wrote:
> > > arch/ia64/kernel/built-in.o(.text+0x4862): In function `efi_initialize_iomem_resources':
> > > : undefined reference to `__ia64_save_stack_nonlocal'
> > > arch/ia64/kernel/built-in.o(.text+0x12a92): In function `pfm_context_create':
> > > : undefined reference to `__ia64_save_stack_nonlocal'
> > > arch/ia64/kernel/built-in.o(.text+0x1bc02): In function `sys_perfmonctl':
> > > : undefined reference to `__ia64_save_stack_nonlocal'
> > > arch/ia64/kernel/built-in.o(.text+0x37c82): In function `dup_state_stack':
> > > : undefined reference to `__ia64_save_stack_nonlocal'
> > > arch/ia64/kernel/built-in.o(.text+0x382b2): In function `desc_prologue':
> > > : undefined reference to `__ia64_save_stack_nonlocal'
> > > arch/ia64/kernel/built-in.o(.text+0x3ad12): more undefined references to `__ia64_save_stack_nonlocal' follow
> > > 
> > > ia64 seems to break a lot.
> > 
> > I just did a git-checkout of
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> >  linux-next/master and got commit:
> > e85df409b2ad8528fa772379393c81406c417bbf
> > 
> > When I
> > make allmodconfig; make -j 24 compressed, I get no such warnings.  I do
> > still see a failure from the SFC driver :(
> > 
> > Are you sure something isn't a little dirty in your work area?  Did you
> > maybe do a make allyesconfig, allnoconfig, allmodconfig sequence?

make mrproper
make allmodconfig
make -j12

> Oh, just realized this could be a gcc version issue as well.  Could you
> provide that as well?  I had used the SLES installed version (4.1.2).

It's the one in http://userweb.kernel.org/~akpm/cross-compilers/

gcc-3.4.5-glibc-2.3.6
GNU ld version 2.15

  parent reply	other threads:[~2008-08-21 16:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  6:35 linux-next: ia64 allmodconfig Andrew Morton
2008-08-21 12:59 ` Robin Holt
2008-08-21 13:04 ` Robin Holt
2008-08-21 16:30 ` Andrew Morton [this message]
2008-08-21 20:14 ` Luck, Tony
2008-08-21 21:08 ` Robin Holt
2008-08-21 23:11 ` Luck, Tony
2008-08-21 23:32 ` Robin Holt
2008-08-21 23:39 ` Gerald Pfeifer
2008-08-22  0:23 ` Luck, Tony
2008-08-22  3:29 ` Robin Holt
2008-08-22  3:31 ` Robin Holt
2008-08-22  8:00 ` Pekka Enberg
2008-08-22 13:03 ` Robin Holt
2008-08-22 23:34 ` Luck, Tony

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=20080821093019.5e770029.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-ia64@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