x86/ -> ./ symlink
Sun Jun 30 22:31:00 GMT 2013
On Sun, Jun 30, 2013 at 11:38:46AM +0200, Corinna Vinschen wrote:
>On Jun 29 13:59, Christopher Faylor wrote:
>> On Sat, Jun 29, 2013 at 12:46:00PM -0400, Christopher Faylor wrote:
>> >On Sat, Jun 29, 2013 at 10:01:52AM +0200, Corinna Vinschen wrote:
>> >>On Jun 24 19:52, Achim Gratz wrote:
>> >>> May I suggest that this sort of link (and the similar one in
>> >>> cygwinports) has potential to break mirror scripts in bad ways? Not
>> >>> quite as bad, but linking x86_64 -> 64bit also results in duplicates
>> >>> that aren't serving a good purpose.
>> >>The x86 symlink break the "Install from directory" function of
>> >>setup.exe. It runs into some endless loop. If I remove the symlinks it
>> >>works as usual. I don't know why it does that at all. It has no
>> >>business reading these symlinks. If nobody beats me to it, I'll
>> >>investigate next week.
>> >Are you saying that this is happening with a CVS version of setup.exe?
>No, this occurs with the current 2.774 version from the home page.
>> >If not, it seems impossible that this symlink would cause an issue on a
>> >local install.
>> >Or, maybe you're copying the whole release area to your work area as
>> >you proposed in the cygwin list.
>We're using a local mirror and "Install from directory" from the local
>mirror for many, many years and it always worked fine.
I'm still investigating this behavior.
>The 64 bit 2.802 executable SEGVs immediately at startup.
That one should be fixed. I'm not sure why it didn't SEGV on 32-bit
too. Different stack layout I guess.
More information about the Cygwin-apps