uctor Corp.
Bus 001 Device 003: ID 04b4:0004 Cypress Semiconductor Corp.
...
Device appears twice as is contains two different end points. Now, I
try to run my code.
$ ./sonde 1
...
CY:Error in opening the device... Libusb error is -12
CyGetDeviceInfo failure (3)
I have tried to ex
ng hogs: 1 lockmix
> stress-ng: info: [175] lockmix: exercising file lock types: flock locka lockf
> 0 [main] stress-ng 175 C:\cygwin64\bin\stress-ng.exe: *** fatal
> error - NtCreateEvent(lock): 0xC035
> stress-ng: warn: [174] metrics-check:
&
] dispatching hogs: 1 lockmix
> stress-ng: info: [175] lockmix: exercising file lock types: flock locka lockf
> 0 [main] stress-ng 175 C:\cygwin64\bin\stress-ng.exe: *** fatal
> error - NtCreateEvent(lock): 0xC035
> stress-ng: warn: [174] metrics-
locka lockf
0 [main] stress-ng 175 C:\cygwin64\bin\stress-ng.exe: *** fatal
error - NtCreateEvent(lock): 0xC035
stress-ng: warn: [174] metrics-check:
all bogo-op counters are zero, data may be incorrect
stress-ng: info: [174] skipped: 0
stress-ng: info: [174
4-09-13 14:02, S. Cowles via Cygwin wrote:
>>>>
>>>> i have a clean install of cygwin on a win11pro box. when i install cyg-x
>>>> (via https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing), i
>>>> get the following error:
>>&g
-installing), i
get the following error:
Package: _/xinit
xinit.sh exit code 3
Where are you seeing this error?
final error reporting window of setup-x86_64.ext instance
the result of the error is no access to any cyg-x apps via start menu, etc.
what is the proper way to fix this error
On Fri, 13 Sep 2024, Brian Inglis via Cygwin wrote:
On 2024-09-13 14:02, S. Cowles via Cygwin wrote:
i have a clean install of cygwin on a win11pro box. when i install cyg-x
(via https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing), i
get the following error:
Package
On 2024-09-13 14:02, S. Cowles via Cygwin wrote:
i have a clean install of cygwin on a win11pro box. when i install cyg-x (via
https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing), i get the
following error:
Package: _/xinit
xinit.sh exit code 3
Where are you seeing
i have a clean install of cygwin on a win11pro box. when i install cyg-x (via
https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing), i get the
following error:
Package: _/xinit
xinit.sh exit code 3
the result of the error is no access to any cyg-x apps via start menu
Richard via Cygwin writes:
> As anticipated, after further investigation, it is NOT a
> Cygwin-related issue, hence I withdraw my request with apologies for
> noise.
You didn't say what you are trying to achieve, but since the exercise
seems to be to learn something about Linux kernel (module) pro
', as
it clearly states in its error message... Once adjusted, there is no issue
left. ;)
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#u
Sirs:
Please note initially that the error indicated occurs systematically in the
actual project, but it was reproduced here using a simpler demonstration case
for documentation.
I might have to defer to www.kernel.org || gcc.gnu.org depending upon your
comments, as I feel that it is not
christianon39--- via Cygwin writes:
> /usr/include/sys/signalfd.h:17:17: error: 'O_CLOEXEC' undeclared here (not in
> a function); did you mean 'FD_CLOEXEC'?
>17 | SFD_CLOEXEC = O_CLOEXEC,
> | ^
> |
oduces the same error when
compiled? Because that doesn't happen for me...
--
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
17:07
Til: cygwin@cygwin.com
Emne: Issue regarding SFD_CLOEXEC. error: "''O_CLOEXEC' undeclared here (not in
a function); did you mean 'FD_CLOEXEC'?"
Hi, I am trying to build wlroots, but get this error in meson logs:
Command line: `cc
/home/Chris/wlroots/build/m
Hi, I am trying to build wlroots, but get this error in meson logs:
Command line: `cc
/home/Chris/wlroots/build/meson-private/tmprxphcsub/testfile.c -o
/home/Chris/wlroots/build/meson-private/tmprxphcsub/output.obj -c
-D_FILE_OFFSET_BITS=64 -O0 -std=c11` -> 1
stderr:
In file included f
I don't use those two Cygwin-X shortcuts that failed to be created by
mkshortcut when /etc/postinstall/xinit.sh tried to do that. I commented
out those two lines near the end of xinit.sh. I hope that has no unwanted
side effect(s).
--
Problem reports: https://cygwin.com/problems.html
FAQ:
On 2024-03-24 12:59, Matthias--- via Cygwin wrote:
I downloaded ntfs-3g_ntfsprogs-2022.10.3.tgz from tuxera, extract it and run,
in my cygwin 3.5
environment:
./configure
make ntfsprogs
I got a "fatal error: linux/fd.h: No such file or directory".
All ntfsprogs are build in ~
Hello,
I downloaded ntfs-3g_ntfsprogs-2022.10.3.tgz from tuxera, extract it and run,
in my cygwin 3.5
environment:
./configure
make ntfsprogs
I got a "fatal error: linux/fd.h: No such file or directory".
All ntfsprogs are build in ~/ntfsprogs but not ntfsrecover, ntfsse
On 2024-03-22 09:49, J M wrote:
This is a very painfull and weird failed error of Windows antivirus. I apologize
for not having realized before.
For other people who may encounter this difficult problem, the key to find this
error is (cut connections only for sites that use Letsencrypt
Hi,
This is a very painfull and weird failed error of Windows antivirus. I
apologize for not having realized before.
For other people who may encounter this difficult problem, the key to find
this error is (cut connections only for sites that use Letsencrypt
certificates), is the strace /usr
;s openssl test:
$ openssl s_client -connect cygwin.com:443
and ldd (or cygcheck):
$ ldd /usr/bin/curl
ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffadca5)
KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL
(0x7ffadb6d)
KERNELBASE.dll =&g
On 2024-03-19 11:00, J M wrote:
$ file /etc/pki/tls/certs/*
/etc/pki/tls/certs/ca-bundle.crt: symbolic link to
/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
/etc/pki/tls/certs/ca-bundle.trust.crt: symbolic link to
/etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
$ grep -c '^-
On 2024-03-19 08:02, ASSI via Cygwin wrote:
J M via Cygwin writes:
$ curl - -O https://cygwin.com/setup-x86_64.exe
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft
Speed
0 00
J M via Cygwin writes:
> $ curl - -O https://cygwin.com/setup-x86_64.exe
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft
> Speed
> 0 00 00 0 0 0 --:--:--
ebmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
El lun, 18 mar 2024 a las 23:19, Brian Inglis via Cygwin ()
escribió:
> On 2024-03-18 15:21, J M via Cygwin wrote:
> > With a fresh install of Cygwin then I launch (with package curl
> installed):
> >
> > curl -O htt
On 2024-03-18 15:21, J M via Cygwin wrote:
With a fresh install of Cygwin then I launch (with package curl installed):
curl -O https://www.cygwin.com/setup-x86_64.exe
Shows a curl 60 error ssl problem.
Using -k or --insecure works, but is not recomended.
Howto fix it?
WJFFM!
That error
Hi,
With a fresh install of Cygwin then I launch (with package curl installed):
curl -O https://www.cygwin.com/setup-x86_64.exe
Shows a curl 60 error ssl problem.
Using -k or --insecure works, but is not recomended.
Howto fix it?
Regards,
Cesar Jorge
--
Problem reports: https
; >> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
> >> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
> >> GNU make 4.4.1-2, when it starts external processes and those external
> >> processes exit wi
>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>> GNU make 4.4.1-2, when it starts external processes and those external
>> processes exit with a zero exit code.
>>
>> For example, a very simple Makefile:
>>
>>
On Feb 26 17:34, Dimitry Andric via Cygwin wrote:
> Hi,
>
> After a recent upgrade of a Cygwin installation, including cygwin1.dll
> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin'
i,
>>>> After a recent upgrade of a Cygwin installation, including cygwin1.dll
>>>> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
>>>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>>>> GNU mak
-February/255308.html) to
3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
GNU make 4.4.1-2, when it starts external processes and those external
processes exit with a zero exit code.
For example, a very simple Makefile:
all:
cmd /c echo done
Running this a few ti
to
>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>> GNU make 4.4.1-2, when it starts external processes and those external
>> processes exit with a zero exit code.
>> For example, a very simple Makefile:
>> all:
>>
On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote:
Hi,
After a recent upgrade of a Cygwin installation, including cygwin1.dll
(see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
GNU mak
Hi,
After a recent upgrade of a Cygwin installation, including cygwin1.dll
(see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
GNU make 4.4.1-2, when it starts external processes and
On Thu, 22 Feb 2024, Takashi Yano wrote:
> On Thu, 22 Feb 2024 11:46:39 +0530 (IST) Satish Balay wrote:
> > With cygwin upgrade to 3.5.0-1 - I'm not seeing "error return codes" on
> > compile failures.
> Thanks for the report.
> This bug has already has bee
run 'cl /c test.c'
>
> With cygwin upgrade to 3.5.0-1 - I'm not seeing "error return codes" on
> compile failures.
>
> However - this works again after downgrading to 3.4.10-1.
>
> Note: This works with 3.5.0-1 - if I use 'mintty'
Usage: Invoke 'cl' from cygwin/bash. i.e:
- run 'Visual Studio CMD' to setup MS compilers in dos shell
- run 'c:\cygwin64\cygwin.bat' [or 'c:\cygwin64\bin\bash --login']
- run 'cl /c test.c'
With cygwin upgrade to 3.5.0-1 - I'm not see
On Sun, Feb 18, 2024 at 3:40 PM Cary Lewis via Cygwin wrote:
>
> Attempting to run:
>
> openssl enc -base64 -i file
>
> gives the following error:
>
> 42949672976:error:25066067:DSO support routines:dlfcn_load:could not load
> the shared library:crypto/d
Attempting to run:
openssl enc -base64 -i file
gives the following error:
42949672976:error:25066067:DSO support routines:dlfcn_load:could not load
the shared library:crypto/dso/dso_dlfcn.c:118:filename(libproviders.dll):
No such file or directory
42949672976:error:25070067:DSO support
On Sat, 3 Feb 2024 at 19:25, Corinna Vinschen wrote:
> > Sorry to say that, but SetThreadErrorMode/CreateProcess don't do what we
> > want them to do. I just tested this myself with a modified Cygwin DLL
> > (code below) and it turns out that the child process error mode
inna Vinschen via Cygwin wrote:
> > > > > Is it actually a safe bet that the error mode set by
> > > > > SetThreadErrorMode
> > > > > is then propagated as process error mode to the child process?
> > > > >
> > > > > I ha
uot;right" is the reason the flag/option was
re-added in MSYS2. I think the most "right" thing Cygwin could do (if it
were to only do one thing, rather than having an option) would be to
somehow have native processes inherit the error mode as though Cygwin were
not in the mix. The issu
On Feb 2 19:51, Corinna Vinschen via Cygwin wrote:
> On Feb 2 18:22, Corinna Vinschen via Cygwin wrote:
> > On Feb 2 14:56, David Allsopp via Cygwin wrote:
> > > On Fri, 2 Feb 2024 at 14:18, Corinna Vinschen via Cygwin wrote:
> > > > Is it actually a safe
the
> > > > call to CreateProcess for a non-Cygwin binary, Cygwin restores the
> > > > error mode (for that thread only) to the value read at startup, calls
> > > > CreateProcess and then sets the error mode back.
> > >
> > > This sounds like a good
e change), but in some ways perhaps Cygwin
> > > should be using GetErrorMode on startup and instead of not inheriting
> > > it, ensuring that it sets whatever it received? i.e. just before the
> > > call to CreateProcess for a non-Cygwin binary, Cygwin restores the
> &
ly suggesting it be done this way (it feels more complicated
> > than just reverting the change), but in some ways perhaps Cygwin
> > should be using GetErrorMode on startup and instead of not inheriting
> > it, ensuring that it sets whatever it received? i.e. just before the
> &
on startup and instead of not inheriting
> it, ensuring that it sets whatever it received? i.e. just before the
> call to CreateProcess for a non-Cygwin binary, Cygwin restores the
> error mode (for that thread only) to the value read at startup, calls
> CreateProcess and then sets the error
ing it be done this way (it feels more complicated
than just reverting the change), but in some ways perhaps Cygwin
should be using GetErrorMode on startup and instead of not inheriting
it, ensuring that it sets whatever it received? i.e. just before the
call to CreateProcess for a non-Cygwin binary,
On Fri, 2 Feb 2024 at 12:55, Corinna Vinschen via Cygwin wrote:
> On Feb 2 09:43, David Allsopp via Cygwin wrote:
> > On Thu, 1 Feb 2024 at 10:02, Corinna Vinschen via Cygwin
> > wrote:
> > >
> > > The behaviour changed in 2020
> > >
> > > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;
w would you
get the behaviour you want?
I guess perhaps what's needed here is a command-wrapper tool like 'nice'
or 'env' which lets you run a command with the error-handling mode you want.
But that must already exist for Windows, right? :)
--
Problem reports: ht
On Feb 2 09:43, David Allsopp via Cygwin wrote:
> On Thu, 1 Feb 2024 at 10:02, Corinna Vinschen via Cygwin
> wrote:
> >
> > The behaviour changed in 2020
> >
> > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=21ec498d7f912
> >
> > not without a discussion
> >
> > https://cygwin.com/pi
On Thu, 1 Feb 2024 at 10:02, Corinna Vinschen via Cygwin
wrote:
>
> The behaviour changed in 2020
>
> https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=21ec498d7f912
>
> not without a discussion
>
> https://cygwin.com/pipermail/cygwin-patches/2020q4/010870.html
Aha, thank you! (congrats
v%d\n", ZSTD_versionNumber());
}
and compiling with
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
when I then run ./test.exe, I get the Windows critical-error-handler
dialog stating "The code execution cannot proceed because
libzstd-1.dll was not found. Reinstalling the program may fix this
problem.&q
s test, there is no popup displayed. However, it also calls
> Cygwin's sh and _that_ executes that program too, so something like
> "C:\cygwin64\bin\sh -c "./test.exe | sed ..." but then the popup error
> message appears. So somewhere along the line, Cygwin appears to be
> res
ogram too, so something like
"C:\cygwin64\bin\sh -c "./test.exe | sed ..." but then the popup error
message appears. So somewhere along the line, Cygwin appears to be
resetting the system error mode, and that appears contrary to previous
(old) messages on the subject.
Thanks,
David
dard v%d\n", ZSTD_versionNumber());
> > }
> >
> > and compiling with
> >
> > x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
> >
> > when I then run ./test.exe, I get the Windows critical-error-handler
> > dialog stating "The code exec
exe, I get the Windows critical-error-handler
dialog stating "The code execution cannot proceed because
libzstd-1.dll was not found. Reinstalling the program may fix this
problem."
My question is not how to fix the problem (I'm well aware of that),
but rather why that message is being
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
>
> when I then run ./test.exe, I get the Windows critical-error-handler
> dialog stating "The code execution cannot proceed because
> libzstd-1.dll was not found. Reinstalling the program may fix this
> problem."
>
> My q
exe, I get the Windows critical-error-handler
dialog stating "The code execution cannot proceed because
libzstd-1.dll was not found. Reinstalling the program may fix this
problem."
[snip]
x86_64-w64-mingw32-gcc is a cross compiler, a.k.a. the Mingw compiler,
not Cygwin's gcc.
Starting with this very trivial C program:
#include
#include
int main(void) {
printf("Zstandard v%d\n", ZSTD_versionNumber());
}
and compiling with
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
when I then run ./test.exe, I get the Windows critical-error-handler
dialog st
Thanks, Jon - I've removed the parameter for '
http://cygwinports.org/ports.gpg' and I'm not entirely sure why I had it
there in the first place.
However, on removing the parameter, I now get the error for every
referenced site in the script "Unable to get setup from
On 22/12/2023 14:41, James Hanley via Cygwin wrote:
when running the following script below - I always get the error indicated
in the subject line. If I click another site from the UI then after it
works fine. If I change the script to reflect that selected site from the
UI and re-run, I get
when running the following script below - I always get the error indicated
in the subject line. If I click another site from the UI then after it
works fine. If I change the script to reflect that selected site from the
UI and re-run, I get the same error mentioned. Any ideas?
""&
Hi,
On 27/11/2023 7:51 pm, tk--- via Cygwin wrote:
Any idea why this is happening ?
I suspect the reason is related to this long standing understanding of
Cygwin:
https://sourceware.org/legacy-ml/cygwin/2004-09/msg00087.html
On 03/09/2004 2:13 am, Corinna Vinschen wrote:
Public Key authenti
Hi,
We have observed that the command 'NET USER' issues en error message and
doesn't display the computer name, even if it completes the command
successfully:
>>>>>
User accounts for \\
o" to use StrictMode
and "yes" to install sshd as a service
I just press for the question for "Value of CYGWIN for the daemon".
cygrunsrv -S cygsshd will not start the sshd. "QueryServiceStatus: Win32 error
1062:"
I tried "ssh-keygen -A" - but no key
that I wrote, and he gets a seemingly nonsensical
> error that I don't understand.
> The script starts out pretty simply, just like this:
> --
> #! /bin/bash
> #set -x
> main() {
> if [ "$1" == "" ]; then
> usage;
> exit;
> fi
>
, but couldn't find the repo for
cygwin-devel anywhere.
This error was introduced with the most recent update to cpuset.h.
There is a public-visible mirror of the Cygwin tree at
https://github.com/cygwin/cygwin/blob/main/winsup/cygwin
and the problematic file can be found at
i
r
was worked on recently, but couldn't track it down any closer. I also
tried to find a git repository so I could find the commit so I could check
for similar errors on other headers, but couldn't find the repo for
cygwin-devel anywhere.
This error was introduced with the most recent update
I just updated to 3.4.9-1 and compiled some code, and it complained about
cpuset.h.
Specifically, "C++ requires a type specifier for all declarations", and
sure enough, there's no return type on line 52. So I changed my local copy
to the following, and it cleared things up:
#define CPU_ZERO_S(siz
- Fatal error 1 on xcb connection
winDeinitMultiWindowWM - Noting shutdown in progress (II) Server
terminated successfully (0). Closing log file.
Any pointers for how to troubleshoot?
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
>Not sure if you guys still exist or not? But having a problem porting over
>to Windows 10 and getting this error. Any suggestions?
>1 [main] bash 9592 find_fst_cwd: WARNING: Couldnt compute FAST_CWD pointer.
>Please report this problem to the public mailing list cygwin@cygwin.
Not sure if you guys still exist or not? But having a problem porting over
to Windows 10 and getting this error. Any suggestions?
1 [main] bash 9592 find_fst_cwd: WARNING: Couldnt compute FAST_CWD pointer.
Please report this problem to the public mailing list cygwin@cygwin.com
Thanks,
--
Rich
>bin/iperf3.exe -c 192.168.1.233 -P 1 -i 1 -p 5201 -f g -t 10Â Â Â 0 [main]
>iperf3 17636 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.Â
>Please report this problem tothe public mailing list cygwin@cygwin.com
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
bin/iperf3.exe -c 192.168.1.233 -P 1 -i 1 -p 5201 -f g -t 10 0 [main]
iperf3 17636 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please
report this problem tothe public mailing list cygwin@cygwin.com
--
Problem reports: https://cygwin.com/problems.html
FAQ:
ext copied in "c." to the cntlm.ini file below the
>following line:
> i. #
> PassNTLMv2 D5826E9C665C37C80B53397D5C07BBCB
>e. Save and Close the cntlm.ini file.
>When I press enter at the end of this li
i. #
PassNTLMv2 D5826E9C665C37C80B53397D5C07BBCB
e. Save and Close the cntlm.ini file.
When I press enter at the end of this line, cntlm -c cntlm.ini -I -M
http://google.ro, it returns the following error.
4 [main] cntlm 5768 find_fast_cwd: WARNING: Couldn&
erent problem.
>
> ...
>
> > He was getting a weird error on line 3, just saying this:
> > -
> > ...: line 3: syntax error near unexpected token `$'{\r''
> > ...: line 3: `main() {
> > ---
>
> If you run bash
pletely different problem.
...
> He was getting a weird error on line 3, just saying this:
> -----
> ...: line 3: syntax error near unexpected token `$'{\r''
> ...: line 3: `main() {
> ---
If you run bash with the "-o igncr" optio
On 6/26/2023 4:58 PM, Dan Harkless via Cygwin wrote:
On 6/26/2023 4:35 PM, David Karr via Cygwin wrote:
> > He was getting a weird error on line 3, just saying this:
> > -
> > ...: line 3: syntax error near unexpected token `$'{\r&#
On 6/26/2023 4:35 PM, David Karr via Cygwin wrote:
> He was getting a weird error on line 3, just saying this:
> -
> ...: line 3: syntax error near unexpected token `$'{\r''
> ...: line 3: `main() {
> ---
Apologies, I don't r
I'm seeing a problem with someone else's Cygwin setup, sort of similar to a
problem I asked about a couple of weeks ago, in that it's a problem with
the same user, but seemingly a completely different problem.
He is using a Bash script that I wrote, and he gets a seemingly nonsens
Achim Gratz wrote:
> Brian Inglis writes:
> > Problem writing tar (with Cygwin default sys) symlinks before target
> > created under Cygwin 3.5.0 - error messages are issued and tar exits
> > with failure status!
> […]
> > The only likely culprit between 3.4
efore target
> > created under Cygwin 3.5.0 - error messages are issued and tar exits
> > with failure status!
> […]
> > The only likely culprit between 3.4.6 and that commit seems to be
> > commit 2023-04-18 fa84aa4dd2fb43eaf7fcdfb040aef854f2f19d01 Cygwin: fix
> > er
Brian Inglis via Cygwin writes:
> Problem writing tar (with Cygwin default sys) symlinks before target
> created under Cygwin 3.5.0 - error messages are issued and tar exits
> with failure status!
[…]
> The only likely culprit between 3.4.6 and that commit seems to be
> co
Problem writing tar (with Cygwin default sys) symlinks before target created
under Cygwin 3.5.0 - error messages are issued and tar exits with failure status!
Also failed with the same issues under my own dev build based off origin/main
commit 2023-05-01
Hello,
I'm trying to create a volume shadow copy image using
$ dd if=/proc/sys/Device/HarddiskVolumeShadowCopy9 of=/dev/null
bs=4096 status=progress
but it ends prematurely with
116923437056 bytes (117 GB, 109 GiB) copied, 65 s, 1.8 GB/s
dd: error reading '/proc/
folks,
Just updated everything including perl and now git send-email fails with error
without prompting or requesting input for sendemail.confirm = always - address
headers have been sanitized and perl indents have been reduced:
$ git send-email --to=patches
0001-fhandler-proc.cc
>pwd 2444 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsu
pwd 2444 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer
--
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
On Fri, Apr 7, 2023 at 2:40 AM Jon Turney wrote:
>
> On 07/04/2023 02:44, Keith Thompson via Cygwin wrote:
> > Running setup-x86_64.exe on a Windows 10 laptop, I get this error message:
> >
> > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
> > 3
On 07/04/2023 02:44, Keith Thompson via Cygwin wrote:
Running setup-x86_64.exe on a Windows 10 laptop, I get this error message:
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: syntax error, unexpected $undefined, expecting COMMA or NL
https://mirrors.kernel.org
>> I'm concerned that the bad setup.zst might propagate to other mirrors.
Yes, identical error arising at
https://cygwin.mirror.uk.sargasso.net/x86_64/setup.zst
and elsewhere.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Do
Running setup-x86_64.exe on a Windows 10 laptop, I get this error message:
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: syntax error, unexpected $undefined, expecting COMMA or NL
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: unrecognized
SQLLIB/lib/db2api.lib" on 64-bit Cygwin.
Is this a Cygwin or native target binary?
*ERROR:*
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: *internal
error:* aborting at
/mnt/share/cygpkgs/binutils/binutils.x86_64/src/binutils-2.40/ld/ldlang.c:527
in compare_secti
his a Cygwin or native target binary?
*ERROR:*
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: *internal
error:* aborting at
/mnt/share/cygpkgs/binutils/binutils.x86_64/src/binutils-2.40/ld/ldlang.c:527
in compare_section
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-p
Is this a Cygwin or native target binary?
> *ERROR:*
> /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld:
> *internal
> error:* aborting at
> /mnt/share/cygpkgs/binutils/binutils.x86_64/src/binutils-2.40/ld/ldlang.c:527
> in compare_section
> /usr/lib/gcc/x86_
Hi,
I'm getting below errors while trying to connect IBM DB2 from 64-bit
Cygwin. Please find the below mentioned details.
1)Trying to compile the program using DB2_LIBRARY="C:/Program
Files/IBM/SQLLIB/lib/db2api.lib" on 64-bit Cygwin.
*ERROR:*
/usr/lib/gcc/x86_64-pc-cygwin/11/../
1 - 100 of 5960 matches
Mail list logo
