[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: HAVE_RELIABLE_FIONREAD & ioctl
From: |
Bruno Haible |
Subject: |
Re: HAVE_RELIABLE_FIONREAD & ioctl |
Date: |
Thu, 21 Jul 2011 02:19:07 +0200 |
User-agent: |
KMail/1.13.6 (Linux/2.6.37.6-0.5-desktop; KDE/4.6.0; x86_64; ; ) |
Hi Sam,
> I pulled ioctl module from gnulib because of a compilation error about
> "ioctl_used_without_requesting_gnulib_ioctl" and I am wondering whether
> the HAVE_RELIABLE_FIONREAD et al are still relevant.
The problem that clisp/src/m4/ioctl.m4 tests against is fixed in Solaris 7
and newer, but is present in Solaris 2.6, FreeBSD 6.4, IRIX 6.5.
> Also, I get this error on linux:
>
> /home/sds/src/clisp/sf/clisp/build-g-gxx/gllib/sys/ioctl.h:361: error:
> declaration of C function 'int ioctl(int, int, ...)' conflicts with
> /usr/include/sys/ioctl.h:42: error: previous declaration 'int ioctl(int, long
> unsigned int, ...)' here
> make: *** [spvw.o] Error 1
>
> (after I removed the ioctl declaration from unix.h)
> what's wrong?
In this situation (on Linux, which has the non-POSIX declaration for ioctl())
REPLACE_IOCTL should be set to 1 by config.status, so that gllib/sys/ioctl.h
provides a declaration for rpl_ioctl, not ioctl. Somehow this is not happening.
Can you look in config.status what is the value of REPLACE_IOCTL? And if it is
0, look up in config.log the details of "checking for ioctl with POSIX
signature ..."
Bruno
--
In memoriam Pancho Villa <http://en.wikipedia.org/wiki/Pancho_Villa>