public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jiri Kosina <jkosina@suse.cz>, Andy Whitcroft <apw@shadowen.org>,
	Franck Bui-Huu <vagabon.xyz@gmail.com>,
	linux-kernel@vger.kernel.org,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: 2.6.23-rc8-mm1 -- powerpc link failure
Date: Thu, 27 Sep 2007 21:31:23 +0200	[thread overview]
Message-ID: <20070927193123.GC1847@uranus.ravnborg.org> (raw)
In-Reply-To: <20070927101342.92422296.akpm@linux-foundation.org>

On Thu, Sep 27, 2007 at 10:13:42AM -0700, Andrew Morton wrote:
> On Thu, 27 Sep 2007 14:13:21 +0200 (CEST) Jiri Kosina <jkosina@suse.cz> wrote:
> 
> > On Thu, 27 Sep 2007, Andy Whitcroft wrote:
> > 
> > > Ok, this problem seems to still persist in 2.6.23-rc8-mm2.  It seems we 
> > > have three options from here:
> > > 1) update the compiler support list to exclude these compilers, or
> > > 2) back this change out, or
> > > 3) switch to the version not using __weak.
> > > The latter seems to be the least intrusive change.  As no-one closer to 
> > > the problem is stepping up to make the decision I will propose we go 
> > > with the third option here.
> > 
> > Andrew,
> > 
> > if you agree with Andy that we should support compilers that don't work 
> > with __weak, please drop i386-and-x86_64-randomize-brk.patch and replace 
> > it with the one below instead (this has been already posted at 
> > http://lkml.org/lkml/2007/8/31/113). Thanks.
> > 
> 
> We have quite a few instances of __weak in there.  What is special about
> this one?

The bug we trigger is an ld bug - not a compiler bug.
What happens is that we have the same function defined weak twice.
In fs/ we include binfmt_elf.o in the build because
CONFIG_BINFMT_ELF is set.
And in arch/powerpc/kernel/binfmt_elf32.c:
we do an: #include "../../../fs/binfmt_elf.c"

Without actually trying it out I assume we trigger the ld bug
because we define the same weak function twice.

And this is a non-typical situation.

	Sam

  reply	other threads:[~2007-09-27 19:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25  8:46 2.6.23-rc8-mm1 Andrew Morton
2007-09-25 10:39 ` 2.6.23-rc8-mm1 Kamalesh Babulal
2007-09-25 15:46   ` 2.6.23-rc8-mm1 Andrew Morton
2007-09-25 12:19 ` [-mm Patch] fs/udf/balloc.c: mark a variable as uninitialized_var() WANG Cong
2007-09-25 12:52 ` [-mm Patch] drivers/usb/misc/sisusbvga/sisusb.c: kill two unused variables WANG Cong
2007-09-25 12:53 ` 2.6.23-rc8-mm1 - drivers/net/ibm_newemac/mal - broken Kamalesh Babulal
2007-09-25 16:16   ` Andrew Morton
2007-09-25 13:46 ` 2.6.23-rc8-mm1 -- powerpc link failure Andy Whitcroft
2007-09-25 15:23   ` Jiri Kosina
2007-09-27 12:03     ` Andy Whitcroft
2007-09-27 12:13       ` Jiri Kosina
2007-09-27 17:13         ` Andrew Morton
2007-09-27 19:31           ` Sam Ravnborg [this message]
2007-09-27 22:13         ` Andrew Morton
2007-09-27 22:17           ` Jiri Kosina
2007-09-25 17:26 ` 2.6.23-rc8-mm1 Randy Dunlap
2007-09-25 17:39   ` 2.6.23-rc8-mm1 Josef Sipek
2007-09-25 17:45   ` [PATCH 1/1] Unionfs: move poison #define into poison.h Josef 'Jeff' Sipek
2007-09-26  1:02     ` Josef 'Jeff' Sipek
2007-09-25 19:02 ` 2.6.23-rc8-mm1: unscrew UFS Alexey Dobriyan
2007-09-25 20:00 ` 2.6.23-rc8-mm1 - powerpc memory hotplug link failure Kamalesh Babulal
2007-09-25 22:01   ` Badari Pulavarty
2007-09-26  8:18     ` Kamalesh Babulal
2007-09-26  1:32   ` KAMEZAWA Hiroyuki
2007-09-26  1:48     ` KAMEZAWA Hiroyuki
2007-09-26  8:19       ` Kamalesh Babulal
2007-09-25 20:56 ` 2.6.23-rc8-mm1: drivers/kvm/ioapic.o build failure Mariusz Kozlowski
2007-09-26  9:00   ` [kvm-devel] " Avi Kivity
2007-09-26  9:14     ` Andrew Morton
2007-09-26  9:18       ` Avi Kivity
2007-09-25 22:05 ` 2.6.23-rc8-mm1 Badari Pulavarty
2007-09-26 12:28   ` 2.6.23-rc8-mm1 Andy Whitcroft
2007-09-25 22:23 ` 2.6.23-rc8-mm1 : wgt634u.c trem
2007-09-26  7:51 ` black screen after kill X [Was: 2.6.23-rc8-mm1] Jiri Slaby

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=20070927193123.GC1847@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=jkosina@suse.cz \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vagabon.xyz@gmail.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