[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200710110817.22344.rob@landley.net>
Date: Thu, 11 Oct 2007 08:17:22 -0500
From: Rob Landley <rob@...dley.net>
To: Adrian Bunk <bunk@...nel.org>
Cc: linux-scsi@...r.kernel.org, sparclinux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Scsi on sparc build break in 2.6.23.
On Thursday 11 October 2007 6:05:55 am Adrian Bunk wrote:
> On Thu, Oct 11, 2007 at 05:52:48AM -0500, Rob Landley wrote:
> > CONFIG_SCSI_SUNESP=y breaks the build in 2.6.23:
> >
> > LD vmlinux
> > `scsi_esp_unregister' referenced in section `__ksymtab' of
> > drivers/built-in.o: defined in discarded section `.exit.text' of
> > drivers/built-in.o
> > make: *** [vmlinux] Error 1
> >
> > Do you need my full .config to reproduce this?
>
> Please always attach the .config when reporting errors.
> The few bytes don't matter and it often saves some time.
>
> I have an idea regarding what might be going wrong in this case,
> but it would cost me additional time to look at it because you didn't
> send your .config.
*shrug* That's why I asked.
The reason I hesitated is I use miniconfig files rather than big .config
files, and some people get confused by that. Drop the attached
miniconfig-linux in the kernel source directory and go:
make ARCH=sparc allnoconfig KCONFIG_ALLCONFIG=miniconfig-linux
That expands it to a big .config file, and from there "make ARCH=sparc
CROSS_COMPILE=sparc-" to reproduce the problem. Assuming you have a sparc
cross-compiler lying around.
Disable CONFIG_SCSI_SUNESP and it builds to the end, (and the result boots but
won't mount the root filesystem, which is sort of expected).
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
View attachment "miniconfig-linux" of type "text/plain" (2021 bytes)
Powered by blists - more mailing lists