Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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, 5 Nov 2004 14:09:31 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Binary read on textmode mount
Message-ID: <20041105190931.GG25396@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT CYG DOT 4 DOT 58 DOT 0411051050240 DOT 3688 AT Crunch DOT bcgssbd DOT sciatl DOT com> <20041105164033 DOT 9CEF11B3FA AT cgf DOT cx> <Pine DOT CYG DOT 4 DOT 58 DOT 0411051309580 DOT 3688 AT Crunch DOT bcgssbd DOT sciatl DOT com> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20041105133813 DOT 043d0a98 AT pop DOT prospeed DOT net> <Pine DOT CYG DOT 4 DOT 58 DOT 0411051345520 DOT 3688 AT Crunch DOT bcgssbd DOT sciatl DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0411051345520.3688@Crunch.bcgssbd.sciatl.com>
User-Agent: Mutt/1.4.1i

On Fri, Nov 05, 2004 at 01:52:34PM -0500, Shaffer, Kenneth wrote:
>Now, now, it seems perfectly legitimate to write a windows program
>which can access files created by gcc to run under cygwin.

Of course, if you know *exactly* what you're doing, you can get away
with all sorts of stuff in any walk of life.  You can run with
scissors.  You can use gasoline to start a fire.  You can have
52 different versions of the cygwin DLL on your system.

You didn't know *exactly* what you were doing and caused yourself
some grief thereby.  That's why, in general, it is a very bad idea
to include cygwin header files in pure windows files.

>The structure of the a.out shouldn't depend on whether I'm compiling
>under windows, cygwin, linux, solaris, whatever.

You may be able to get away with this with a.out.h (which, if so, makes
me wonder why you were having problems to begin with) but you can't
just make sweeping statements like this for any old header file.

>I just need the a.out.h file for the system on which it was created.
>(Time to change the subject line, I guess)

If this is all that you needed then it's hard to understand why we are
even having this discussion with this particular subject line.  AFAICT,
a.out.h, doesn't need fcntl.h but, if it does, that sort of proves the
point.

cgf

--
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/