This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Cygwin 1.0 CD
- To: John Fralinger <fralinjh at ei dot dupont dot com>, cygwin at sourceware dot cygnus dot com
- Subject: Re: Cygwin 1.0 CD
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Tue, 9 Nov 1999 15:31:55 -0500
- References: <19991109194426.11572.rocketmail@web123.yahoomail.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
Actually, it sounds to me like the problem is as simple as either not
creating directories directly under the installed directory and/or
mounting your source directories as text mounts.
If you are copying include files into a directory mounted off the cygwin
root you will have to convert them to CRLF format. Or, you could
remount your root as non-binary.
cgf
On Tue, Nov 09, 1999 at 11:44:26AM -0800, Earnie Boyd wrote:
>Your problem is most likely due to the duplicate registry key for the /
>directory. cd to the bin directory containing mount and umount and issue
>
>./sh -c './umount / && mount c:\\ /'
>
>
>Replace the c:\\ with the device/directory of your choice.
>
>--- John Fralinger <fralinjh@ei.dupont.com> wrote:
>>Is this the method for reporting Cygwin 1.0 CD problems?
>>
>>The Cygwin 1.0 installer appears to mount / and all of it's subdirs as
>>binary.
>>
>>I am running into a problem installing header files.
>>
>>The compile fails whenever the header file has a \ at the end (for line
>>continuation). I suspect because of the CR/LF.
>>
>>Makefiles with line continuations also do not work when executed from
>>any of the Cygwin paths.
>>
>>Are we supposed to always convert text files to unix format before
>>copying them to the cygwin mount point?
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com