[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091006141057.GA2911@tuxdriver.com>
Date: Tue, 6 Oct 2009 10:10:58 -0400
From: "John W. Linville" <linville@...driver.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Sam Ravnborg <sam@...nborg.org>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: wireless/kbuild tree build failure
On Tue, Oct 06, 2009 at 04:16:39PM +1100, Stephen Rothwell wrote:
> Hi John,
>
> Today's linux-next build (i386 defconfig) failed like this:
>
> net/wireless/ethtool.c:1:30: error: linux/utsrelease.h: No such file or directory
> net/wireless/ethtool.c: In function 'cfg80211_get_drvinfo':
> net/wireless/ethtool.c:13: error: 'UTS_RELEASE' undeclared (first use in this function)
>
> Caused by commit fdd4b63be177e74b9346a557b75f4b48f3a42ee1 ("wireless:
> implement basic ethtool support for cfg80211 devices").
>
> utsrelease.h is now in include/generated after commit
> bbae701f7f258b051ed199ef71c5e85e683c0fb8 ("kbuild: move utsrelease.h to
> include/generated") from the kbuild tree. (My other builds only worked
> because utsrelease.h was left over in include/linux from previous builds.)
>
> I have reverted the kbuild commit for today. Sam, we need to come up
> with a better solution ... maybe for one release we could have the old
> files including the new files ... maybe remove the old files after
> 2.6.33-rc2 ...
It looks like not much uses utsrelease.h -- should I be using something
else to get a version identifier for the running kernel?
John
--
John W. Linville Someday the world will need a hero, and you
linville@...driver.com might be all we have. Be ready.
--
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