Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 17 Oct 2003 13:55:35 -0400
From: Steve Coleman <Steve.Coleman@jhuapl.edu>
Subject: Re: linux/*.h include files
In-reply-to: <6.0.0.22.2.20031017114633.02755bf0@localhost>
To: Flavio Rabello de Souza <rabello@escelsa.com.br>
Cc: cygwin@cygwin.com
Message-id: <3F902D17.3000602@jhuapl.edu>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 8BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
References: <6.0.0.22.2.20031017114633.02755bf0@localhost>

Flavio Rabello de Souza wrote:

>
> I´m trying to compile a C program under cygwin but it uses some linux 
> include files. (#include <linux/in.h> and #include <linux/if_ether.h>)

On my cygwin system I have both <netinet/in.h> and <net/if.h> . These 
are the 'standard' includes that they probably should have used if they 
wanted their code to be portable. Try them and see if that helps. These 
standard include files will usually in turn include the 'platform 
specific' header files for that system. It is best to never use the 
'platform specific' version (e.g. linux/*.h, cygwin/*.h ) directly 
unless it is in code which would never compile and run on any other system.

Steve.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/