How do you find the header file you need?

[Jim Holder]

I tried building libpcap and tcpdump from my Red Hat 7 RPMs. The
tcpdump make couldn't find ioccom.h and sockio.h.

When a header file is missing, how do you find it?

Thanks.

 

[Ben Pfaff]

I tried building libpcap and tcpdump from my Red Hat 7 RPMs. The
tcpdump make couldn't find ioccom.h and sockio.h.

When a header file is missing, how do you find it?

Your question is outside the domain of comp.lang.c, which discusses
only the standard C programming language, including the standard C
library. This is a remarkably narrow topic compared to what many
people expect.

For your convenience, the list below contains topics that are not
on-topic for comp.lang.c, and suggests newsgroups for you to explore
if you have questions about these topics. Please do observe proper
netiquette before posting to any of these newsgroups. In particular,
you should read the group's charter and FAQ, if any (FAQs are
available from www.faqs.org and other sources). If those fail to
answer your question then you should browse through at least two weeks
of recent articles to make sure that your question has not already
been answered.

* OS-specific questions, such as how to clear the screen,
access the network, list the files in a directory, or read
"piped" output from a subprocess. These questions should be
directed to OS-specific newsgroups, such as
comp.os.ms-windows.programmer.misc, comp.unix.programmer, or
comp.os.linux.development.apps.

* Compiler-specific questions, such as installation issues and
locations of header files. Ask about these in
compiler-specific newsgroups, such as gnu.gcc.help or
comp.os.ms-windows.programmer.misc. Questions about writing
compilers are appropriate in comp.compilers.

* Processor-specific questions, such as questions about
assembly and machine code. x86 questions are appropriate in
comp.lang.asm.x86, embedded system processor questions may
be appropriate in comp.arch.embedded.

* ABI-specific questions, such as how to interface assembly
code to C. These questions are both processor- and
OS-specific and should typically be asked in OS-specific
newsgroups.

* Algorithms, except questions about C implementations of
algorithms. "How do I implement algorithm X in C?" is not a
question about a C implementation of an algorithm, it is a
request for source code. Newsgroups comp.programming and
comp.theory may be appropriate.

* Making C interoperate with other languages. C has no
facilities for such interoperation. These questions should
be directed to system- or compiler-specific newsgroups. C++
has features for interoperating with C, so consider
comp.lang.c++ for such questions.

* The C standard, as opposed to standard C. Questions about
the C standard are best asked in comp.std.c.

* C++. Please do not post or cross-post questions about C++
to comp.lang.c. Ask C++ questions in C++ newsgroups, such
as comp.lang.c++ or comp.lang.c++.moderated.

* Test posts. Please test in a newsgroup meant for testing,
such as alt.test.

news.groups.questions is a good place to ask about the appropriate
newsgroup for a given topic.

 

[Malcolm]

I tried building libpcap and tcpdump from my Red Hat 7 RPMs. The
tcpdump make couldn't find ioccom.h and sockio.h.

When a header file is missing, how do you find it?

The technically correct answer is using search tools, as you would find any
file (it will be called something like "find" or "dir" on your machine).

However normally if a header is missing, that means that the body of code
which it is the header for is also missing. For instance "sockio" sounds
like "socket input/output" and there is a good chance that it is not
compatible with sockets on your platform. In this case, you can't build the
library.

 

[nrk]

Ben Pfaff wrote:

<snip off-topic original post>

<snip long, elaborate reply>

While I definitely like the idea of this sort of a comprehensive reply to an
off-topic post, I think it is counter-productive to actually post the full
text as a response to each and every off-topic post in this group (not to
mention, a terrific waste of bandwidth). Instead, put up a webpage with
the message, and your response on the newsgroup can merely state that the
OP is off-topic and should refer to your <URL> for details/guidelines on
what's considered topical in clc.

Just my $0.02

-nrk.

 

[CBFalconer]

Ben Pfaff wrote:

<snip off-topic original post>

<snip long, elaborate reply>

While I definitely like the idea of this sort of a comprehensive
reply to an off-topic post, I think it is counter-productive to
actually post the full text as a response to each and every
off-topic post in this group (not to mention, a terrific waste of
bandwidth). Instead, put up a webpage with the message, and your
response on the newsgroup can merely state that the OP is
off-topic and should refer to your <URL> for details/guidelines
on what's considered topical in clc.

Just my $0.02

On the contrary, Ben's original post consumed something like 70
lines of less than 70 chars each, or under 5k bytes. It covers
the subject and gobbled up about 1 sec of transfer time at 50 odd
kbaud. A URL reference requires that the end-user be on line (I
am not), willing to abandon his current thread (reading the group)
etc. If that user was not capable of recognizing the OT nature in
the first place, there is no need to complicate instructing him.

 

[Randy Howard]

I tried building libpcap and tcpdump from my Red Hat 7 RPMs. The
tcpdump make couldn't find ioccom.h and sockio.h.

When a header file is missing, how do you find it?

Not surprisingly, "man find" will contain your answer.