Re: Dependencies: non-standard path to system headers

[Ineiev]

Hello, Brian

Thank you for your hint on `make' from CVS. It really works.

On 7/2/08, Brian Dessent <address@hidden> wrote:
> I never said that fopen("c:/foo") wouldn't work, but it's because the
>  Cygwin APIs simply pass-thru arguments to the underlying Win32 APIs that
>  don't look like POSIX paths.  When you use Win32 pathnames in this
>  context you bypass all Cygwin mount table code for instance, which means
>  that if you are relying on the mount table setting of textmode or
>  binmode to change the default file mode, it won't work.

You certainly know more than me. I even never thought of any Cygwin
mount tables. I think you are right in general, but when I tested the
sample, I observed that
1) fopen(...,"w") and fopen(...,"wb") don't translate '\n' to "\r\n"
(it was a surprise for me that '"w" opens in "binary" mode)
2) fopen(...,"wt") translates the character
3) this does not depend on the file name

This probably depends on installation settings (I used the recommended ones).

>  $ tar cf c:/tmp/foo.tar foo
>  rcmd: getaddrinfo: hostname nor servname provided, or not known
>  tar: c\:/tmp/foo.tar: Cannot open: Input/Output error
>  tar: Error is not recoverable: exiting now

--force-local?

Again, I think your idea is generally correct; and I am not going to
work on Cygwin at all (I wish my eyes didn't look at them!), I just
checked whether my package can build there.

Regards,
               Ineiev