From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "John W. Linville" <linville@tuxdriver.com>,
Sam Ravnborg <sam@ravnborg.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: wireless/kbuild tree build failure
Date: Tue, 6 Oct 2009 16:16:39 +1100 [thread overview]
Message-ID: <20091006161639.85e731bb.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
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 ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-10-06 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 5:16 Stephen Rothwell [this message]
2009-10-06 14:10 ` linux-next: wireless/kbuild tree build failure John W. Linville
2009-10-06 14:37 ` John W. Linville
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=20091006161639.85e731bb.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sam@ravnborg.org \
/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