All of lore.kernel.org
 help / color / mirror / Atom feed
From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: make error
Date: Thu, 1 Nov 2012 07:40:39 -0700	[thread overview]
Message-ID: <20121101144039.GA2623@gmail.com> (raw)
In-Reply-To: <CAKE9jaZb3rNbHMXuCv60Lthw0iQN2kEEnJWL6ixwWUJZuME=YQ@mail.gmail.com>

On Thu, Nov 01, 2012 at 03:13:04PM +0200, Gregg Douglas wrote:
> Thanks Anmol, first installed the following extra packages
> "linux-kernel-headers kernel-syms module-init-tools" then ran make
> oldconfig && make prepare, I get further:
>  make M=drivers/staging/bcm/
> 
>   WARNING: Symbol version dump /home/douglagm/git/linux-2.6/Module.symvers
>            is missing; modules will have no dependencies and modversions.
> 
>   LD [M]  drivers/staging/bcm//bcm_wimax.o
> /bin/sh: scripts/mod/modpost: No such file or directory
> make[1]: *** [drivers/staging/bcm//bcm_wimax.o] Error 1
> make: *** [_module_drivers/staging/bcm/] Error 2
> 
> I did a git clone git://
> git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> then git branch douglagm - I am working on this.
> 
You should be cloing linux-next[1].

You are seing the above warning message because you have booted from
kernel-Version-X and you are building modules for kernel-Version-Y. To get rid
of this, after cloning the linux-next tree, build the kernel and boot from it.
Building and booting from your fresh kernel is sort of straight forward process
if you are not much concerned about the final kernel image size, etc. Following 
steps on my ubuntu box works fine, might work for you as well.
To build the kernel, in just few steps:

1: # sudo apt-get install build-essential
2: # make oldconfig
3: # make all 
4: # make modules_install install
5: # update-grub
6: # shutdown -r -y now

If you have system has multiple CPUs(see: cat /proc/cpuinfo), you can reduce the
build time by replacing the command in step 3 above as 
3: # make -jX all 
Where X = Number of CPUs

You also need to change your email-client to something else as gmail e-mail
client will not work for sending patches, refer email-clients[2] under
Documentation. I use mutt and this works quite well with gmail smtp server. You
can search for a mutt configuration file over world wide web to work with gmail.

You can also use git send-email command to send patches, but before that you
need to instal git-email add-on. On ubuntu box:
# sudo apt-get install git-email

Then setup smtp configuration
# git config --global sendemail.smtpserver smtp.gmail.com
# git config --global sendemail.smtpserverport 587
# git config --global sendemail.smtpencryption tls
# git config --global sendemail.smtpuser <YOUR_GMAIL_ID@gmail.com>

-Amit

[1] git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
[2] http://lxr.linux.no/#linux+v3.6.5/Documentation/email-clients.txt

  reply	other threads:[~2012-11-01 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 12:18 make error Gregg Douglas
     [not found] ` <CAP0ktjLiv=2U2oja_2vk1r9Gof_xL+n5Vs0diigsPOMxWHyvdw@mail.gmail.com>
2012-11-01 13:13   ` Gregg Douglas
2012-11-01 14:40     ` Kumar amit mehta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-08 12:04 Masaru Nomiya
2011-10-10 11:02 ` Todor Tomov
2011-10-10 12:26   ` Masaru Nomiya
2002-04-16 18:38 Thomas Beer
2002-04-16 19:06 ` Richard Adams
2002-04-17  0:59 ` lawson_whitney
2002-04-17  6:40   ` Tom Beer

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=20121101144039.GA2623@gmail.com \
    --to=gmate.amit@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.