> I noticed that some programs that depend on zlib stopped working and started
> creating stackdumps with Windows Dev Channel build 20246.1. I could not get
> gdb working with zlib but I figured a workaround: I recompiled zlib with
> cygport using the latest gcc (10.2.0) and copied the dll over
On 2020-10-31 14:19, Teemu via Cygwin wrote:
> I noticed that some programs that depend on zlib stopped working and started
> creating stackdumps with Windows Dev Channel build 20246.1. I could not get
> gdb working with zlib but I figured a workaround: I recompiled zlib with
> cygport using the
Hello!
I noticed that some programs that depend on zlib stopped working and started
creating stackdumps with Windows Dev Channel build 20246.1. I could not get gdb
working with zlib but I figured a workaround: I recompiled zlib with cygport
using the latest gcc (10.2.0) and copied the dll over t
On 2020-10-31 08:21, Adam Dinwoodie wrote:
> On Sat, 31 Oct 2020 at 13:16, Matt D. via Cygwin wrote:
>> I can't always know what binaries exist in C:\Windows\System32 when
>> writing my scripts. Am I supposed to always launch scripts as "bash
>> --login -i -c"? I don't want or need to have bash run
GNU tar has been updated to the latest upstream release 1.32.
This is a new upstream release. Upstream release notes can be found
alongside other documentation in /usr/share/doc/tar/.
ZStandard compression support is enabled in this release.
This also fixes an accidental regression, where the
This is a re-release of the latest upstream release of the LZO library,
compiled with gcc-10. In addition the MingW64 packages for the
cross-compilation toolchains have been updated to the same release.
liblzo2-2.10-2
mingw64-i686-lzo2-2.10-2
mingw64-x86_64-lzo2-2.10-2
Home Page
=
htt
As previously announced, version 3.4.3-2 of
libarchive (source)
libarchive-devel
libarchive13
bsdcat
bsdcpio
bsdtar
is available in the Cygwin distribution. The MinGW64 packages for
the cross-compilation toolchains have now been updated as well:
On 12/10/2020 09:04, Clientvps Offshore Hosting via Cygwin wrote:
Hi
We are a hosting service company that wants to provide services to open
source software systems. In this regard, we have prepared a mirror for
Cygwin support, which we want to put in your list after your review.
Please check our
On Sat, 31 Oct 2020 at 13:16, Matt D. via Cygwin wrote:
> I can't always know what binaries exist in C:\Windows\System32 when
> writing my scripts. Am I supposed to always launch scripts as "bash
> --login -i -c"? I don't want or need to have bash run all of its login
> scripts unnecessarily.
>
> H
I have Cygwin's /bin directory configured to be available on my login
environment PATH by default. This behavior is inherited when I run a
bash login shell:
$ where sort
C:\cygwin\bin\sort.exe
C:\Windows\System32\sort.exe
But if I run the following script from a Windows command prompt:
C:\> bash
Please ignore this. There was an error in my test case.
--
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
Simple Bash script:
> #!/bin/bash
>
> cut
Save as "testme.sh" in C:\ or elsewhere.
Open a Windows command prompt and type:
> cmd /c bash -c /c/testme.sh
I get the following error:
> -gThe system cannot find the file specified.
This only seems to trigger when bash is running as a child proces
I don't have any of /user /users /User /Users folders on my setup.
Do you mean C:\Users ?
Even if I symlink it, won't that just change the location, but not the
used usernames?
As for /etc/passwd , I don't have that file.
/etc/nsswitch.conf is empty (only comments).
It is basically a fresh cyg
On Sat, Oct 31, 2020 at 02:09:28PM +0900, cygwin wrote:
> On Sat, 31 Oct 2020 14:56:14 +1100, Duncan Roe
> > On Sat, Oct 31, 2020 at 02:30:07PM +1100, Duncan Roe wrote:
> > > Hi,
> > >
> > > Updated cygwin64 this morning and now gdb won't start.
> > >
> > > cygcheck shows 2 missing libraries:
> > >
14 matches
Mail list logo
