From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Gregoire Favre <greg@magma.unil.ch>
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 01:52:18 +0200 [thread overview]
Message-ID: <3ED2A8B2.5040607@gmx.net> (raw)
In-Reply-To: <20030526223803.GB14954@magma.unil.ch>
Gregoire Favre wrote:
> On Mon, May 26, 2003 at 11:01:12PM +0100, Grzegorz Jaskiewicz wrote:
>
>
>>looks like LINUX_VERSION_CODE is not defined
>>try this (as 2.5.69 > than 2.5.9)
>
>
> Well, maybe BK is not for me:
>
> greg@greg:linux >make dep && make bzImage && make modules && sudo make modules_install
> *** Warning: make dep is unnecessary now.
> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
> Starting the build. KBUILD_BUILTIN=1 KBUILD_MODULES=
> CHK include/linux/compile.h
> dnsdomainname: Unknown host
> CC fs/xfs/pagebuf/page_buf.o
> In file included from fs/xfs/pagebuf/page_buf.c:65:
> fs/xfs/pagebuf/page_buf_internal.h:46:24: operator '<' has no left operand
> fs/xfs/pagebuf/page_buf_internal.h:51:24: operator '<' has no left operand
> make[2]: *** [fs/xfs/pagebuf/page_buf.o] Error 1
> make[1]: *** [fs/xfs] Error 2
> make: *** [fs] Error 2
> Exit 2
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
HTH,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2003-05-26 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 19:31 xfs don't compil in linux-2.5 BK 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 [this message]
2003-05-27 19:42 ` Gregoire Favre
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=3ED2A8B2.5040607@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=gj@pointblue.com.pl \
--cc=greg@magma.unil.ch \
--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.