From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin@cygwin.com
Subject: Re: /usr/include path issue
Date: Thu, 19 May 2011 10:20:00 -0000 [thread overview]
Message-ID: <BANLkTiknH0yhdBP8yw5EZQUyO_ewixGy6w@mail.gmail.com> (raw)
In-Reply-To: <BANLkTima=eDmHqsHA-i4BzF-ko77HjY5pA@mail.gmail.com>
On Thu, May 19, 2011 at 8:54 AM, Gabor Alsecz wrote:
> Hi All,
>
> I am using the latest cygwin installation and I have an issue with my
> /usr/include directory under cygwin bash.
>
> my .c file snippet looks like this:
>
> #include <netdb.h>
> #include <sys/types.h>
> #include <sys/socket.h>
> #include <netinet/in.h>
> #include <arpa/inet.h>
>
> And when running gcc from bash with the followin command:
> gcc getip.c
>
> i receive the following error:
> fatal error: netdb.h: No such file or directory
Hi Gabor,
do you actually have a netdb.h ? What does
$ find /usr/include/ -name netdb.h
print ?
You can check which directories gcc searches for include files by
adding the -v switch to the gcc command line:
gcc -v getip.c
netdb.h is part of the cygwin package (according to
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=netdb.h) which is
always installed; it should be in /usr/include, which is searched by
gcc by default.
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-05-19 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 6:54 Gabor Alsecz
2011-05-19 10:20 ` Csaba Raduly [this message]
2011-05-19 10:34 ` Gábor Alsecz
2011-05-19 16:32 ` Christopher Faylor
2011-05-19 12:45 ` Nellis, Kenneth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTiknH0yhdBP8yw5EZQUyO_ewixGy6w@mail.gmail.com \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).