All of lore.kernel.org
 help / color / mirror / Atom feed
From: julio <julio7k@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: error while installing staging kernel GKH
Date: Tue, 18 Nov 2014 03:54:58 +0000	[thread overview]
Message-ID: <546AC312.7080805@gmail.com> (raw)

Hi,

I was following the tutorial on how to build your first patch and came 
across this error when running
sudo make modules_install install

INSTALL sound/firewire/fireworks/snd-fireworks.ko
   DEPMOD  3.18.0-rc4-01142-gcc03f9b
sh ./arch/x86/boot/install.sh 3.18.0-rc4-01142-gcc03f9b 
arch/x86/boot/bzImage \
     System.map "/boot"
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.18.0-rc4-01142-gcc03f9b /boot/vmlinuz-3.18.0-rc4-01142-gcc03f9b
run-parts: executing /etc/kernel/postinst.d/dkms 
3.18.0-rc4-01142-gcc03f9b /boot/vmlinuz-3.18.0-rc4-01142-gcc03f9b
Error! Bad return status for module build on kernel: 
3.18.0-rc4-01142-gcc03f9b (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
^Carch/x86/boot/Makefile:185: recipe for target 'install' failed
make[1]: *** [install] Interrupt
arch/x86/Makefile:239: recipe for target 'install' failed
make: *** [install] Interrupt

this is the staging tree GKH.

cat /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log

returns the following message:

DKMS make.log for bcmwl-6.30.223.248+bdcom for kernel 
3.18.0-rc4-01142-gcc03f9b (x86_64)
lun 17 nov 20:54:47 CST 2014
CFG80211 API is prefered for this kernel version
Using CFG80211 API
   LD      /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/built-in.o
   CC [M] 
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.o
   CC [M] 
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_alloc_linux_if’:
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:64: 
error: macro "alloc_netdev" requires 4 arguments, but only 3 given
   dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup);
                                                                 ^
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:8: 
error: ‘alloc_netdev’ undeclared (first use in this function)
   dev = alloc_netdev(sizeof(priv_link_t), intf_name, ether_setup);
         ^
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:1316:8: 
note: each undeclared identifier is reported only once for each function 
it appears in
scripts/Makefile.build:257: recipe for target 
'/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o' failed
make[3]: *** 
[/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.o] 
Error 1
Makefile:1380: recipe for target 
'_module_/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build' failed
make[2]: *** [_module_/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build] Error 2

the question is should I report a bug on a staging driver?
and how this could be fixed? did the alloc_netdev function changed?
this kernel was compiled with make allyesconfig
Thanks,
PD: I am a Kernel newbie trying to commit my first patch...
Sorry if this is not the right mailing list
Julio Ordonez-Viales

                 reply	other threads:[~2014-11-18  3:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=546AC312.7080805@gmail.com \
    --to=julio7k@gmail.com \
    --cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.