Bugzilla Bug 164703

My current, working,  configuration is gentoo-sources-2.6.18-r6,
ieee80211-1.1.13-r1, ipw3945-1.1.0-r1 . Afrter stabilising to
gentoo-sources-2.6.19-r5, ipw3945 does not compile, failing with the following
error:

make[1]: Entering directory `/usr/src/linux-2.6.19-gentoo-r5'
  CC [M] 
/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.o
In file included from
/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.c:68:
/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.h:32:26:
error: linux/config.h: No such file or directory
/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.c: In
function ‘ipw_pci_probe’:
/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.c:16355:
warning: passing argument 2 of ‘request_irq’ from incompatible pointer type
/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.c: In
function ‘ipw_pci_resume’:
/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.c:16622:
warning: ignoring return value of ‘pci_enable_device’, declared with
attribute warn_unused_result
make[2]: ***
[/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0/ipw3945.o]
Error 1
make[1]: ***
[_module_/var/tmp/portage/net-wireless/ipw3945-1.1.0-r1/work/ipw3945-1.1.0]
Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.19-gentoo-r5'
make: *** [modules] Error 2

!!! ERROR: net-wireless/ipw3945-1.1.0-r1 failed.
Call stack:
  ebuild.sh, line 1611:   Called dyn_compile
  ebuild.sh, line 968:   Called qa_call 'src_compile'
  environment, line 4009:   Called src_compile
  ipw3945-1.1.0-r1.ebuild, line 74:   Called linux-mod_src_compile
  linux-mod.eclass, line 510:   Called die

!!! Unable to make  KSRC=/usr/src/linux KSRC_OUTPUT=/usr/src/linux
IEEE80211_INC=/usr/include all.
!!! If you need support, post the topmost build error, and the call stack if
relevant.
!!! A complete build log is located at
'/var/log/portage/net-wireless:ipw3945-1.1.0-r1:20070131-140313.log'

*** This bug has been marked as a duplicate of bug 157076 ***