On Thu, Aug 25, 2005 at 07:18:29AM +0200, Love Hörnquist Åstrand wrote:
> What is the compile error ?

 gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include
        -DROKEN_RENAME -I/usr/include -I/usr/include -I../../lib/krb5
        -I/usr/include/et -Wall -Wmissing-prototypes -Wpointer-arith
        -Wbad-function-cast -Wmissing-declarations -Wnested-externs -g
        -O2 -c afssys.c  -fPIC -DPIC -o .libs/afssys.o
afssys.c: In function 'do_proc':
afssys.c:171: error: '_IOT__IOTBASE_void' undeclared (first use in this
        function)
afssys.c:171: error: (Each undeclared identifier is reported only once
afssys.c:171: error: for each function it appears in.)
afssys.c:171: error: syntax error before ')' token
afssys.c: In function 'k_afs_cell_of_file':
afssys.c:227: error: '_IOT_ViceIoctl' undeclared (first use in this
        function)
afssys.c: In function 'k_unlog':
afssys.c:235: error: '_IOT_ViceIoctl' undeclared (first use in this
        function)
make[3]: *** [afssys.lo] Error 1

> I added autoconf glue for --disable-afs-support, but I want to fix the real
> error too.

There is no kernel AFS support in the Hurd yet (though this issue might
have stirred up some interest to write a translator for it), so the
syscalls in afssys.c fail.

I am not sure what should be done in the generic case (I saw there is
some code for various other operating systems), but I think it makes no
sense to call these syscalls without kernel support?  There was quite a
discussion whether a bogus ioctl should be added to glibc on the Hurd
for this issue, but this got (rightfully, IMHO) discarded by the
maintainers.

Probably the whole kafs directory should not need to be compiled if AFS
is not found (could configure check for that somehow, perhaps?), and the
code in the other parts be conditionalized appropriately.


cheers,

Michael

-- 
Michael Banck
Debian Developer
[EMAIL PROTECTED]
http://www.advogato.org/person/mbanck/diary.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to