[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080221222245.GB30976@uranus.ravnborg.org>
Date: Thu, 21 Feb 2008 23:22:45 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: Nish Aravamudan <nish.aravamudan@...il.com>
Cc: Len Brown <lenb@...nel.org>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
Andy Whitcroft <apw@...dowen.org>
Subject: Re: [BUILD_FAILURE] 2.6.25-rc2-mm1 - Build Failure at acpi_os
On Thu, Feb 21, 2008 at 10:54:40AM -0800, Nish Aravamudan wrote:
> On 2/20/08, Len Brown <lenb@...nel.org> wrote:
> > On Saturday 16 February 2008 14:47, Kamalesh Babulal wrote:
> > > Hi Andrew,
> > >
> > > The 2.6.25-rc2-mm1 kernel with randconfig build option, fails
> > > to build on x86_64 machine
> > >
> > > CC drivers/acpi/osl.o
> > > drivers/acpi/osl.c:60:38: error: empty filename in #include
> > > drivers/acpi/osl.c: In function 'acpi_os_table_override':
> > > drivers/acpi/osl.c:399: error: 'AmlCode' undeclared (first use in this function)
> > > drivers/acpi/osl.c:399: error: (Each undeclared identifier is reported only once
> > > drivers/acpi/osl.c:399: error: for each function it appears in.)
> > > make[2]: *** [drivers/acpi/osl.o] Error 1
> > > make[1]: *** [drivers/acpi] Error 2
> > > make: *** [drivers] Error 2
> > >
> > > #
> > > # Automatically generated make config: don't edit
> > > # Linux kernel version: 2.6.25-rc2-mm1
> > > # Sun Feb 17 08:07:17 2008
> > > #
> >
> >
> > > CONFIG_ACPI_CUSTOM_DSDT=y
> > > CONFIG_ACPI_CUSTOM_DSDT_FILE=""
> >
> >
> > garbage in, garbage out.
>
> garbage explicitly *allowed* by Kconfig in this case, though.
>
> > If you don't give this build option a file name where AmlCode lives,
> > then the build will be unable to find AmlCode[].
> >
> > http://www.lesswatts.org/projects/acpi/overridingDSDT.php
>
> So we have a .config option whose sole purpose is to use another
> .config option? That seems ... less than ideal. Is there not some
> Kconfig voodoo we can do to only require the one option? Maybe
> something like how CONFIG_INITRAMFS_SOURCE is done? Adding Sam to the
> Cc, in case he has any ideas.
Make sure STANDALONE is y for your randconfig builds.
See README for examples.
STANALONE is there exactly to prevent the above but we cannot
control randconfig.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists