Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
> > Unfortunately, it'll turn *all* warnings into errors; the > only warnings I want turned into errors are the warnings for > undefined references, as there might be other warnings that > are harmless *and* difficult if not impossible to eliminate > in a configure script. > > That's probably

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
> > What autoconf wants is to have an attempt to compile and link > a program that refers to a particular symbol cause, on a > system that doesn't have that symbol in the libraries being > used, the linker to exit with a non-zero exit status; that's > the sense in which the linker needs to fai

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
> > > configure:3849: checking for getifaddrs > > configure:3899: cc -o conftest -g -O2 conftest.c >&5 > > Warning(1028): getifaddrs_ is an undefined reference > > That's only a warning? Is there a way to force cc on QNX4 to > *fail* if some symbol isn't found? If so, autoconf's > AC_CHECK

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
> > > Here is the relevant output, from config.log: > > Is there earlier "checking for getifaddr" output in config.log? > configure:3849: checking for getifaddrs configure:3899: cc -o conftest -g -O2 conftest.c >&5 Warning(1028): getifaddrs_ is an undefined reference file conftest.o(/home/pt

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
Here is the relevant output, from config.log: configure:3348: checking ifaddrs.h usability configure:3361: cc -c -g -O2 conftest.c >&5 configure(3393): Error! E1055: Unable to open 'strings.h' configure(3396): Error! E1055: Unable to open 'inttypes.h' configure(3405): Error! E1055: Unable to open

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
> Unable to open 'ifaddrs.h'" > The configure script reports: > checking ifaddrs.h usability... yes > checking ifaddrs.h presence... no > checking for ifaddrs.h... no > What can I do about this? (The file does not exist.) Okay, instead of being delerious, I will try to be helpful... There is

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
QNX 4.25 ?? Egads, the slope gets more slippery. Paul Thomas - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
> Is the "getifaddrs()" you're using part of QNX4, or is it > from some add-on library, e.g. taking the eCos implementation > and porting it to QNX4? "getifaddrs()" is not part of QNX4. There is no connection whatsoever. It is utilized in the libpcap file, 'fad-getad.c'. This source file is

Re: [tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
> If that's the QNX4 documentation, then... > > > SYNOPSIS > > #include > > #include > > #include > > ...I would infer that QNX4 - or its development kit, if > that's where header files come from, or wherever header files > for whichever library "getifaddrs()" is in come from

[tcpdump-workers] Libpcap build error

2004-12-16 Thread Paul Thomas
his? (The file does not exist.) Thanks, Paul Thomas - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.