Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 17 Oct 2003 13:55:35 -0400 From: Steve Coleman Subject: Re: linux/*.h include files In-reply-to: <6.0.0.22.2.20031017114633.02755bf0@localhost> To: Flavio Rabello de Souza Cc: cygwin AT cygwin DOT 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 X-Accept-Language: en-us, en References: <6 DOT 0 DOT 0 DOT 22 DOT 2 DOT 20031017114633 DOT 02755bf0 AT localhost> Flavio Rabello de Souza wrote: > > I´m trying to compile a C program under cygwin but it uses some linux > include files. (#include and #include ) On my cygwin system I have both and . 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/