From: Gregoire Favre <greg@magma.unil.ch>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Grzegorz Jaskiewicz <gj@pointblue.com.pl>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: xfs don't compil in linux-2.5 BK
Date: Tue, 27 May 2003 21:42:08 +0200 [thread overview]
Message-ID: <20030527194208.GC17428@magma.unil.ch> (raw)
In-Reply-To: <3ED2A8B2.5040607@gmx.net>
On Tue, May 27, 2003 at 01:52:18AM +0200, Carl-Daniel Hailfinger wrote:
> if you are using bk, maybe not all files were checked out? Try
>
> bk -r get
>
> and if the error still does not go away,
>
> make mrproper
>
> and then
>
> make {,x,menu}config
>
> make dep does nothing in 2.5 and make bzImage is standard target, so you
> can abbreviate you command line to
>
> make && make modules && sudo make modules_install
Thank you very much for your answer, I have tried the bk -r get, but I
didn't get the 2.5.70 in the Makefile...
I am a little bit lost with bk. Finally I tried:
bk pull
bk -r co
And then I got the 2.5.70 and it still compiling it ;-)
(the xfs stuff is passed).
Sorry for the complete off-topic: I use DVB, and most of the time, the
one included in the kernel is outdated and I took the one from
cvs -q -z3 -d :pserver:anonymous@linuxtv.org:/cvs/linuxtv co dvb-kernel
and the dvb-kernel/makelinks replace some files from the kernel with
symlinks: could I then use bk to update after?
An hudge thank,
Grégoire
__________________________________________________________________
http://www-ima.unil.ch/greg ICQ:16624071 mailto:greg@magma.unil.ch
prev parent reply other threads:[~2003-05-27 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 19:31 Gregoire Favre
2003-05-26 22:01 ` Grzegorz Jaskiewicz
2003-05-26 22:38 ` Gregoire Favre
2003-05-26 23:21 ` Nathan Scott
2003-05-27 19:46 ` Gregoire Favre
2003-05-26 23:52 ` Carl-Daniel Hailfinger
2003-05-27 19:42 ` Gregoire Favre [this message]
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=20030527194208.GC17428@magma.unil.ch \
--to=greg@magma.unil.ch \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=gj@pointblue.com.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®