All of lore.kernel.org
 help / color / mirror / Atom feed
* libaal compile fails
@ 2003-10-29  4:33 Sævaldur Gunnarsson
  0 siblings, 0 replies; 8+ messages in thread
From: Sævaldur Gunnarsson @ 2003-10-29  4:33 UTC (permalink / raw)
  To: reiserfs-list


[-- Attachment #1.1: Type: text/plain, Size: 1451 bytes --]

When I try building libaal it fails with the following error message:

make[2]: Entering directory
`/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13/src'
source='file.c' object='libaal_la-file.lo' libtool=yes \
depfile='.deps/libaal_la-file.Plo'
tmpdepfile='.deps/libaal_la-file.TPlo' \
depmode=gcc3 /bin/sh ../depcomp \
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..
-I../include   -D_REENTRANT -D_FILE_OFFSET_BITS=64 -O0 -g -W -Wall
-Wno-unused-parameter -Wredundant-decls -Werror -c -o libaal_la-file.lo
`test -f file.c || echo './'`file.c
rm -f .libs/libaal_la-file.lo
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -D_REENTRANT
-D_FILE_OFFSET_BITS=64 -O0 -g -W -Wall -Wno-unused-parameter
-Wredundant-decls -Werror -c file.c -MT libaal_la-file.lo -MD -MP -MF
.deps/libaal_la-file.TPlo  -fPIC -DPIC -o .libs/libaal_la-file.lo
file.c: In function `file_len':
file.c:213: parse error before '[' token
cc1: warnings being treated as errors
file.c:213: warning: signed and unsigned type in conditional expression
make[2]: *** [libaal_la-file.lo] Error 1
make[2]: Leaving directory
`/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13'
make: *** [all] Error 2
titanium /usr/src/linux/libaal-0.4.13#



Sævaldur Gunnarsson: RHCE
Let justice be done; though the
world perish

[-- Attachment #1.2: Type: text/html, Size: 2152 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libaal compile fails
@ 2003-10-29  8:57 Yury Umanets
  2003-10-29  8:58 ` Yury Umanets
  0 siblings, 1 reply; 8+ messages in thread
From: Yury Umanets @ 2003-10-29  8:57 UTC (permalink / raw)
  To: S?valdur Gunnarsson; +Cc: ReiserFS

 >>When I try building libaal it fails with the following error message:

 >>make[2]: Entering directory 
`/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13/src'
 >>source='file.c' object='libaal_la-file.lo' libtool=yes \
 >>depfile='.deps/libaal_la-file.Plo' 
tmpdepfile='.deps/libaal_la-file.TPlo' \
 >>depmode=gcc3 /bin/sh ../depcomp \
 >>/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. 
-I../include   -D_REENTRANT -D_FILE_OFFSET_BITS=64 -O0 -g -W -Wall 
 >>-Wno-unused-parameter -Wredundant-decls -Werror -c -o 
libaal_la-file.lo `test -f file.c || echo './'`file.c
 >>rm -f .libs/libaal_la-file.lo
 >>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -D_REENTRANT 
-D_FILE_OFFSET_BITS=64 -O0 -g -W -Wall -Wno-unused-parameter 
 >>-Wredundant-decls -Werror -c file.c -MT libaal_la-file.lo -MD -MP -MF 
.deps/libaal_la-file.TPlo  -fPIC -DPIC -o .libs/libaal_la-file.lo
 >>file.c: In function `file_len':
 >>file.c:213: parse error before '[' token
 >>cc1: warnings being treated as errors
 >>file.c:213: warning: signed and unsigned type in conditional expression
 >>make[2]: *** [libaal_la-file.lo] Error 1
 >>make[2]: Leaving directory 
`/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13/src'
 >>make[1]: *** [all-recursive] Error 1
 >>make[1]: Leaving directory 
`/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13'
 >>make: *** [all] Error 2
 >>titanium /usr/src/linux/libaal-0.4.13#

Hello,

This is pretty strange. Line 213 does not contain any "[" tokens and 
suspicious macros. Have you got correct sources? Can you send me line 
213 with context?

Also use please configure with option --disable-Werror specified.

-- 
umka



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libaal compile fails
  2003-10-29  8:57 libaal compile fails Yury Umanets
@ 2003-10-29  8:58 ` Yury Umanets
  2003-11-09  8:59   ` Tupshin Harper
  0 siblings, 1 reply; 8+ messages in thread
From: Yury Umanets @ 2003-10-29  8:58 UTC (permalink / raw)
  To: Yury Umanets; +Cc: S?valdur Gunnarsson, ReiserFS

Yury Umanets wrote:

> >>When I try building libaal it fails with the following error message:
>
> >>make[2]: Entering directory 
> `/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13/src'
> >>source='file.c' object='libaal_la-file.lo' libtool=yes \
> >>depfile='.deps/libaal_la-file.Plo' 
> tmpdepfile='.deps/libaal_la-file.TPlo' \
> >>depmode=gcc3 /bin/sh ../depcomp \
> >>/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. 
> -I../include   -D_REENTRANT -D_FILE_OFFSET_BITS=64 -O0 -g -W -Wall 
> >>-Wno-unused-parameter -Wredundant-decls -Werror -c -o 
> libaal_la-file.lo `test -f file.c || echo './'`file.c
> >>rm -f .libs/libaal_la-file.lo
> >>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -D_REENTRANT 
> -D_FILE_OFFSET_BITS=64 -O0 -g -W -Wall -Wno-unused-parameter 
> >>-Wredundant-decls -Werror -c file.c -MT libaal_la-file.lo -MD -MP 
> -MF .deps/libaal_la-file.TPlo  -fPIC -DPIC -o .libs/libaal_la-file.lo
> >>file.c: In function `file_len':
> >>file.c:213: parse error before '[' token
> >>cc1: warnings being treated as errors
> >>file.c:213: warning: signed and unsigned type in conditional expression
> >>make[2]: *** [libaal_la-file.lo] Error 1
> >>make[2]: Leaving directory 
> `/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13/src'
> >>make[1]: *** [all-recursive] Error 1
> >>make[1]: Leaving directory 
> `/raid/disc0/usr/src/linux-2.6.0-test9/libaal-0.4.13'
> >>make: *** [all] Error 2
> >>titanium /usr/src/linux/libaal-0.4.13#
>
> Hello,
>
> This is pretty strange. Line 213 does not contain any "[" tokens and 
> suspicious macros. Have you got correct sources? Can you send me line 
> 213 with context?
>
> Also use please configure with option --disable-Werror specified.
>
Forgot to ask. Do you use recent snapshot of libaal?

-- 
umka



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libaal compile fails
  2003-10-29  8:58 ` Yury Umanets
@ 2003-11-09  8:59   ` Tupshin Harper
  2003-11-09  9:46     ` Tupshin Harper
  0 siblings, 1 reply; 8+ messages in thread
From: Tupshin Harper @ 2003-11-09  8:59 UTC (permalink / raw)
  To: Yury Umanets; +Cc: S?valdur Gunnarsson, ReiserFS

Yury Umanets wrote:

> Yury Umanets wrote:
>
>> >>When I try building libaal it fails with the following error message:
>>
> Forgot to ask. Do you use recent snapshot of libaal?
>
FWIW, I get the exact same problem as Saevaldur. Using 
libaal-0.4.13.tar.gz, and attempting to compile on a Debian Sid x86 
machine. I can only imagine it's a gcc parsing bug (line 213 indeed does 
not have a square bracket). GCC is 3.3.2. Commenting out the check 
performed by that line results in a sucesful compilation.

-Tupshin


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libaal compile fails
  2003-11-09  8:59   ` Tupshin Harper
@ 2003-11-09  9:46     ` Tupshin Harper
  2003-11-10  8:51       ` Yury V. Umanets
  0 siblings, 1 reply; 8+ messages in thread
From: Tupshin Harper @ 2003-11-09  9:46 UTC (permalink / raw)
  To: ReiserFS; +Cc: Yury Umanets, S?valdur Gunnarsson

Tupshin Harper wrote:

> Yury Umanets wrote:
>
>> Yury Umanets wrote:
>>
>>> >>When I try building libaal it fails with the following error message:
>>>
>> Forgot to ask. Do you use recent snapshot of libaal?
>>
> FWIW, I get the exact same problem as Saevaldur. Using 
> libaal-0.4.13.tar.gz, and attempting to compile on a Debian Sid x86 
> machine. I can only imagine it's a gcc parsing bug (line 213 indeed 
> does not have a square bracket). GCC is 3.3.2. Commenting out the 
> check performed by that line results in a sucesful compilation.
>
> -Tupshin
>
A bit more info.

It is not a problem with the gcc version, as the same message comes from 
3.2 and 2.95.

I'm guessing that it emerges from macros expanded through multiple 
layers of expansion.
BLKGETSIZE64 expands to _
IOR(0x12, 114, sizeof(uint64_t))

_IOR expands to
_IOC(_IOC_READ,(type),(nr),(_IOC_TYPECHECK(size)))

and _IOC_TYPECHECK expands to
((sizeof(t) == sizeof(t[1]) && sizeof(t) < (1 << _IOC_SIZEBITS)) ? 
sizeof(t) : __invalid_size_argument_for_IOC)

which is the first hint of a bracket on that line. That's as far as I'm 
going ;-).

-Tupshin


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libaal compile fails
  2003-11-09  9:46     ` Tupshin Harper
@ 2003-11-10  8:51       ` Yury V. Umanets
  0 siblings, 0 replies; 8+ messages in thread
From: Yury V. Umanets @ 2003-11-10  8:51 UTC (permalink / raw)
  To: Tupshin Harper; +Cc: ReiserFS, S?valdur Gunnarsson

On Sun, 2003-11-09 at 12:46, Tupshin Harper wrote:
> Tupshin Harper wrote:
> 
> > Yury Umanets wrote:
> >
> >> Yury Umanets wrote:
> >>
> >>> >>When I try building libaal it fails with the following error message:
> >>>
> >> Forgot to ask. Do you use recent snapshot of libaal?
> >>
> > FWIW, I get the exact same problem as Saevaldur. Using 
> > libaal-0.4.13.tar.gz, and attempting to compile on a Debian Sid x86 
> > machine. I can only imagine it's a gcc parsing bug (line 213 indeed 
> > does not have a square bracket). GCC is 3.3.2. Commenting out the 
> > check performed by that line results in a sucesful compilation.
> >
> > -Tupshin
> >
> A bit more info.
> 
> It is not a problem with the gcc version, as the same message comes from 
> 3.2 and 2.95.
> 
> I'm guessing that it emerges from macros expanded through multiple 
> layers of expansion.
> BLKGETSIZE64 expands to _
> IOR(0x12, 114, sizeof(uint64_t))
> 
> _IOR expands to
> _IOC(_IOC_READ,(type),(nr),(_IOC_TYPECHECK(size)))
> 
> and _IOC_TYPECHECK expands to
> ((sizeof(t) == sizeof(t[1]) && sizeof(t) < (1 << _IOC_SIZEBITS)) ? 
> sizeof(t) : __invalid_size_argument_for_IOC)
> 
> which is the first hint of a bracket on that line. That's as far as I'm 
> going ;-).
> 
> -Tupshin
Hello,

First of all thanks for shutting a bug. There is really one error in the
macro you have pointed to. 

Old variant is:

#if defined(__linux__) && defined(_IOR) && !defined(BLKGETSIZE64)
#   define BLKGETSIZE64 _IOR(0x12, 114, sizeof(uint64_t))
#endif

New variant (right one) is:

#if defined(__linux__) && defined(_IOR) && !defined(BLKGETSIZE64)
#   define BLKGETSIZE64 _IOR(0x12, 114, uint64_t)
#endif

But I don't think, that problem is related to it. Also, we have not such
a error on gcc 3.3.1 and older. Can you try to build libaal with this
fix and see what happens?


Thanks.
-- 
umka


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libaal compile fails
@ 2003-11-19 19:35 Eric Wong
  2003-11-20  8:09 ` Yury V. Umanets
  0 siblings, 1 reply; 8+ messages in thread
From: Eric Wong @ 2003-11-19 19:35 UTC (permalink / raw)
  To: reiserfs-list, umka

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.

-- 
Eric Wong  (normalperson on OFTC and Freenode)

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libaal compile fails
  2003-11-19 19:35 Eric Wong
@ 2003-11-20  8:09 ` Yury V. Umanets
  0 siblings, 0 replies; 8+ messages in thread
From: Yury V. Umanets @ 2003-11-20  8:09 UTC (permalink / raw)
  To: Eric Wong; +Cc: reiserfs-list

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


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2003-11-20  8:09 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-10-29  8:57 libaal compile fails 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
  -- strict thread matches above, loose matches on Subject: below --
2003-11-19 19:35 Eric Wong
2003-11-20  8:09 ` Yury V. Umanets
2003-10-29  4:33 Sævaldur Gunnarsson

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.