Public bug reported:

Binary package hint: rt2500

Since feisty, rt2500 fails to build on all arches with errors:

g++ -c -pipe -w -O2 -D_REENTRANT  -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_SHARED 
-DQT_TABLET_SUPPORT -I/usr/share/qt3/mkspecs/default -I. -I. -I/usr/include/qt3 
-o raconfigui.o raconfigui.cpp
/usr/include/linux/wireless.h:886: error: 'IFNAMSIZ' was not declared in this 
scope
/usr/include/linux/wireless.h:925: error: 'IFNAMSIZ' was not declared in this 
scope
/usr/include/linux/wireless.h:1049: error: 'IFNAMSIZ' was not declared in this 
scope

Looking deeper, it seems that there was a change in the mainline
kernel's wireless.h back in September where some includes have been
surrounded by an #ifdef __KERNEL__ block in order to "sanitise" the
header. This means that IFNAMSIZ and some other things no longer get
defined. The changes can be seen at:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=baef186519c69b11cf7e48c26e75feb1e6173baa

Following the comments in linux/wireless.h I tried building rt2500 with
some includes changed from linux/wireless.h to iwlib.h (build dep on
libiw-dev) which allowed the package to build but after installing the
package, rt2500-source failed to build using module-assistant. This
could be a whole different bug but that's where I became out of my depth
of knowledge and felt filing a bug would be more useful.

I'd be happy to try fixing this bug/s since I have an rt2500 card but
I'm not very familiar with this kind of packaging so I may need some
mentoring through it

As an aside, this bug may be quite important to fix as a fallback if bug
#120297 doesn't get fixed for gutsy.

** Affects: rt2500 (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed

-- 
rt2500 fails to build
https://bugs.launchpad.net/bugs/120301
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to