linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-user] Re: [uml-devel] new skas3 patch ready for 2.4.25
Date: Sun, 22 Feb 2004 20:56:30 +0100	[thread overview]
Message-ID: <200402222056.30704.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <87u11jrnwk.fsf@amaterasu.srvr.nix>

Alle 19:04, domenica 22 febbraio 2004, Nix ha scritto:
> On Sun, 22 Feb 2004, BlaisorBlade said:
> > Hmmm, I've looked at the faulting code and IMHO the most probable thing
> > is a compilation problem (forgot make dep after applying the patch, for
> > instance) - try saving your .config, running make mrproper,
> > grepping through .config to check that CONFIG_PROC_MM=y and recompiling
> > the bzImage:
> >  $ make dep bzImage
>
> It's highly plausible that exactly that happened: I forgot `make
> oldconfig' during the first build and assumed (ha!) that `make dep'
> would fix everything up OK so that a config change would trigger
> rebuilds appropriately. Possibly this was a foolish assumption and a
> `make dep clean' was necessary.

When analyzing your bug I was really astonished - I thought at a such scenario 
( 1st build without CONFIG_PROC_MM created ptrace.o but then failed - config 
updated - rebuild all but ptrace.o is not rebuilt) and posted my answer in 
that hypothesis, but I thought that was too hard to trigger and that I had 
made some errors.

Make dep should have fixed things, so it's not your fault, but in this case it 
didn't - sometimes happens in 2.4 builds. Luckily, 2.6 finally fixed this (at 
least for what I've heard and for my personal experience).

Good bye and best wishes for your new kernel!
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-02-22 20:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 16:00 [uml-devel] skas3 patch fails against vanilla-2.4.25 Patrick Moor
2004-02-19 20:27 ` [uml-devel] " Sven Köhler
2004-02-20 10:12   ` Gerd Knorr
2004-02-20 12:30     ` Sven Köhler
2004-02-20 12:54       ` Gerd Knorr
2004-02-20 13:19         ` Sven Köhler
2004-02-20 17:10   ` Goetz Bock
2004-02-20 20:25 ` [uml-devel] new skas3 patch ready for 2.4.25 BlaisorBlade
2004-02-21 15:50   ` Nix
2004-02-22 15:00     ` [uml-user] " BlaisorBlade
2004-02-22 18:04       ` Nix
2004-02-22 19:56         ` BlaisorBlade [this message]
2004-02-25  7:57           ` Nix
2004-02-23  6:30   ` skas and vserver on 2.4.25 (Re: [uml-devel] new skas3 patch ready for 2.4.25) Nicholas Lee
2004-02-25 15:54     ` BlaisorBlade
2004-02-25 19:40       ` Nicholas Lee
2004-02-25 20:06         ` BlaisorBlade
2004-02-24 15:59   ` [uml-devel] new skas3 patch ready for 2.4.25 Patrick Moor

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=200402222056.30704.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox