IEEE 128 Support Re: Cygwin Digest, Vol 22, Issue 26

IEEE 128 Support Re: Cygwin Digest, Vol 22, Issue 26

[James McKelvey]

 I have an up-to-date Cygwin and the latest snapshot of gcc-11 on Windows 10. How do I have to configure to make C++use IEEE-128 for long double? No big deal, I'm just curious. I could build gcc-12 (or other) if that helps.


    On Tuesday, December 14, 2021, 04:00:28 AM PST, cygwin-request@cygwin.com <cygwin-request@cygwin.com> wrote:  
 
 Send Cygwin mailing list submissions to
    cygwin@cygwin.com

To subscribe or unsubscribe via the World Wide Web, visit
    https://cygwin.com/mailman/listinfo/cygwin
or, via email, send a message with subject or body 'help' to
    cygwin-request@cygwin.com

You can reach the person managing the list at
    cygwin-owner@cygwin.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Cygwin digest..."
Today's Topics:

  1. Re: setup-x86_64.exe does not start in win10 20H2 (Brian Inglis)
  2. RE: Starting CMD from a bash shell with current directory on
      a mounted/network drive results in an incorrect current directory
      (john daintree)
On 2021-12-13 23:31, Marco Atzeri wrote:
> On 14.12.2021 07:17, Brian Inglis wrote:
>> On 2021-12-13 16:26, Kutty, Rejeesh wrote:
>>> I uninstalled Beyond Trust with our IT help, rebooted, same behavior.
>>> I then came upon another thread that talks about the compression.
>>> I didn't build it, I just decompressed it and now setup-64bit works 
>>> fine.
>>> For some reason, 32bit doesn't have any of this problem.
>>> If it is not too much of trouble, I would request that you provide an 
>>> uncompressed version too.
>>> The file size is not that bad, It came to be about 5MB only.
>>> Perhaps, suggest in the installation instructions to try in case it 
>>> doesn't launch?

If you have that problem, you have an app in the BLODA.
Are you still running BeyondTrust or another AV?
You need to get Cygwin setup exes using upx bypassed or whitelisted by 
your support or the vendor.

>> What was the URL of the thread about compression?
>> Which file did you download about 5MB, from which URL, how did you 
>> download and decompress it: using which tools, commands, options, and 
>> what were the before and after sizes?
>> There appear to be no Cygwin setup files about 5MB:

> he means 5MB after decompressing the 1.3Mb setup-x86_64.exe
> If I remember right upx is used for setup compression

Why would anyone want or need to do that manually: that implies a badly 
written app in the BLODA interfering with decompression, and that hasn't 
had any mentions as a problem for a couple of years!

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]


Cool, thanks.

-----Original Message-----
From: Cygwin <cygwin-bounces+johnd=dyalog.com@cygwin.com> On Behalf Of
Corinna Vinschen
Sent: 13 December 2021 15:06
To: cygwin@cygwin.com
Subject: Re: Starting CMD from a bash shell with current directory on a
mounted/network drive results in an incorrect current directory

On Dec 13 20:06, Takashi Yano wrote:
> On Mon, 13 Dec 2021 10:53:41 -0000
> "john daintree" wrote:
> > I've just upgraded a machine from Windows 10 to Windows 11. Part of 
> > my work process is now broken because when starting cmd from Cygwin 
> > with the current directory on a mounted drive I get the following
error/warning/issue:
> > 
> >  
> > 
> >  
> > 
> > /cygdrive/j$ cmd
> > 
> > '\\nas00.<redacted>\devt\users\johnd'
> > 
> > CMD.EXE was started with the above path as the current directory.
> > 
> > UNC paths are not supported.  Defaulting to Windows directory.
> > 
> > Microsoft Windows [Version 10.0.22000.348]
> > 
> > (c) Microsoft Corporation. All rights reserved.
> > 
> >  
> > 
> > C:\Windows>
> > 
> >  
> > 
> >  
> > 
> > The drive J: is mounted as something on our network (I've redacted a 
> > bit of the path, for probably no good reason)
> > 
> >  
> > 
> > Is there a workaround? Or is this something that can be fixed in Cygwin?
> 
> Thanks for the report. This was already fixed recently in git head.
> 
> https://cygwin.com/pipermail/cygwin/2021-December/250153.html
> https://cygwin.com/pipermail/cygwin-patches/2021q4/011583.html
> 
> Please wait for the next cygwin release or new developers snapshot.

New developer snapshot is available on https://cygwin.com/snapshots/


Corinna

-- 
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