X-Spam-Check-By: sourceware.org Date: Thu, 17 Aug 2006 11:35:51 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Cc: Eli Zaretskii Subject: Re: change in behavior of make from 3.80 to 3.81 Message-ID: <20060817093551.GD20467@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com, Eli Zaretskii References: <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060815151104 DOT 0b40e260 AT pop DOT nycap DOT rr DOT com> <01b901c6c116$21259430$a501a8c0 AT CAM DOT ARTIMI DOT COM> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816091525 DOT 0ab90af0 AT pop DOT nycap DOT rr DOT com> <20060816144110 DOT GX20467 AT calimero DOT vinschen DOT de> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816111421 DOT 0b446b60 AT pop DOT nycap DOT rr DOT com> <20060816155054 DOT GY20467 AT calimero DOT vinschen DOT de> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816144036 DOT 09695af0 AT pop DOT nycap DOT rr DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Aug 17 05:05, Eli Zaretskii wrote: > > Date: Wed, 16 Aug 2006 15:52:59 -0400 (EDT) > > From: Igor Peshansky > > cc: cygwin AT cygwin DOT com > > > > Alternatively, you can try to implement a $(cygpath ...) function in make > > and submit *that* to the upstream maintainers. > > FWIW, I don't think such a function is a good idea, and if it is > proposed on the Make mailing list, I will probably object to it. > > The reason is that adding such a function goes against portability of > Makefiles across different ports of Make, and also adds a too-tight > coupling between Make and the Cygwin file-name handling (i.e., every > change in how /cygdrive/ is handled in Cygwin will require a > corresponding change in Make). While these disadvantages are not a > catastrophe, I don't see a need to punish Make by them when a better > and easier solution is available (i.e. use the existing HAVE_DOS_PATHS > code, perhaps with some Cygwin-specific changes). Contrary to what > some people said in this thread, I don't see any problems that could > hamper the Cygwin build of Make if it supported drive letters, since > Windows doesn't allow colons anywhere else in file names anyway. That's not quite right. Colons are also used in file names when the file name denotes an alternative named stream on NTFS file systems. Try this on NTFS: $ echo 'Normal data stream' > foo $ echo 'Alternative named data stream' > foo:bar $ ls -l foo* -rw-r--r-- 1 corinna root 19 Aug 17 11:33 foo < Note the file length! $ cat foo Normal data stream $ cat foo:bar Alternative named data stream For a more detailed description, see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/file_streams.asp Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/