[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94f2fc1405c37bac5bb677285d3d9626@smtp.hushmail.com>
Date: Fri, 22 Mar 2013 21:15:12 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: makefile, build (cygwin)
On 22 Mar, 2013, at 18:45 , "jfoug" <jfoug@....net> wrote:
> One note, changes like this would only build useable exe files, that run using the cygwin shell. The symlinks would not work properly under a plain Win32 cmd. However, the unix symlink model is far from correct on win32 as it is. There are some environmental, and stdin/stdout strangeness from using the symlink.c method. I personally copy john.exe to whatever name I need (such as copy john.exe unique.exe). If done that way, all of the strange behaviors go away.
Does "ln -s" not produce absolutely normal symlinks? IIRC Windows and NTFS has handled symlinks and hard links ever since the first NT version 20 years ago. I thought the only thing missing in the Windows world was userland tools.
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
