www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2025/01/03/15:41:46

DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 503Kfk5r1278603
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 503Kfk5r1278603
Authentication-Results: delorie.com;
dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=JCo3aIqz
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1362F3858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
s=default; t=1735936904;
bh=XiTt9CXccOxh2nj5n7NdaJiJuk2S5MRRZXkrSP9Jw1Y=;
h=References:In-Reply-To:Date:Subject:To:Cc:List-Id:
List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
From:Reply-To:From;
b=JCo3aIqzWhQ2+MgP58H+T9fwlt8szjVLWNmM1RDyW+Yjbq7VJShmZD+2dXD7Smunl
VeOi3Mmyyu24+fnYUL1rYxYND5T57of27cDEQ2EbaUeQ3yr64kaLyt8oqe4Eybzb+J
YvYegWnAfn4wCe1Y5ve8jaNE+h/UtYqPYnMvvWMU=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C04323858D20
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C04323858D20
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1735936845; cv=none;
b=k7Q+M5asvuGvVIucuQh4ZuvYj0yoj2xeriM7qgGpKoYX8ds/jTzcdHR3yGFDl0tCrEJNZ4FebTnAvmic+9dkpu6Il5spqtilEpOjHxRqFukmhS8EVRP2f15B+arHzg0Wz7ovqz3nLvdr92Lr9DH+sN+3VuAFsixpzqI7PtDyWEA=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
t=1735936845; c=relaxed/simple;
bh=kIKvC8M6WlLzIQesRw/JN0b8X7UQ3r6ZrsvaLxfP0tw=;
h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To;
b=HLMRcaVvmlwJiZ0QiXSaQrpEjTpD8pPxRsM9zYzEf9eolEOAuzxDiXBzLqAlzjkTvD2x2xS182GiH269Syw0xH4whjKyK60RJcjF8wCbYjsCveCL5lg6lDQsPKm4CV0dclRSbm1A8b5Qbe7HUMaCHMNBPUIgoWrM7eJLOSGH8Go=
ARC-Authentication-Results: i=1; server2.sourceware.org
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C04323858D20
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1735936844; x=1736541644;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
:reply-to;
bh=a36syOJvcfrZKV007KKHSiQNz/YCQ3Izjd5SubmwAEI=;
b=I5/UZvFz1BUUdlXKBvcjW2U/bFQhw+oftpYjiECk6UNXNGaG21cUvkyUQxVdN7wXFW
uLokYCL30+w8qQu/BS385I/fS297VJj0R7hsn4w0KCLPvL8Wv9TvaRCOIhz4gIvLfijw
E1QyxtxOBiNKyEiWnsSjqkFoimectCEFeqsqaZLo3zb7YJ2rzmVaxjq1S0WrP25b/AjR
XWRi0thDLcsNlYZn+tRRMxhP8KFXPQmWSSRKUNbO1IZSaSCDo/7fN9FWuMa6q69zZ2Ro
bWaSdS/mujAgQpdEogHA1SZ8BL/4HBqefWM9a/+ioYZj9//nJYAzo8GkugshEsPLJjHR
p45g==
X-Gm-Message-State: AOJu0Yz41rRR/caEDGl1hyoOrPHtObPbKux0qLVsfaAxSYPB5rMSLK6n
zNlTHhQHDYhqUE3gs9nE7bX97RST0SLMKA6RslblvcK1W8unU3yPtY5NuASl8WtYbY8T7gQwH+i
SOeFCWk7fG5KqU+GcFaGhx913TgQ=
X-Gm-Gg: ASbGnctTzzJvYs8qqliiXKI1kt303QwXiUZd4VyTBJsRCUu7OW/Mpo9LU7Eau2/7Vgq
srlyQxQgdoEUbeg7y6KUv0DxYaZnswasPr/QFvM0=
X-Google-Smtp-Source: AGHT+IHwZ1nYN41e8KJuLEpv1jbwWtGePJNQiqEc16feeSJPwe1sICJOYLbDhZBprxq2Wh3s658pVhlUCyA1baqKbG8=
X-Received: by 2002:a17:90b:1f83:b0:2ee:fd53:2b17 with SMTP id
98e67ed59e1d1-2f452eb3ce1mr78920430a91.29.1735936843653; Fri, 03 Jan 2025
12:40:43 -0800 (PST)
MIME-Version: 1.0
References: <f67d6da0-cab3-4cf0-82cb-f72f09255d31 AT GlueLogix DOT com>
In-Reply-To: <f67d6da0-cab3-4cf0-82cb-f72f09255d31@GlueLogix.com>
Date: Fri, 3 Jan 2025 12:40:32 -0800
Message-ID: <CAJtSMgvDudMF4_OUYzP36KCf-w1Mtqk9dHvymTc9CVY=zj9JEQ@mail.gmail.com>
Subject: Re: How to make Cygwin handle Unicode symbolic links?
To: Larry Martin <Larry AT gluelogix DOT com>
Cc: cygwin AT cygwin DOT com
X-Content-Filtered-By: Mailman/MimeDel 2.1.30
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: David Dyck via Cygwin <cygwin AT cygwin DOT com>
Reply-To: David Dyck <david DOT dyck AT gmail DOT com>
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 503Kfk5r1278603

I assume you meant  cygcheck
<https://cygwin.com/cygwin-ug-net/cygcheck.html>, not  symcheck ?
 ( i've been "into" symbolic links in cygwin today so the title caught my
eye )

what do you have for the CYGWIN environment variable,  I've been using
winsymlinks:native
eg
  export CYGWIN=winsymlinks:native

On Fri, Jan 3, 2025 at 11:58 AM Larry Martin via Cygwin <cygwin AT cygwin DOT com>
wrote:

> I have two Cygwin systems, seemingly identical.  But one can compile
> openssl and one can't.  The problem occurs in the symbolic links that
> come with the source.  They all seem to be Unicode, or at least
> recognizeable ASCII characters with 0x00's in between.  Cygwin on my
> regular development system processes those symlinks just fine.  But on a
> second PC, Cygwin just sees the symlink as a file.  Per the
> instructions, the output of `symcheck -s -v -r` for both systems is
> attached.  Neither system has any environment variables starting with
> "LC_" or "LANG".
>
> In order to describe the problem, I have to use examples from openssl.
> Please remember that this is a Cygwin question, not gcc or openssl.  I'm
> also aware that my openssl version is quite old. There are reasons for
> that.  It doesn't affect this question.
>
> On the "bad" system, the first error is "stray '\377' in program" when
> gcc parses openssl/include/openssl/des.h.  That is a symlink to
> ../../crypto/des/des.h.  In my compile folder on the bad system, this
> happens:
> > $ head openssl-1.0.2p/include/openssl/des.h
> > !<symlink>??../../crypto/des/des.h
> Note that Cygwin did _not_ follow the symlink, but printed it out like
> any other file.
>
> On the "good" system, the same command goes more like this:
> > $  head openssl-1.0.2p/include/openssl/des.h
> > /* crypto/des/des.h */
> > /* Copyright (C) 1995-1997 Eric Young (eay AT cryptsoft DOT com)
> >  * All rights reserved.
> where Cygwin _has_ followed the symlink.
>
> In emacs, the symlink in question looks like Unicode:
> > !<symlink>
> > .\0.\0/\0.\0.\0/\0c\0r\0y\0p\0t\0o\0/\0d\0e\0s\0/\0d\0e\0s\0.\0h\0\0\0
> It is the same on both systems.
>
> When I make a new symlink on either system, it is unreadable, so I can't
> dump it with any hex editor including od.  However, the file length
> seems to be about half that of the openssl source tree links, so it's
> probably UTF-8.
>
> The question is: what might be different between these two Cygwin/Win11
> systems, where one follows a Unicode symlink and the other doesn't?
>
> Thank you.
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019