Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
You could create a Windows symbolic link using the Windows 'mklink' tool though, and it should work both in cmd.exe and in Cygwin. Thanks for the info and Corinna's quote. Probably I'll just create windows symlinks like from c:\users\tuli\bin\gcc.exe to c:\cygwin\bin\gcc-3.exe so that cygwin updates wouldn't break my modifications. Cheers, Tuli -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
On 01/01/2010 04:52 PM, Lee Rothstein wrote: Will Windows junctions (for the path; plus the file name) work, here, Andy? (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx) NTFS junctions are for directories only.. For files and directories, one could use mklink on Vista and newer, with the caveats mentioned here http://en.wikipedia.org/wiki/Symbolic_link#Windows_Vista_symbolic_link. Oh and for all those wondering, this still isn't enough to be a drop-in replacement for Cygwin's symbolic links unfortunately. If you're curious about this, see the email archives for discussions about it. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
Will Windows junctions (for the path; plus the file name) work, here, Andy? (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx) (Admittedly, a kludge, but this is Windows, after all. ;-)) Lee Actually, in Windows 7, Microsoft has implemented true symbolic links (as far as I know). Maybe it is also in Vista? Anyway, is that (microsoft's true symlinks) feature used in cygwin 1.7? Apparently not, since it would solve my problem. Tuli -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
Lee Rothstein: Will Windows junctions (for the path; plus the file name) work, here? Don't think so, afaik junction points (introduced in Win2000, and different from Vista/7 symlinks) work correctly for directories only. Hard links, however, should work just fine for the problem at hand. tuli tanssi: Actually, in Windows 7, Microsoft has implemented true symbolic links (as far as I know). Maybe it is also in Vista? Anyway, is that (microsoft's true symlinks) feature used in cygwin 1.7? Apparently not, since it would solve my problem. Quoting Corinna Vinschen at http://sourceware.org/ml/cygwin/2009-11/msg00202.html: Cygwin 1.7 does recognize reparse points and especially the new NTFS6 symlinks. However, it only reads them, never writes them, for the reasons repeated by cgf and me a couple of times. You just can't use them to store POSIX paths *and* allowing interoperability with native Win32 processes, plus the nonsense of coupling them with a user right, plus the super-nonsense only to allow Admins to create them by default. All that together makes them worse than Windows shortcuts and they have not the faintest advantage over Cygwin-only symlinks implemented as files with the SYSTEM DOS attribute set. You could create a Windows symbolic link using the Windows 'mklink' tool though, and it should work both in cmd.exe and in Cygwin. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
This is a known limitation of the symbolic links in Cygwin 1.7. The solution is ... Thanks for the info. I'll try one of your workarounds. Cheers, Tuli -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
2009/12/30 Larry Hall (Cygwin): I've been using gcc and other tools in older versions of cygwin with 32-bit Windows XP and Vista from windows command prompt (cmd.exe) without problems. But now I'm using 64-bit Windows 7, and some command line tools like gcc.exe do not work anymore (from cmd.exe). They do work ok from Cygwin's bash. [...] Another [solution] might be to set winsymlinks in the CYGWIN environment variable http://cygwin.com/cygwin-ug-net/using-cygwinenv.html and recreate the symlinks you want that way. That won't work. The option causes symlinks to be represented by Windows shortcuts, which do work in Explorer, but not in cmd.exe where they appear as .lnk files instead. (Lame, eh?) Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
Hi, I've been using gcc and other tools in older versions of cygwin with 32-bit Windows XP and Vista from windows command prompt (cmd.exe) without problems. But now I'm using 64-bit Windows 7, and some command line tools like gcc.exe do not work anymore (from cmd.exe). They do work ok from Cygwin's bash. The message I get when trying to run gcc in cmd.exe is: Access is denied. Anyway, only some tools don't work, e.g. 'ls' works ok from cmd.exe. I noticed that all cygwin tools that are actually symbolic links to somehere else (just like /bin/gcc.exe and some others) are the problematic tools. Also /bin/gcc.exe has System rights (as seen by Attrib command of windows), while tools that do work have only Archive rights. So the I guess the problem is related to how symbolic links are created and with what rights. Anyone else tried this? Any solutions? Cheers, Tuli -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt
On 12/30/2009 08:30 AM, tuli tanssi wrote:
Hi,
I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anymore (from cmd.exe). They do
work ok from Cygwin's bash.
The message I get when trying to run gcc in cmd.exe is: Access is denied.
Anyway, only some tools don't work, e.g. 'ls' works ok from cmd.exe.
I noticed that all cygwin tools that are actually symbolic links to
somehere else (just like /bin/gcc.exe and some others) are the
problematic tools.
Also /bin/gcc.exe has System rights (as seen by Attrib command of
windows), while tools that do work have only Archive rights.
So the I guess the problem is related to how symbolic links are
created and with what rights.
Anyone else tried this? Any solutions?
This is a known limitation of the symbolic links in Cygwin 1.7. The solution
is to invoke the command directly ('gcc-3.exe' or 'gcc-4.exe' in this case) or
create your own batch file wrappers or DOS aliases to point to the proper
alternative. Another might be to set winsymlinks in the CYGWIN environment
variable http://cygwin.com/cygwin-ug-net/using-cygwinenv.html and recreate
the symlinks you want that way. The clear downside to this approach is that
it won't handle international characters in file names/paths properly. As a
result
one might guess this is not the recommended solution. And one would be
right! ;-)
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_
A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
