[ANNOUNCEMENT] Updated: mingw64-{headers, runtime, winpthreads} 8.0.0-1
Now released for both 32bit and 64bit Cygwin: Notable changes: * New Hyper-V headers and libraries by Biswapriyo Nath * Many headers updated from Wine by Jacek Caban. * ARM math improvements by Martin Storsjö * floating point fixes by Liu Hao * many *printf compatibility fixes by Liu Hao and Martin Storsjö * massive Windows App Store API updates by Steve Lhomme * winstorecompat library updates by Martin Storsjö * __USE_MINGW_ANSI_STDIO now automatically enabled in C99 and C11 mode when not using UCRT by Pali Rohár * wdm and ddk updates by Zebediah Figura * UCRT for Windows Store Apps (-lucrtapp) by Martin Storsjö * Audioclient and ActivateAudioInterfaceAsync API updates by Liu Hao * DirectX SDKs are now always installed *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature -- 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
Updated: mingw64-{headers,runtime,winpthreads} 8.0.0-1
Now released for both 32bit and 64bit Cygwin: Notable changes: * New Hyper-V headers and libraries by Biswapriyo Nath * Many headers updated from Wine by Jacek Caban. * ARM math improvements by Martin Storsjö * floating point fixes by Liu Hao * many *printf compatibility fixes by Liu Hao and Martin Storsjö * massive Windows App Store API updates by Steve Lhomme * winstorecompat library updates by Martin Storsjö * __USE_MINGW_ANSI_STDIO now automatically enabled in C99 and C11 mode when not using UCRT by Pali Rohár * wdm and ddk updates by Zebediah Figura * UCRT for Windows Store Apps (-lucrtapp) by Martin Storsjö * Audioclient and ActivateAudioInterfaceAsync API updates by Liu Hao * DirectX SDKs are now always installed *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
[ANNOUNCEMENT] Updated: w32api-{headers, runtime}-8.0.0-1 (x86/x86_64)
Now released for both 32bit and 64bit Cygwin: w32api-headers-8.0.0-1 w32api-runtime-8.0.0-1 Based on mingw-w64-v8.0.0. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature -- 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
Updated: w32api-{headers,runtime}-8.0.0-1 (x86/x86_64)
Now released for both 32bit and 64bit Cygwin: w32api-headers-8.0.0-1 w32api-runtime-8.0.0-1 Based on mingw-w64-v8.0.0. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. signature.asc Description: OpenPGP digital signature
Re: Windows 2019 support?
On 2020-09-17 09:52, Bill Stewart wrote: > On Thu, Sep 17, 2020 at 7:58 AM Chris Bovitz wrote: > Cygwin can be expected to run on all modern, released versions of Windows. >> State [sic] January 2016 this includes Windows Vista, Windows Server 2008 >> and all later versions of Windows up to Windows 10 and Windows Server 2016. >> >> To me, this implies that Windows Server 2019 is supported, but is that >> true? If so, could the FAQ be updated to show that? Thanks. >> > > Windows Server 2019 is just the server version of Windows 10 1809. In my > testing it works without any issues. > > My recommendation is for the FAQ to state: > > "Cygwin can be expected to run on all modern, released versions of Windows. > Since January 2016 this includes Windows Vista, Windows Server 2008, and > all later versions." Wanted to enumerate Vista, 7, 8, 8.1, 10 progression to be clear, exclude S mode, add Cygwin32 on ARM, specify 64 bit only AMD/Intel, and remove any dates to avoid confusion in future, so patched to read: "1.2. What versions of Windows are supported? Cygwin can be expected to run on all modern, released versions of Windows, from Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all later versions of Windows, except Windows S mode due to its limitations. The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on released 64 bit versions of Windows including ARM PCs, the 64 bit version of course only on 64 bit AMD/Intel compatible PCs." but we are unsure how to get it regened and pushed onto the production web site. -- 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 IEC units and prefixes, physical quantities in SI.] -- 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
Re: Cygwin 3.1.5, 3.1.6 and 3.1.7 builds reporting tty errors with OpenSSH Services in indows Event Logs
On Fri, 18 Sep 2020 01:44:53 + Peter Board wrote: > Attached is the ssh_config and sshd_config. Both looks sane... Could you please check the output of: ls -l /dev/*ty* and icacls 'F:\cygwin64\dev' -- Takashi Yano -- 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
Re: [PATCH v2] winsup/doc/faq-what.xml: FAQ 1.2 Windows versions supported
On 9/18/2020 11:29 AM, Brian Inglis wrote: On 2020-09-18 05:59, Ken Brown via Cygwin-patches wrote: On 9/17/2020 10:53 PM, Brian Inglis wrote: enumerate Vista, 7, 8, 10 progression to be clear, and earliest server 2008; add 8.1, exclude S mode, add Cygwin32 on ARM, specify 64 bit only AMD/Intel --- winsup/doc/faq-what.xml | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index ea8496ccbc65..77ba1c5fdd9c 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -30,12 +30,12 @@ They can be used from one of the provided Unix shells like bash, tcsh or zsh. What versions of Windows are supported? -Cygwin can be expected to run on all modern, released versions of Windows. -State January 2016 this includes Windows Vista, Windows Server 2008 and all -later versions of Windows up to Windows 10 and Windows Server 2016. +Cygwin can be expected to run on all modern, released versions of Windows, +from Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all +later versions of Windows, except Windows S mode due to its limitations. The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on -released 64 bit versions of Windows, the 64 bit version of course only on -64 bit Windows. +released 64 bit versions of Windows including ARM PCs, +the 64 bit version of course only on 64 bit AMD/Intel compatible PCs. Keep in mind that Cygwin can only do as much as the underlying OS supports. Because of this, Cygwin will behave differently, and Pushed. Thanks. Ken Thanks Ken, Do you have to run something to regen the docs, FAQ.html, and push to the web site, or does it run periodically, so I can follow up to the OP and get feed back from the responder? No, sorry. I don't know how/when that's done. Ken
Re: [PATCH v2] winsup/doc/faq-what.xml: FAQ 1.2 Windows versions supported
On 2020-09-18 05:59, Ken Brown via Cygwin-patches wrote: > On 9/17/2020 10:53 PM, Brian Inglis wrote: >> enumerate Vista, 7, 8, 10 progression to be clear, and earliest server 2008; >> add 8.1, exclude S mode, add Cygwin32 on ARM, specify 64 bit only AMD/Intel >> --- >> winsup/doc/faq-what.xml | 10 +- >> 1 file changed, 5 insertions(+), 5 deletions(-) >> >> diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml >> index ea8496ccbc65..77ba1c5fdd9c 100644 >> --- a/winsup/doc/faq-what.xml >> +++ b/winsup/doc/faq-what.xml >> @@ -30,12 +30,12 @@ They can be used from one of the provided Unix shells >> like >> bash, tcsh or zsh. >> What versions of Windows are supported? >> >> -Cygwin can be expected to run on all modern, released versions of >> Windows. >> -State January 2016 this includes Windows Vista, Windows Server 2008 and all >> -later versions of Windows up to Windows 10 and Windows Server 2016. >> +Cygwin can be expected to run on all modern, released versions of >> Windows, >> +from Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all >> +later versions of Windows, except Windows S mode due to its limitations. >> The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on >> -released 64 bit versions of Windows, the 64 bit version of course only on >> -64 bit Windows. >> +released 64 bit versions of Windows including ARM PCs, >> +the 64 bit version of course only on 64 bit AMD/Intel compatible PCs. >> >> Keep in mind that Cygwin can only do as much as the underlying OS >> supports. Because of this, Cygwin will behave differently, and > > Pushed. Thanks. > > Ken Thanks Ken, Do you have to run something to regen the docs, FAQ.html, and push to the web site, or does it run periodically, so I can follow up to the OP and get feed back from the responder? -- 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 IEC units and prefixes, physical quantities in SI.]
[ANNOUNCEMENT] fish-3.1.2-2
fish 3.1.2-2 is now available in Cygwin. This release updates the default fish_prompt function to the version shipped in the upstream fish 3.1.2. The new default prompt function has lots more stuff in it, like a colored username, version control branch name, and numerical exit status code of the previous command, if it ended in an error status. Personally, I find all of that to be too much information for a shell prompt. But it's what the fish project ships now, so Cygwin is including it. If you want to change/simplify the prompt, you can: * Change fish's colors. For example, you can set the username color in the prompt from bright green (!) back to normal by set -U fish_user_color normal * Create your own fish_prompt function. You can start by copying it from /usr/share/fish/vendor_functions.d/fish_prompt.fish into either of: /etc/fish/functions (for all users on the host) ~/.config/fish/functions (for just your account) Then edit the function, for example to remove fish_vcs_prompt (which I find also slows down the prompt) or prompt_status. fish is the friendly interactive shell. It's a Unix shell that focuses on interactive use, discoverability, and user friendliness. The design goal of fish is to give the user a rich set of powerful features in a way that is easy to discover, remember, and use. Home page: http://fishshell.com Andrew E. Schulman *** To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com_at_cygwin.com If you need more information on unsubscribing, start reading here: http://cygwin.com/lists.html#subscribe-unsubscribe Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
fish-3.1.2-2
fish 3.1.2-2 is now available in Cygwin. This release updates the default fish_prompt function to the version shipped in the upstream fish 3.1.2. The new default prompt function has lots more stuff in it, like a colored username, version control branch name, and numerical exit status code of the previous command, if it ended in an error status. Personally, I find all of that to be too much information for a shell prompt. But it's what the fish project ships now, so Cygwin is including it. If you want to change/simplify the prompt, you can: * Change fish's colors. For example, you can set the username color in the prompt from bright green (!) back to normal by set -U fish_user_color normal * Create your own fish_prompt function. You can start by copying it from /usr/share/fish/vendor_functions.d/fish_prompt.fish into either of: /etc/fish/functions (for all users on the host) ~/.config/fish/functions (for just your account) Then edit the function, for example to remove fish_vcs_prompt (which I find also slows down the prompt) or prompt_status. fish is the friendly interactive shell. It's a Unix shell that focuses on interactive use, discoverability, and user friendliness. The design goal of fish is to give the user a rich set of powerful features in a way that is easy to discover, remember, and use. Home page: http://fishshell.com Andrew E. Schulman *** To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com_at_cygwin.com If you need more information on unsubscribing, start reading here: http://cygwin.com/lists.html#subscribe-unsubscribe Please read *all* of the information on unsubscribing that is available starting at this URL.
Re: TMP/TEMP environment variable and /tmp
On 2020-09-17 23:56, Kristian Ivarsson via Cygwin wrote:
>
> Does anyone know the rational with this behaviour and what can be
> done to get hold of the (real) Windows TMP/TEMP
> environment-variable-values (in a
> (hopefully) platform independent way) ?
so if you are making your custom tree, try to stick on that
expectation and have both directories.
>>> In general, you are free to set TMP to a directory of your choice,
>>> that's the purpose of that variable, no need to sync it with some root.
>>> There is a comment in /etc/profile:
>>># TMP and TEMP as defined in the Windows environment
>>># can have unexpected consequences for cygwin apps, but it does not
>>> explain what consequences that might be; probably some trouble with
>>> ACL/access permissions for temporary files.
>> Nowadays that would be $LOCALAPPDATA/Temp, or if you really insist, the
>> content of /proc/registry/HKEY_CURRENT_USER/Environment/TMP (or TEMP),
>> after similarly expanding environment variable references found in that.
>>
>> The fact that getting Windows' idea of the user's TEMP directory is not
>> immediately platform independent may well have been part of the rationale
>> for not even trying that.
>
> Well, at least it's up to the user
>
> If the user sets its TMP-variable to "C:\Jabba Dabba Dooo" or "/jabba
> dabba doo", I expect the value of getenv("TMP") should be just that and
> regardless of OS the value returned is whatever the variable is set to
> and not magically changed to "/tmp"
Of course and that's not happening, no worries. The issue was that TMP is
set in /etc/profile and not inherited from the Windows environment.
>>> Well, where my Cygwin-compiled-application is running, there’s no
>>> Cygwin-installation and thus no /etc/profile so it cannot be set there (if
>>> /etc/profile is not a built in resource in every executable), so there must
>>> be some text-value inside the compiled executables used in some manner
>>> somehow
>>
>> There must be something going on in your environment that you haven't told
>> us yet. I just tried the following test case:
>>
>> #include
>> #include
>> int
>> main ()
>> {
>> printf ("The value of TMP is %s\n", getenv ("TMP"));
>> }
>>
>> In a Cygwin bash shell I get
>>
>> The value of TMP is /tmp
>>
>> Running the same executable under a Windows Command Prompt, I get
>>
>> The value of TMP is /c/Users/kbrown/AppData/Local/Temp
>>
>> So Cygwin converts TMP to a Posix path [*], but it doesn't change it to
>> "/tmp".
>>
>> Ken
>>
>> [*] See environ.cc:303 for a list of environment variables that Cygwin
>> converts.
>
> Hmm, you’re right Ken
>
> I tried this before taking off for a vacation and the Windows-TMP-variable is
> extracted
>
> I now suspect that we maybe do have some logic that falls back to /tmp if the
> TMP-variable is NULL and perhaps the variable is NULL because we launch the
> process with CreateProcess and perhaps the environment-variables doesn’t get
> inherited then ?
>
> The reason why we use CreateProcess from within a cygwin-application to
> create another cygwin-application (instead of fork or such) might seem weird,
> but it has its reasons
>
> I need to confirm this after the vacation-trip or if someone already know if
> environment-variables “dissapear” if things such as CreateProcess are used ?
Programmer optional - same applies for CreateProcessA/W/AsUserA/W:
https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessa
"lpEnvironment
A pointer to the environment block for the new process. If this parameter is
NULL, the new process uses the environment of the calling process.
An environment block consists of a null-terminated block of null-terminated
strings. Each string is in the following form:
name=value\0
Because the equal sign is used as a separator, it must not be used in the name
of an environment variable.
An environment block can contain either Unicode or ANSI characters. If the
environment block pointed to by lpEnvironment contains Unicode characters, be
sure that dwCreationFlags includes CREATE_UNICODE_ENVIRONMENT. If this parameter
is NULL and the environment block of the parent process contains Unicode
characters, you must also ensure that dwCreationFlags includes
CREATE_UNICODE_ENVIRONMENT.
The ANSI version of this function, CreateProcessA fails if the total size of the
environment block for the process exceeds 32,767 characters.
Note that an ANSI environment block is terminated by two zero bytes: one for the
last string, one more to terminate the block. A Unicode environment block is
terminated by four zero bytes: two for the last string, two more to terminate
the block."
Note that when MS say "Unicode" they usually mean UTF16LE, which only some
programs support, depending on the I/O functions they use.
Re: [PATCH v2] winsup/doc/faq-what.xml: FAQ 1.2 Windows versions supported
On 9/17/2020 10:53 PM, Brian Inglis wrote: enumerate Vista, 7, 8, 10 progression to be clear, and earliest server 2008; add 8.1, exclude S mode, add Cygwin32 on ARM, specify 64 bit only AMD/Intel --- winsup/doc/faq-what.xml | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index ea8496ccbc65..77ba1c5fdd9c 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -30,12 +30,12 @@ They can be used from one of the provided Unix shells like bash, tcsh or zsh. What versions of Windows are supported? -Cygwin can be expected to run on all modern, released versions of Windows. -State January 2016 this includes Windows Vista, Windows Server 2008 and all -later versions of Windows up to Windows 10 and Windows Server 2016. +Cygwin can be expected to run on all modern, released versions of Windows, +from Windows Vista, 7, 8, 8.1, 10, Windows Server 2008 and all +later versions of Windows, except Windows S mode due to its limitations. The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on -released 64 bit versions of Windows, the 64 bit version of course only on -64 bit Windows. +released 64 bit versions of Windows including ARM PCs, +the 64 bit version of course only on 64 bit AMD/Intel compatible PCs. Keep in mind that Cygwin can only do as much as the underlying OS supports. Because of this, Cygwin will behave differently, and Pushed. Thanks. Ken
