Mail Archives: cygwin/2008/08/02/15:13:18
Jason Pyeron wrote:
> I am trying to compile gcc (and later ghdl) and it seems that certain files are
> inaccessible to cygwin, while easily accessed from non-cygwin applications. I
> installed another disk and formatted it FAT32 as a workaround right now, but
> what might the problem be or where can I start researching this one?
If you check your mount table I think you'll see that /usr/src has been
switched to managed mode, yet those filenames contain uppercase
characters that are not escaped. I don't recall right now all the
circumstances as to which postinstall script makes this change, probably
one of the gcc postinstalls. Or maybe it's setup itself when you select
any source package. I think the reasoning was that one or more source
packages contain filenames that cannot be represented by Win32 filename
rules, so the /usr/src dir has to be set to managed mode. The problem
is that managed mounts only work when the files in them are created by
Cygwin, which does the filename mangling. If something else (in this
case setup) writes files to a managed mount then the mangling won't
occur and Cygwin will get confused because it expects the filenames to
have been mangled.
What I would do: turn off managed mode, erase everything in /usr/src,
turn managed mode back on, unpack the source packages by hand with tar.
Further, I'm pretty sure that managed mode is not required for any of
the FSF gcc parts, only for one of the out-of-tree add-on languages like
D or Pascal. So if you're not unpacking/building those you can skip the
whole ordeal.
Brian
--
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/
- Raw text -