From: Gabor Alsecz <alseczg@gmail.com>
To: cygwin@cygwin.com
Subject: /usr/include path issue
Date: Thu, 19 May 2011 06:54:00 -0000 [thread overview]
Message-ID: <BANLkTima=eDmHqsHA-i4BzF-ko77HjY5pA@mail.gmail.com> (raw)
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
So how can i add the fine include directory path to the compiler or
cygwin bash to find the .h includes?
Same issue (include .h file(s) not found) when i try to
compile/configure Kannel under cygwin
Regards,
Gabor
--
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 reply other threads:[~2011-05-19 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 6:54 Gabor Alsecz [this message]
2011-05-19 10:20 ` Csaba Raduly
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='BANLkTima=eDmHqsHA-i4BzF-ko77HjY5pA@mail.gmail.com' \
--to=alseczg@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).