Summary: | cannot emerge net-wireless/ieee80211 against vanilla-sources-2.6.14 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Scott McKenzie <nzgreen> |
Component: | New packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andre.hinrichs, bart.braem, kernel, krosswindz |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Scott McKenzie
2005-10-28 19:03:49 UTC
(In reply to comment #0) > Old ieee80211 references found. In order to build the ieee80211 > subsystem, prior versions must first be removed. You can perform > this task by running this makefile as root via: > > % sudo make check_old > > and answering Y to remove the file references. Please, read the ebuild instructions before reporting bugs. *** This bug has been marked as a duplicate of 97397 *** This bug is not a dup of 97397. If it was then I could just follow the instructions given (remove /usr/src/linux/include/net/ieee80211.h) and it would merge. This bug relates to kernel 2.6.14. Bug 97397 relates to kernel 2.6.13 - just like it says in the bug title. > Please, read the ebuild instructions before reporting bugs. Please look at the ebuild and show me where it says: > % sudo make check_old Those instructions come not from the ebuild, but from the package source. Stop reopening this bug, I'm dead serious... (In reply to comment #3) > Stop reopening this bug, I'm dead serious... Eh, sorry. Too many open tabs, I thought you've reopened Bug 97397. I've added a work-around to net-wireless/ieee80211-1.1.x. Basically, you need to run the following command before emerging the package: `/bin/sh /usr/portage/net-wireless/ieee80211/files/remove-old /usr/src/linux` Wait a few hours, `emerge --sync`, run the above command - and retry the merge. *** Bug 112441 has been marked as a duplicate of this bug. *** This is a problem, please reopen: 2.6.14 is stable on x86 but ieee80211 1.1 is not, so the current situation gives horrible errors. The new kernel should be marked unstable or ieee80211 1.1.x should become stable I guess? Oh yes: there is even more confusion with the new kernel containing the ieee80211 framework, what should users use? (perhaps this is a different bug) I'd like to also suggest to either mark 2.6.14.2 unstable or to mark
ieee80211 stable. I've done this by marking 2.6.14.2 unstable locally on
my system:
Put the following line to /etc/portage/package.mask to do the same...
>=sys-kernel/vanilla-sources-2.6.14
|