All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hanson <jhanson@sgi.com>
To: linux-raid@vger.kernel.org
Subject: Re: still compile error
Date: Thu, 29 Sep 2005 09:19:55 -0400	[thread overview]
Message-ID: <pan.2005.09.29.13.19.52.927124@sgi.com> (raw)
In-Reply-To: 433AEBEC.2000003@naa.net

On Wed, 28 Sep 2005 21:15:56 +0200, Norman Schmidt wrote:

> Jeff Hanson schrieb:
> 
>>>Unfortunately, Neils last answer didn´t answer my compile error.
>>>
>>>I just tried mdadm-1.9.0, it compiles well under a standard SuSE 9.3 distro.
>>>
>>>But mdadm-2.0 and mdadm-2.1 do not with the following error:
>>>
>>>gcc -Wall -Werror -Wstrict-prototypes -DCONFFILE=\"/etc/mdadm.conf\" 
>>>-ggdb -DSendmail=\""/usr/sbin/sendmail -t"\"   -c -o bitmap.o bitmap.c
>>>bitmap.c: In function `bitmap_fd_read':
>>>bitmap.c:130: warning: int format, different type arg (arg 3)
>>>make: *** [bitmap.o] Error 1
>>>
>> 
>> 
>> What platform (i386, x86_64, ...).  On my i386 SuSE Linux 9.3 system
>> it compiles just fine with gcc-3.3.5-5.
>> 
>> Is the system updated from YOU?
> 
> It is fully updated with manual YOU. The platform is x86_64, processor 
> is one opteron 246 with 2 GB ram.

Ah - same problem on ia64 system with SLES9SP2

gcc -Wall -Werror -Wstrict-prototypes -DCONFFILE=\"/etc/mdadm.conf\" -ggdb -DSendmail=\""/usr/sbin/sendmail -t"\"   -c -o bitmap.o bitmap.c
bitmap.c: In function `bitmap_fd_read':
bitmap.c:130: warning: int format, different type arg (arg 3)
bitmap.c:171: warning: long long unsigned int format, __u64 arg (arg 3)
bitmap.c: In function `ExamineBitmap':
bitmap.c:265: warning: long long unsigned int format, __u64 arg (arg 2)
bitmap.c:266: warning: long long unsigned int format, __u64 arg (arg 2)
bitmap.c:276: warning: long long unsigned int format, __u64 arg (arg 2)
make: *** [bitmap.o] Error 1

-- 
-----------------------------------------------------------------------
Jeff Hanson - jhanson@sgi.com - Field Technical Analyst

You can choose a ready guide in some celestial voice. 
If you choose not to decide, you still have made a choice. 
You can choose from phantom fears and kindness that can kill; 
I will choose a path that's clear 
I will choose freewill. - Lee/Lifeson/Peart


-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2005-09-29 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 14:57 still compile error Norman Schmidt
2005-09-28 18:02 ` Jeff Hanson
2005-09-28 19:15   ` Norman Schmidt
2005-09-29 13:19     ` Jeff Hanson [this message]

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=pan.2005.09.29.13.19.52.927124@sgi.com \
    --to=jhanson@sgi.com \
    --cc=linux-raid@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.