Date: Mon, 24 Sep 2007 23:02:22 +0200
From: Sam Ravnborg <sam@ravnborg.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org,
       Andy Whitcroft <apw@shadowen.org>
Subject: Re: 2.6.23-rc7-mm1
Message-ID: <20070924210222.GA4595@uranus.ravnborg.org>
References: <20070924021716.9bfe7dfb.akpm@linux-foundation.org> <46F78C73.5040505@linux.vnet.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46F78C73.5040505@linux.vnet.ibm.com>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1415
Lines: 47

Hi Kamalesh.

> The link error for a PowerMac G5 (powerpc) is still seen with 
> 2.6.23-rc7-mm1,
> and was reported for 2.6.23-rc6-mm1 (http://lkml.org/lkml/2007/9/19/62).
> 
>  KSYM    .tmp_kallsyms1.S
>  AS      .tmp_kallsyms1.o
>  LD      .tmp_vmlinux2
>  KSYM    .tmp_kallsyms2.S
>  AS      .tmp_kallsyms2.o
>  LD      vmlinux.o
> ld: dynreloc miscount for fs/built-in.o, section .opd
> ld: can not edit opd Bad value
> make: *** [vmlinux.o] Error 1

Can you try to narrow it down a bit further...
As this happens when building fs/built-in.o it should be
straightforward to do so.

First step would be to do:
rm fs/built-in.o
make fs/ V=1

Then copy the ld invocation and try to remove the input .o files one-by-one.
This should tell you which .o file is causing the bug.

Next step is to try to squeze down the offending file until the
errornous part remains.

Last time I did a
make fs/file.i

And then I used gcc & ld to compile and link.
Gradually removing stuff from file.i made me spot the problem
with the weak prototype in a header file.

I guess something else is making ld hit this error now.

PS. Just reinstalled my dev box so no crosscompiler atm.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/