All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: ReiserFS <reiserfs-list@namesys.com>
Cc: Yury Umanets <umka@namesys.com>, S?valdur Gunnarsson <addi@root.is>
Subject: Re: libaal compile fails
Date: Sun, 09 Nov 2003 01:46:07 -0800	[thread overview]
Message-ID: <3FAE0CDF.9080104@tupshin.com> (raw)
In-Reply-To: <3FAE01DF.7090802@tupshin.com>

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


  reply	other threads:[~2003-11-09  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

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=3FAE0CDF.9080104@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=addi@root.is \
    --cc=reiserfs-list@namesys.com \
    --cc=umka@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.