public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	Bill Gatliff <bgat@billgatliff.com>
Subject: Re: Linux 2.6.30-rc2: [PATCH] ARM OABI compatibility: fix build error
Date: Wed, 15 Apr 2009 11:35:19 +0200	[thread overview]
Message-ID: <20090415093519.GC12921@traven> (raw)
In-Reply-To: <20090415092942.GJ6058@n2100.arm.linux.org.uk>

El Wed, Apr 15, 2009 at 10:29:42AM +0100 Russell King - ARM Linux ha dit:

> On Wed, Apr 15, 2009 at 11:12:23AM +0200, Matthias Kaehlcke wrote:
> > El Wed, Apr 15, 2009 at 10:03:07AM +0100 Russell King - ARM Linux ha dit:
> > 
> > > On Wed, Apr 15, 2009 at 10:33:26AM +0200, Matthias Kaehlcke wrote:
> > > > Building for ARM with CONFIG_OABI_COMPAT enabled fails due to a
> > > > missing include:
> > > 
> > > Yes, lots of people have been whinging about this over the last six days,
> > > but I'm only just catching up since returning from an Easter break.
> > > 
> > > Does anyone know /when/ this breakage happened, or even better what caused
> > > it?
> > 
> > a week ago i build v2.6.30-rc1 based on the same .config without
> > running into this issue. if i find some time i'll try bisecting it
> 
> Hmm, I think it's caused by 47788c58e66c050982241d9a05eb690daceb05a9.

you're right, bitsecting just pointed me to this commit
 
> The commit message looks rather interesting, including:
> 
>     arch/ia64/ia32/ia32priv.h:290:1: warning: "elf_check_arch" redefined
>     arch/ia64/include/asm/elf.h:19:1: warning: this is the location of the previous definition
> 
> surely the right answer is to only have _one_ definition of this thing,
> rather than two which may be different?  IOW, how do you know for certain
> which definition gets used where.
> 
> Not sure that I totally agree with the rationale in this commit, but I
> guess we have to live with it because it's x86.
> 
> Now, others have been putting out patches to solve the ARM build problem
> caused by the above commit, including one which includes linux/slab.h
> instead of linux/mm.h.  That seems to be a better fix than needlessly
> including lots of other stuff via linux/mm.h.  I notice that akpm picked
> up the linux/slab.h version yesterday.

i agree that linux/slab.h is preferable to linux/mm.h

-- 
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona

                       El camino se hace al andar
                           (Antonio Machado)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

  reply	other threads:[~2009-04-15  9:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 23:48 Linux 2.6.30-rc2 Linus Torvalds
2009-04-15  0:22 ` Alessandro Suardi
2009-04-15  1:17   ` Linus Torvalds
2009-04-15  0:40 ` patch-2.6.30-rc2.bz2 does not apply cleanly Tetsuo Handa
2009-04-15  1:42 ` Linux 2.6.30-rc2 Zhang, Yanmin
2009-04-15  2:01   ` Linus Torvalds
2009-04-15  2:24     ` Tetsuo Handa
2009-04-15 13:26     ` Alessandro Suardi
2009-04-15  6:21 ` Brice Goglin
2009-04-15  7:33   ` yakui_zhao
2009-04-15  7:41     ` Zhang Rui
2009-04-15  7:43       ` Brice Goglin
2009-04-15  8:33 ` Linux 2.6.30-rc2: [PATCH] ARM OABI compatibility: fix build error Matthias Kaehlcke
2009-04-15  9:03   ` Russell King - ARM Linux
2009-04-15  9:12     ` Matthias Kaehlcke
2009-04-15  9:29       ` Russell King - ARM Linux
2009-04-15  9:35         ` Matthias Kaehlcke [this message]
2009-04-15 12:22 ` Linux 2.6.30-rc2 Eyal Lebedinsky

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=20090415093519.GC12921@traven \
    --to=matthias@kaehlcke.net \
    --cc=bgat@billgatliff.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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