Re: C, automake, testing change for compiling old c program

2019-02-07 Thread songbird
Thomas Schmitt wrote: > Hi, hello, :) > songbird's autotools wrote: ^ *snicker* >> configure: WARNING: sys/ioctl.h: see the Autoconf documentation >> configure: WARNING: sys/ioctl.h: section "Present But Cannot Be > > According to > > https://www.gnu.org/s

[SOLVED] C, automake, testing change for compiling old c program

2019-02-07 Thread songbird
wrote: > On Thu, Feb 07, 2019 at 06:06:01AM -0500, songbird wrote: >> i used to be able to compile my program=20 >> using Debian testing/unstable by setting the -m32 >> in CFLAGS and regenerating my environment. >>=20 >> now i'm picking up a warning from the auto stuff=20 >> like: >>=20 >> =3

Re: C, automake, testing change for compiling old c program

2019-02-07 Thread Thomas Schmitt
Hi, songbird's autotools wrote: > configure: WARNING: sys/ioctl.h: see the Autoconf documentation > configure: WARNING: sys/ioctl.h: section "Present But Cannot Be According to https://www.gnu.org/software/autoconf/manual/autoconf-2.64/html_node/Present-But-Cannot-Be-Compiled.html you will

Re: C, automake, testing change for compiling old c program

2019-02-07 Thread tomas
On Thu, Feb 07, 2019 at 06:06:01AM -0500, songbird wrote: > i used to be able to compile my program > using Debian testing/unstable by setting the -m32 > in CFLAGS and regenerating my environment. > > now i'm picking up a warning from the auto stuff > like: > > = > checking sys/ioctl.h

C, automake, testing change for compiling old c program

2019-02-07 Thread songbird
i used to be able to compile my program using Debian testing/unstable by setting the -m32 in CFLAGS and regenerating my environment. now i'm picking up a warning from the auto stuff like: = checking sys/ioctl.h usability... no checking sys/ioctl.h presence... yes configure: WARNING: sys