Re: build failures: syntax error before '{' token

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de> writes:

> Martin Michlmayr wrote:
>> There is a number of packages which fail to build from source on mips
>> like this:
>> 
>> llseek.c:60: warning: return type defaults to `int'
>> llseek.c: In function `_syscall5':
>> llseek.c:62: error: storage class specified for parameter `my_llseek'
>> llseek.c:62: error: syntax error before '{' token
>> llseek.c:66: error: syntax error before "retval"
>> llseek.c:80: error: storage class specified for parameter `do_compat'
>> llseek.c:80: error: parameter `do_compat' is initialized
>> llseek.c:82: error: syntax error before "if"
>> llseek.c:40: warning: `_llseek' declared `static' but never defined
>> llseek.c:60: warning: `_syscall5' defined but not used
>> 
>> See for example
>> http://buildd.debian.org/fetch.php?&pkg=sg3-utils&ver=1.05-2&arch=mips&stamp=1073903670&file=log&as=raw
>> but at least the following packages are affected: tct, raidtools,
>> atari-fdisk, sleuthkit
>> 
>> Can anyone check if this is causes by a broken libc or kernel header,
>> or if those packages include headers they shouldn't.
>
> See #234236, patch available. But basically, those programs should
> use normal userland includes instead.
>
>
> Thiemo

Those programs do use a normal userland include (extrapolating from
util-linux).

The bug appears when using llseek the "normal" way. The system headers
get included indirectly.

MfG
        Goswin