All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: linux-next: kbuild tree build failure
Date: Wed, 14 Oct 2009 12:20:24 +1100	[thread overview]
Message-ID: <20091014122024.f5fa52a2.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hi Sam,

Today's linux-next build (x86_64 allmodconfig) failed like this:

In file included from arch/x86/kernel/syscall_64.c:28:
arch/x86/include/asm/unistd_64.h:665: error: array index in initializer exceeds array bounds
arch/x86/include/asm/unistd_64.h:665: error: (near initialization for 'sys_call_table')
arch/x86/include/asm/unistd_64.h:665: warning: excess elements in array initializer
arch/x86/include/asm/unistd_64.h:665: warning: (near initialization for 'sys_call_table')

Exposed by commit a2e2725541fad72416326798c2d7fa4dafb7d337 ("net:
Introduce recvmmsg socket syscall").  include/asm/asm-offsets.h did not
get updated even though arch/x86/kernel/asm-offsets.s did.  Ah,
generated/asm-offsets.h has been updated but my build tree still has the
(generated in a previous build) include/asm/asm-offsets.h which is
presumably found before the new arch/x86/include/asm/asm-offsets.h
introduced by commit fe5ff47a5d79ca99ec7e3155eb19469b44905b2c ("kbuild:
move asm-offsets.h to include/generated").

Sam, can you think of a better migration path?

I removed include/asm/asm_offsets.h from my object tree and everything
builds ok.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2009-10-14  1:21 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  1:20 Stephen Rothwell [this message]
2009-10-14  7:43 ` linux-next: kbuild tree build failure Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2009-06-09  1:48 Stephen Rothwell
2009-06-09 16:15 ` Sam Ravnborg
2009-06-09 16:19   ` Stephen Rothwell
2009-06-09 21:04     ` Sam Ravnborg
2009-06-09 23:27       ` Stephen Rothwell
2009-05-05  1:17 Stephen Rothwell
2009-05-05  6:35 ` Jan Beulich
2009-05-05  6:43   ` Sam Ravnborg
2009-05-05  7:04     ` Jan Beulich
2008-11-26  4:42 Stephen Rothwell
2008-11-26 21:06 ` Sam Ravnborg
2008-11-26 23:49   ` Stephen Rothwell
2008-12-03  0:36   ` Stephen Rothwell
2008-12-03  9:46     ` Sam Ravnborg
2008-11-25  4:47 Stephen Rothwell
2008-11-25  8:42 ` Sam Ravnborg
2008-11-25  8:58   ` Stephen Rothwell
2008-07-12 22:32 Milton Miller
2008-07-12 22:32 ` Milton Miller
2008-07-12 23:21 ` Roman Zippel
2008-07-12 23:21   ` Roman Zippel
2008-07-07  8:40 Stephen Rothwell
2008-07-07  8:40 ` Stephen Rothwell
2008-07-07 12:51 ` Sam Ravnborg
2008-07-07 12:51   ` Sam Ravnborg
2008-07-07 13:08   ` Stephen Rothwell
2008-07-07 13:08     ` Stephen Rothwell
2008-07-07 16:13 ` Roman Zippel
2008-07-07 16:13   ` Roman Zippel
2008-07-07 21:01   ` Sam Ravnborg
2008-07-07 23:36   ` Michael Ellerman
2008-07-07 23:36     ` Michael Ellerman
2008-07-08  2:55     ` Roman Zippel
2008-07-08  2:55       ` Roman Zippel
2008-07-10  0:51       ` Michael Ellerman
2008-07-10  0:51         ` Michael Ellerman
2008-07-10 14:59         ` Roman Zippel
2008-07-10 14:59           ` Roman Zippel
2008-07-14 16:53           ` Milton Miller
2008-07-14 16:53             ` Milton Miller
2008-07-08 21:19   ` Sam Ravnborg
2008-07-10 14:52     ` Roman Zippel
2008-07-25  4:13 ` Stephen Rothwell
2008-07-25  4:13   ` Stephen Rothwell
2008-07-26 10:06   ` Sam Ravnborg
2008-07-26 10:06     ` Sam Ravnborg
2008-07-26 12:40     ` Stephen Rothwell
2008-07-26 12:40       ` Stephen Rothwell

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=20091014122024.f5fa52a2.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=acme@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sam@ravnborg.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 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.