X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Thu, 27 Aug 2009 21:52:26 -0700 Message-ID: Subject: Cygwin, symlinks, and wine From: Dan Kegel To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Although it seems strange to run cygwin on top of wine, doing so would make it possible to run a lot of build scripts for windows apps unchanged, which would be very handy in verifying that wine works properly (see http://wiki.winehq.org/UnitTestSuites ). The problem is, wine doesn't support the system attribute on files well. There's no convenient place to store that bit. That means that installing cygwin on wine fails subtly; /bin/cc doesn't get installed at all when you install gcc, for example. This problem is described in more detail at http://bugs.winehq.org/show_bug.cgi?id=15679 Since cygwin special cases some file system that doesn't support the system attribute, maybe it could do something similar when running in Wine. Or alternately, Wine could notice the attempt to set the system bit on a file that looks like a cygwin symlink, and create instead a real unix symlink. (Probably not a good idea, offhand.) Has anybody thought about this issue? Thanks, Dan -- 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