From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Gregoire Favre <greg@magma.unil.ch>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: xfs don't compil in linux-2.5 BK
Date: 26 May 2003 23:01:12 +0100 [thread overview]
Message-ID: <1053986469.3754.6.camel@nalesnik.localhost> (raw)
In-Reply-To: <20030526193136.GB10276@magma.unil.ch>
On Mon, 2003-05-26 at 20:31, Gregoire Favre wrote:
> Hello,
>
> I don't know if I have fetched the source with BK the right way...
> Anyway the compil ends that way:
>
> CC fs/xfs/xfs_rw.o
> 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
> make[2]: *** [fs/xfs/pagebuf/page_buf.o] Error 1
> make[1]: *** [fs/xfs] Error 2
> make: *** [fs] Error 2
> 141.112u 14.914s 3:19.78 78.0% 0+0k 0+0io 492771pf+0w
> Exit 2
looks like LINUX_VERSION_CODE is not defined
try this (as 2.5.69 > than 2.5.9)
diff -ur 2/fs/xfs/pagebuf/page_buf_internal.h
1/fs/xfs/pagebuf/page_buf_internal.h
--- 2/fs/xfs/pagebuf/page_buf_internal.h 2003-05-05
00:53:14.000000000 +0100
+++ 1/fs/xfs/pagebuf/page_buf_internal.h 2003-05-26
22:59:27.000000000 +0100
@@ -43,11 +43,6 @@
#define PB_DEFINE_TRACES
#include "page_buf_trace.h"
-#if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,9)
-#define page_buffers(page) ((page)->buffers)
-#define page_has_buffers(page) ((page)->buffers)
-#endif
-
#ifdef PAGEBUF_LOCK_TRACKING
#define PB_SET_OWNER(pb) (pb->pb_last_holder = current->pid)
#define PB_CLEAR_OWNER(pb) (pb->pb_last_holder = -1)
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 labs
next prev parent reply other threads:[~2003-05-26 22:00 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 [this message]
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
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=1053986469.3754.6.camel@nalesnik.localhost \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox