All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yury V. Umanets" <umka@namesys.com>
To: Eric Wong <eric@yhbt.net>
Cc: reiserfs-list@namesys.com
Subject: Re: libaal compile fails
Date: Thu, 20 Nov 2003 11:09:12 +0300	[thread overview]
Message-ID: <1069315752.1687.26.camel@firefly> (raw)
In-Reply-To: <20031119193539.GE24852@BL4ST>

On Wed, 2003-11-19 at 22:35, Eric Wong wrote:
> Hi, I'm still having problems with compiling libaal on Debian
> sid/unstable after trying the proposed-fix here:
> 
> http://marc.theaimsgroup.com/?l=reiserfs&m=106841085428596&w=2
> 
> Here is the output I got after making the above changes to the BLKGETSIZE64
> macro:
> 
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -D_REENTRANT
> -D_FILE_OFFSET_BITS=64 -O0 -g -W -Wall -Wno-unused -Wredundant-decls
> -Werror -c file.c -Wp,-MD,.deps/libaal_la-file.TPlo  -fPIC -DPIC -o
> .libs/libaal_la-file.lo
> file.c: In function `file_len':
> file.c:213: warning: signed and unsigned type in conditional expression
> make[2]: *** [libaal_la-file.lo] Error 1
> 
> I'm using gcc 3.3.2 and the somewhat troublesome (yet standard fare in
> Debian unstable nowadays) linux-kernel-headers package that provides
> kernel headers for glibc.  I'm running 2.6.0-test9
> 
> This package compiles fine on my Debian stable/Woody system, however.
> 
> If you need any more info, let me know.  Thanks.
Hello,

Thanks for shooting the bug, will be fixed.

Use --disable-Werror option in configure as temporal workaround. Next
snapshot has it turned on by default. 
-- 
umka


  reply	other threads:[~2003-11-20  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 19:35 libaal compile fails Eric Wong
2003-11-20  8:09 ` Yury V. Umanets [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-29  8:57 Yury Umanets
2003-10-29  8:58 ` Yury Umanets
2003-11-09  8:59   ` Tupshin Harper
2003-11-09  9:46     ` Tupshin Harper
2003-11-10  8:51       ` Yury V. Umanets
2003-10-29  4:33 Sævaldur Gunnarsson

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=1069315752.1687.26.camel@firefly \
    --to=umka@namesys.com \
    --cc=eric@yhbt.net \
    --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.