>
> 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
>
> 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
On Dec 16, 2004, at 4:44 PM, Guy Harris wrote:
Oh, well - I guess that means that autoconf won't work on QNX (or
QNX4, at least - it won't work on any of the QNX versions where the
Watcom linker is being used).
Or, more precisely, "I guess that means that autoconf-generated
configure scripts tha
On Dec 16, 2004, at 4:30 PM, Paul Thomas wrote:
But, the behavior "do not create executable if undefined symbols
are present" is not the same as having the linker "fail", is it?
What autoconf wants is to have an attempt to compile and link a program
that refers to a particular symbol cause, on a s
On Dec 16, 2004, at 3:10 PM, Paul Thomas wrote:
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
On Dec 16, 2004, at 2:47 PM, Paul Thomas wrote:
Here is the relevant output, from config.log:
Is there earlier "checking for getifaddr" output in config.log?
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.
On Dec 16, 2004, at 3:40 PM, Paul Thomas wrote:
There is a wcc option, "-we" (treat all warnings as errors) described
as
follows.
"By default, the compiler continues to create an object file when
there are
warnings produced. This option can be used to treat all warnings as
errors,
thereby prev
>
> > 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
On Dec 16, 2004, at 1:23 PM, Paul Thomas wrote:
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
>
> > 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
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
On Dec 16, 2004, at 2:08 PM, Paul Thomas wrote:
There is a very clear dependency on "ifaddrs.h".
Am I right to say that it is needed to build libpcap?
It's needed to build libpcap *IF* libpcap is to call "getifaddrs()" in
the implementation of "pcap_findalldevs()". Otherwise, it's not
needed.
I
> 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
Hello:
> I am trying to build libpcap for QNX 4.25, and am experiencing the
following error:
> 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
> 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
On Dec 16, 2004, at 12:38 PM, Paul Thomas wrote:
Unfortunately, there is no connection between the quoted
Man-Page-snippet
and QNX.
So what's the "TCP/IP Library Reference", whence that man page snipped
came, a manual for?
I Googled for "TCP/IP Library Reference" and "System Library Functions"
> 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
On Dec 16, 2004, at 12:15 PM, Paul Thomas wrote:
From the TCP/IP Library Reference / System Library Functions Manual
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 com
On Dec 16, 2004, at 10:02 AM, Paul Thomas wrote:
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.)
Ask QNX; at least according to this page:
http://www.qnx.com/devel
Hello:
I am trying to build libpcap for QNX 4.25, and am experiencing
the following error:
"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 n
20 matches
Mail list logo
