All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: JD <jd1008@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question/help re: themake scripts in 2.6.36
Date: Sun, 7 Nov 2010 15:42:13 +0800	[thread overview]
Message-ID: <20101107074213.GL3046@hack> (raw)
In-Reply-To: <4CD63067.8010506@gmail.com>

On Sat, Nov 06, 2010 at 09:51:51PM -0700, JD wrote:
> I have compiled 2.6.36 (i686) without any problems.
> Since then, I have decided to change a couple of
> config variables (using xconfig).


You can use 'make oldconfig'.

> When done, running make all
> causes the make scripts to stop compilation after building
> a few objects, and spawn a shell.
> Since I have no idea what to do in that shell, I exit
> that shell, and the compilaton continues.
> This takes place 3 times before compilation is complete.
>


What? How can make spawn a shell...

Can you copy and paste what you see and what you get
from your terminal?

> Now, when I type make modules_install install,
> only modules_install is done. /boot does not get
> populated and /boot/grub/grub.conf is unchanged.
>
> The currently installed and running 2.6.36-1
> went through a similar scenario during build,
> but at least install did work.
> Now the install does not work.
> Befor the present build attempt,
> I had edited the Makefile to change the EXTRAVERSION to -2
> in order not to clobber the installed  2.6.36-1
>
> Could someone tell me what to do to force the install in /boot?
> /lib/modules does have 2.6.36-2.fc13.i686 fully populated.
>

Since you are using Fedora, you can try grubby or new-kernel-pkg.

-- 
Live like a child, think like the god.
 

  reply	other threads:[~2010-11-07  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07  4:51 Question/help re: themake scripts in 2.6.36 JD
2010-11-07  7:42 ` Américo Wang [this message]
     [not found]   ` <4CD73A04.5020604@gmail.com>
2010-11-09 10:40     ` Américo Wang

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=20101107074213.GL3046@hack \
    --to=xiyou.wangcong@gmail.com \
    --cc=jd1008@gmail.com \
    --cc=linux-kernel@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.