All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Oglesby <doglesby@teleformix.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: "Hans Reiser" <reiser@namesys.com>,
	"Jake Maciejewski" <maciejej@msoe.edu>,
	"Łukasz Mierzwa" <prymitive@pcserwis.hopto.org>,
	"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>,
	vs <vs@thebsh.namesys.com>
Subject: Re: reiser4 for 2.6.13 is available on our website
Date: Thu, 29 Sep 2005 21:59:59 -0500	[thread overview]
Message-ID: <433CAA2F.2030708@teleformix.com> (raw)
In-Reply-To: <e692861c050929162314ffcc7c@mail.gmail.com>

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

  reply	other threads:[~2005-09-30  2:59 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 [this message]
2005-09-30  3:03           ` Dan Oglesby
2005-09-30  5:02             ` Dan Oglesby
2005-09-30  6:01               ` Dan Oglesby
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=433CAA2F.2030708@teleformix.com \
    --to=doglesby@teleformix.com \
    --cc=gmaxwell@gmail.com \
    --cc=maciejej@msoe.edu \
    --cc=prymitive@pcserwis.hopto.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@thebsh.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.