From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Oglesby Subject: Re: reiser4 for 2.6.13 is available on our website Date: Thu, 29 Sep 2005 21:59:59 -0500 Message-ID: <433CAA2F.2030708@teleformix.com> References: <433C23A2.9020403@namesys.com> <1128031794.10856.155.camel@gentoo> <433C6B7E.40201@namesys.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Gregory Maxwell Cc: Hans Reiser , Jake Maciejewski , =?UTF-8?B?xYF1a2FzeiBNaWVyendh?= , "reiserfs-list@namesys.com" , vs Gregory Maxwell wrote: >On 9/29/05, Hans Reiser wrote: > > >>It works on non-amd64, will fix amd64 tomorrow I hope. >> >> > >No, it fails on FC4/x86 here to complie as well, with the same failure mode. > > > Errors from my vanilla 2.6.13.1 kernel + ReiserFS4 patch compile tonight: fs/reiser4/super_ops.c: In function `reiser4_dirty_inode': fs/reiser4/super_ops.c:176: warning: long long unsigned int format, oid_t arg (arg 2) fs/reiser4/plugin/file_ops_readdir.c: In function `readdir_common': fs/reiser4/plugin/file_ops_readdir.c:635: warning: long long unsigned int format, oid_t arg (arg 2) fs/reiser4/plugin/file/file.c: In function `delete_object_unix_file': fs/reiser4/plugin/file/file.c:2991: warning: long long unsigned int format, oid_t arg (arg 2) fs/reiser4/plugin/dir_plugin_common.c: In function `rem_entry': fs/reiser4/plugin/dir_plugin_common.c:207: warning: long long unsigned int format, oid_t arg (arg 2) fs/reiser4/plugin/space/bitmap.c: In function `bnode_check_adler32': fs/reiser4/plugin/space/bitmap.c:506: warning: long long unsigned int format, bmap_nr_t arg (arg 2) Compile finished with no other ReiserFS related errors. This was during a stage 1 install on Gentoo 2005.1 on a Sun Ultra II workstation (dual processor, 64-bit). # gcc --version gcc (GCC) 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) Are the failed compiles all on machines running GCC 4.0? --Dan