From: Dan Oglesby <doglesby@teleformix.com>
To: Dan Oglesby <doglesby@teleformix.com>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: reiser4 for 2.6.13 is available on our website
Date: Fri, 30 Sep 2005 01:01:53 -0500 [thread overview]
Message-ID: <433CD4D1.5090100@teleformix.com> (raw)
In-Reply-To: <433CC6FA.1050001@teleformix.com>
Dan Oglesby wrote:
> Dan Oglesby wrote:
>
>> Dan Oglesby wrote:
>>
>>> Gregory Maxwell wrote:
>>>
>>>> On 9/29/05, Hans Reiser <reiser@namesys.com> 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
>>
>>
>>
>>
>> Nevermind, I just saw Jake's email (failed on gcc 3.4.4).
>>
>> --Dan
>>
> From my Slackware 10.2 x86 system tonight:
>
> In file included from fs/reiser4/lock.h:15,
> from fs/reiser4/context.h:14,
> from fs/reiser4/debug.c:25:
> fs/reiser4/txnmgr.h: In function `spin_atom_init':
> fs/reiser4/txnmgr.h:512: error: duplicate case value
> fs/reiser4/txnmgr.h:512: error: previously used here
> fs/reiser4/txnmgr.h: In function `spin_txnh_init':
> fs/reiser4/txnmgr.h:513: error: duplicate case value
> fs/reiser4/txnmgr.h:513: error: previously used here
> fs/reiser4/txnmgr.h: In function `spin_txnmgr_init':
> fs/reiser4/txnmgr.h:514: error: duplicate case value
> fs/reiser4/txnmgr.h:514: error: previously used here
> In file included from fs/reiser4/context.h:14,
> from fs/reiser4/debug.c:25:
> fs/reiser4/lock.h: In function `spin_stack_init':
> fs/reiser4/lock.h:198: error: duplicate case value
> fs/reiser4/lock.h:198: error: previously used here
> In file included from fs/reiser4/znode.h:16,
> from fs/reiser4/tree.h:15,
> from fs/reiser4/super.h:9,
> from fs/reiser4/debug.c:26:
> fs/reiser4/jnode.h: In function `spin_jnode_init':
> fs/reiser4/jnode.h:344: error: duplicate case value
> fs/reiser4/jnode.h:344: error: previously used here
> fs/reiser4/jnode.h: In function `spin_jload_init':
> fs/reiser4/jnode.h:348: error: duplicate case value
> fs/reiser4/jnode.h:348: error: previously used here
> In file included from fs/reiser4/super.h:9,
> from fs/reiser4/debug.c:26:
> fs/reiser4/tree.h: In function `spin_epoch_init':
> fs/reiser4/tree.h:169: error: duplicate case value
> fs/reiser4/tree.h:169: error: previously used here
> In file included from fs/reiser4/debug.c:26:
> fs/reiser4/super.h: In function `spin_super_init':
> fs/reiser4/super.h:379: error: duplicate case value
> fs/reiser4/super.h:379: error: previously used here
> make[2]: *** [fs/reiser4/debug.o] Error 1
> make[1]: *** [fs/reiser4] Error 2
> make: *** [fs] Error 2
>
> # gcc --version
> gcc (GCC) 3.3.6
>
> Same copy of the 2.6.13.1 kernel source and patch as the compile I did
> on the Gentoo machine tonight.
>
> --Dan
Last update for tonight/this morning...
On a Slackware 10.1 machine (32bit/x86), with gcc 3.3.4 there were no
warnings or errors related to ReiserFS4 (got a couple with some
deprecated bits of serial port code, nothing from filesystem code).
I'll definately get some ReiserFS4 filesystems online this weekend, and
see how hard I can push this FS on my various machines.
--Dan
next prev parent reply other threads:[~2005-09-30 6:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 17:25 reiser4 for 2.6.13 is available on our website Hans Reiser
2005-09-29 18:24 ` Łukasz Mierzwa
2005-09-29 22:09 ` Jake Maciejewski
2005-09-29 22:32 ` Hans Reiser
2005-09-29 23:23 ` Gregory Maxwell
2005-09-30 2:59 ` Dan Oglesby
2005-09-30 3:03 ` Dan Oglesby
2005-09-30 5:02 ` Dan Oglesby
2005-09-30 6:01 ` Dan Oglesby [this message]
2005-09-30 8:31 ` Alexander Zarochentsev
2005-09-30 12:01 ` Łukasz Mierzwa
2005-10-01 7:20 ` Jake Maciejewski
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=433CD4D1.5090100@teleformix.com \
--to=doglesby@teleformix.com \
--cc=reiserfs-list@namesys.com \
/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.