On Mar 24 15:42, Christian Franke via Cygwin wrote:
> Corinna Vinschen via Cygwin wrote:
> > On Mar 23 10:57, Christian Franke via Cygwin wrote:
> > > On Mar 21 16:15, Corinna Vinschen via Cygwin wrote:
> > > > On Mar 21 09:58, Christian Franke via Cygwin wrote:
> > > > > > > ..
> > > > I just gave
Corinna Vinschen via Cygwin wrote:
On Mar 23 10:57, Christian Franke via Cygwin wrote:
On Mar 21 16:15, Corinna Vinschen via Cygwin wrote:
On Mar 21 09:58, Christian Franke via Cygwin wrote:
..
I just gave it a try on W11. The results are even more funny than I
anticipated:
...
So, yeah, wi
On Mar 23 10:57, Christian Franke via Cygwin wrote:
> On Mar 21 16:15, Corinna Vinschen via Cygwin wrote:
> > On Mar 21 09:58, Christian Franke via Cygwin wrote:
> > > > > ..
> > I just gave it a try on W11. The results are even more funny than I
> > anticipated:
> >
> > ...
> >
> > So, yeah, wit
On Mar 21 16:15, Corinna Vinschen via Cygwin wrote:
On Mar 21 09:58, Christian Franke via Cygwin wrote:
..
I just gave it a try on W11. The results are even more funny than I
anticipated:
...
So, yeah, with your observations especially on older W10 versions and
with 8.1 doing the same thing,
On Mar 22 18:13, Ray Satiro via Cygwin wrote:
> On 3/21/2024 11:15 AM, Corinna Vinschen via Cygwin wrote:
> >https://cygwin.com/cgit/newlib-cygwin/commit/?id=48511f3d3847c
>
> The code in that commit doesn't look right. RtlGetNtVersionNumbers is a void
> function
The code doesn't request a re
s 8.1, RtlGetVersion/ RtlGetNtVersionNumbers
both report W10. The "Operating system context" in Task Manager reports
"Windows 8.1"
No surprise there.
Next I linked against a Windows 7 manifest:
GetVersionEx : 6.2.9200
RtlGetVersion : 10.0.22631
RtlGetNtVer
2631
RtlGetVersion : 10.0.22631
RtlGetNtVersionNumbers: 10.0.22631
The "Operating system context" in Task Manager is empty.
Next I linked against a Windows 8.1 manifest:
GetVersionEx : 6.3.9600
RtlGetVersion : 10.0.22631
RtlGetNtVersionNumbers: 10.0.22631
Corinna Vinschen via Cygwin wrote:
On Mar 20 12:39, Christian Franke via Cygwin wrote:
Corinna Vinschen via Cygwin wrote:
You have to create an application with an application manifest not
supporting your OS.
For Cygwin apps, this occured when you built, say, an executable under
Windows 8.1 be
On Mar 20 12:39, Christian Franke via Cygwin wrote:
> Corinna Vinschen via Cygwin wrote:
> > You have to create an application with an application manifest not
> > supporting your OS.
> >
> > For Cygwin apps, this occured when you built, say, an executable under
> > Windows 8.1 before Windows 10 s
On Wed, Mar 20, 2024 at 5:40 AM Christian Franke wrote:
Corinna Vinschen via Cygwin wrote:
>
> > For Cygwin apps, this occured when you built, say, an executable under
> > Windows 8.1 before Windows 10 support was added to the Cygwin toolchain:
> > the manifest linked to the Cygwin executable didn
Corinna Vinschen via Cygwin wrote:
On Mar 19 09:18, Bill Stewart via Cygwin wrote:
On Tue, Mar 19, 2024 at 9:01 AM Richard Campbell wrote:
On Tue, Mar 19, 2024 at 9:04 AM Bill Stewart via Cygwin
wrote:
Can you please clarify the circumstances under which the RtlGetVersion
function "may not
On Tue, Mar 19, 2024 at 10:21 AM Corinna Vinschen wrote:
On Mar 19 09:18, Bill Stewart via Cygwin wrote:
>
> > I'm not sure of the exact scenario that led to the "RtlGetVersion is
> > subject to manifesting" conclusion, but I can't reproduce it.
>
> You have to create an application with an applic
On Mar 19 09:18, Bill Stewart via Cygwin wrote:
> On Tue, Mar 19, 2024 at 9:01 AM Richard Campbell wrote:
>
> On Tue, Mar 19, 2024 at 9:04 AM Bill Stewart via Cygwin
> > wrote:
> >
> > > Can you please clarify the circumstances under which the RtlGetVersion
> > > function "may not return the corr
On Tue, Mar 19, 2024 at 9:01 AM Richard Campbell wrote:
On Tue, Mar 19, 2024 at 9:04 AM Bill Stewart via Cygwin
> wrote:
>
> > Can you please clarify the circumstances under which the RtlGetVersion
> > function "may not return the correct values"?
>
> "Originally, using RtlGetVersion instead of G
On Tue, Mar 19, 2024 at 9:04 AM Bill Stewart via Cygwin
wrote:
>
> Can you please clarify the circumstances under which the RtlGetVersion
> function "may not return the correct values"?
>
"Originally, using RtlGetVersion instead of GetVersionEx was supposed to
fix the fact that GetVersionInfo re
On Tue, Mar 19, 2024 at 4:21 AM Christian Franke wrote:
Cygwin uses the undocumented RtlGetNtVersionNumbers() from ntdll.dll
> because even RtlGetVersion() may not return the correct values. See
> function wincapc::init()
>
> https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/winca
Cedric Blancher via Cygwin wrote:
How does cygwin uname -s work, i.e. how does it get the OS version,
revision and build number ('10.0-19045')?
I tried to replicate it via GetVersionEx(), but that is deprecated.
AFAICS, MS does not offer an official way to retrieve the actual Windows
version
Good morning!
How does cygwin uname -s work, i.e. how does it get the OS version,
revision and build number ('10.0-19045')?
I tried to replicate it via GetVersionEx(), but that is deprecated.
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem re
esday, November 8, 2023 10:24 AM
To: 'cygwin@cygwin.com'
Subject: RE: [EXT] Re: XWin copy/paste succeeds on Windows 7, crashes on
Windows 11 Enterprise.
I have made an important discovery here. I've been using "release" mode when
compiling, and had the following resu
When using "translations_copypaste", the program crashes.
On Windows 7 professional (release):
When using "translations_ignore", it correctly just prints "Ignoring" every
time I cut/copy/paste.
When using "translations_copypaste", it correctly cuts/c
t; every
time I cut/copy/paste.
When using "translations_copypaste", the program crashes.
On Windows 7 professional:
When using "translations_ignore", it correctly just prints "Ignoring" every
time I cut/copy/paste.
When using "translations_copypaste", i
>-Original Message-
>From: Brian Inglis
>Sent: Monday, November 6, 2023 2:14 PM
>To: cygwin@cygwin.com
>Cc: Stone, Timothy M
>Subject: Re: [EXT] Re: XWin copy/paste succeeds on Windows 7, crashes on
>Windows 11 Enterprise.
>On 2023-11-06 12:04, Stone, Ti
On 2023-11-06 12:04, Stone, Timothy M via Cygwin wrote:
Have you tried the original Motif copy/cut/paste C-Ins/S-Del/S-Ins
available at Windows system level to see if that can give you some hints
about what's happening?
I don't know how to do this...can you explain?
Try Ctrl-Insert/Shift-Delet
>Have you tried the original Motif copy/cut/paste C-Ins/S-Del/S-Ins available
>at Windows system level to see if that can give you some hints about what's
>happening?
>
>--
>Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
>
>La perfection est atteinte Perf
copy/paste functionality in
TextFieldWidgets:
*Cut/Copy/Paste works perfectly on Windows 7 Professional
*Cut/Copy/Paste does not work at all and typically crashes on
Windows 11 Enterprise
I'm assuming this means "the X server crashes", but it's not exactly clear.
If th
calls ignore_cut_paste()
when the same keys are pressed. This function just prints a message to the
console ("Ignoring") so I know it's working.
This is almost the entire program. All that is missing is initializing the
parent and the app_context.
What happens is:
On Windows 7
dgets:
*Cut/Copy/Paste works perfectly on Windows 7 Professional
*Cut/Copy/Paste does not work at all and typically crashes on Windows 11
Enterprise
I'm assuming this means "the X server crashes", but it's not exactly clear.
If that is the case, there are some i
Hi folks,
I'm having a really hard time debugging this issue.
If I use the exact same version of cygwin and XWin, exact same code, exact same
Motif GUI app...
I find that when I try to use copy/paste functionality in TextFieldWidgets:
*Cut/Copy/Paste works perfectly on Wind
On Sun, May 8, 2022 at 2:09 PM Takashi Yano wrote:
> I have pushed two patches to cygwin-3_3-branch. I am not sure
> why, but the issue (bash with readline crash) seems to disappear.
>
> Could you please try?
It no longer crashes with these fixes.
Thanks!
- Orgad
--
Problem reports: http
On Sat, 7 May 2022 09:20:51 +0900
Takashi Yano wrote:
> On Sat, 7 May 2022 05:13:23 +0900
> Takashi Yano wrote:
> > On Fri, 6 May 2022 21:16:10 +0200 (CEST)
> > Johannes Schindelin wrote:
> > > Takashi, for the record, I find it hard to believe that the bug is
> > > libreadline's because Orgad's sc
On Sat, 7 May 2022 05:13:23 +0900
Takashi Yano wrote:
> On Fri, 6 May 2022 21:16:10 +0200 (CEST)
> Johannes Schindelin wrote:
> > Takashi, for the record, I find it hard to believe that the bug is
> > libreadline's because Orgad's scenario works if he reverts that patch in
> > the _MSYS2 runtime_,
On Fri, 6 May 2022 21:16:10 +0200 (CEST)
Johannes Schindelin wrote:
> Takashi, for the record, I find it hard to believe that the bug is
> libreadline's because Orgad's scenario works if he reverts that patch in
> the _MSYS2 runtime_, _and_ it is rather dubious that libreadline would
> potentially
Hi Orgad,
On Fri, 6 May 2022, Orgad Shaneh wrote:
> Adding @Johannes Schindelin to the loop.
Thank you, but that unfortunately does not work on this list. Due to the
policy to never reply-to-all, the subsequent replies immediately lost me.
The reason why MSYS2's Bash does not depend on the `lib
On Fri, 6 May 2022 17:05:02 +0300
Orgad Shaneh wrote:
> On Fri, May 6, 2022 at 1:49 AM Takashi Yano wrote:
> > > Only bash in msys2 package fails.
> >
> > I identified the difference which causes the issue
> > between bash built from original source and msys2 bash.
> >
> > If --enable-readline and
On 2022-05-06 08:05, Orgad Shaneh wrote:
On Fri, May 6, 2022 at 1:49 AM Takashi Yano wrote:
Only bash in msys2 package fails.
I identified the difference which causes the issue
between bash built from original source and msys2 bash.
If --enable-readline and --with-installed-readline is specif
On Fri, May 6, 2022 at 1:49 AM Takashi Yano wrote:
> > Only bash in msys2 package fails.
>
> I identified the difference which causes the issue
> between bash built from original source and msys2 bash.
>
> If --enable-readline and --with-installed-readline is specified
> to configure, the problem
On Thu, 5 May 2022 15:44:40 +0900
Takashi Yano wrote:
> On Thu, 5 May 2022 13:41:20 +0900
> Takashi Yano wrote:
> > I downloaded bash source files from:
> > https://git.savannah.gnu.org/git/bash.git
> > and built it by:
> > ./configure && make
> > and replaced /usr/bin/bash.
> >
> > Then the issue
On Thu, 5 May 2022 13:41:20 +0900
Takashi Yano wrote:
> I downloaded bash source files from:
> https://git.savannah.gnu.org/git/bash.git
> and built it by:
> ./configure && make
> and replaced /usr/bin/bash.
>
> Then the issue disappeared.
> Now, I start to suspect the issue is a bug of msys2 bash
re_attach_mutex (mutex_timeout);
> > > > > > >fhandler_console::need_invisible ();
> > > > > > >release_attach_mutex ();
> > > > > >
> > > > > > A few things about this.
> > > > > >
> &g
gt; > > > > A few things about this.
> > > > >
> > > > > 1) bash exits with exit code 127 for 'mintty bash'
> > > > > 2) 'mintty bash' does not work, but 'mintty ash' and 'mintty tcsh'
> >
ole::need_invisible ();
> > > > >release_attach_mutex ();
> > > >
> > > > A few things about this.
> > > >
> > > > 1) bash exits with exit code 127 for 'mintty bash'
> > > > 2) 'mintty bash' does no
with exit code 127 for 'mintty bash'
> > > 2) 'mintty bash' does not work, but 'mintty ash' and 'mintty tcsh' work.
> >
> > Right. mintty dash also works.
> >
> > Notice that I did *not* set enable_pcon (not supported
release_attach_mutex ();
> >
> > A few things about this.
> >
> > 1) bash exits with exit code 127 for 'mintty bash'
> > 2) 'mintty bash' does not work, but 'mintty ash' and 'mintty tcsh' work.
>
> Right. mintty dash also works.
&
On Wed, May 4, 2022 at 2:16 PM Takashi Yano wrote:
>
> > Reduced the revert to this:
> > @@ -979,16 +979,10 @@ fhandler_pty_slave::open (int flags, mode_t)
> > code does not work as expected because it calls Win32
> > API directly rather than cygwin read()/write(). Due to
> >
; > > > On Tue, May 3, 2022 at 6:23 PM Takashi Yano
> > > > wrote:
> > > > >
> > > > > On Tue, 3 May 2022 14:47:17 +0300
> > > > > Orgad Shaneh wrote:
> > > > > > Hi,
> > > > > >
> >
t; > >
> > > > On Tue, 3 May 2022 14:47:17 +0300
> > > > Orgad Shaneh wrote:
> > > > > Hi,
> > > > >
> > > > > Running `mintty ./bash` crashes on Windows 7 on cygwin-3_3-branch.
> > > > >
> > > > > Tes
t; > > > Hi,
> > > >
> > > > Running `mintty ./bash` crashes on Windows 7 on cygwin-3_3-branch.
> > > >
> > > > Tested in MSYS2 on merge-3.3 branch from
> > > > https://github.com/orgads/msys2-runtime-1. It includes the tip of
>
On Tue, 3 May 2022 18:52:28 +0300
Orgad Shaneh wrote:
> On Tue, May 3, 2022 at 6:23 PM Takashi Yano wrote:
> >
> > On Tue, 3 May 2022 14:47:17 +0300
> > Orgad Shaneh wrote:
> > > Hi,
> > >
> > > Running `mintty ./bash` crashes on Windows 7 on c
On Tue, May 3, 2022 at 6:23 PM Takashi Yano wrote:
>
> On Tue, 3 May 2022 14:47:17 +0300
> Orgad Shaneh wrote:
> > Hi,
> >
> > Running `mintty ./bash` crashes on Windows 7 on cygwin-3_3-branch.
> >
> > Tested in MSYS2 on merge-3.3 branch from
> >
On Tue, 3 May 2022 14:47:17 +0300
Orgad Shaneh wrote:
> Hi,
>
> Running `mintty ./bash` crashes on Windows 7 on cygwin-3_3-branch.
>
> Tested in MSYS2 on merge-3.3 branch from
> https://github.com/orgads/msys2-runtime-1. It includes the tip of
> cygwin-3_3-branch as
Hi,
Running `mintty ./bash` crashes on Windows 7 on cygwin-3_3-branch.
Tested in MSYS2 on merge-3.3 branch from
https://github.com/orgads/msys2-runtime-1. It includes the tip of
cygwin-3_3-branch as of today (05827d2df8).
Steps to reproduce:
1. Start cmd.exe
2. cd \usr\bin
3. mintty ./bash
GDB
On 9/17/2020 4:27 PM, Roland Roberts wrote:
On 8/24/2020 5:43 PM, Roland Roberts wrote:
I have one machine, a company machine which makes it hard to post details,
which is running Windows 7. We run cygwin as our development environment for
Java, but Java is installed as a Windows program. The
On 8/24/2020 5:43 PM, Roland Roberts wrote:
I have one machine, a company machine which makes it hard to post
details, which is running Windows 7. We run cygwin as our development
environment for Java, but Java is installed as a Windows program. The
scripts that do the builds are bash scripts
I have one machine, a company machine which makes it hard to post
details, which is running Windows 7. We run cygwin as our development
environment for Java, but Java is installed as a Windows program. The
scripts that do the builds are bash scripts that pull down updated code
from svn, then
On 11/28/2019 6:53 PM, P via cygwin wrote:
Additional update after experimenting:
email is working using smtp.office365.com:25 for outlook and smtp.gmail.com:587
for gmail.
Yahoo email no longer works for me.
Again, a firewall related to port 465 would explain this,
so I still feel that;s wort
Additional update after experimenting:
email is working using smtp.office365.com:25 for outlook and smtp.gmail.com:587
for gmail.
Yahoo email no longer works for me.
FYI,
Mike
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 2019-11-28 07:48, Eliot Moss wrote:
> On 11/28/2019 8:01 AM, Mike via cygwin wrote:
>> After upgrading to Windows 10, Cygwin smtp email doesn't work.
>> Get the error:
>>> $ echo "this is a test"|email -s "test" pel...@yahoo.com
>>> email: FATAL: Smtp error: Lost connection with SMTP server
>> H
On 11/28/2019 8:01 AM, P via cygwin wrote:
After upgrading to Windows 10, Cygwin smtp email doesn't work.
Get the error:
$ echo "this is a test"|email -s "test" pel...@yahoo.com
email: FATAL: Smtp error: Lost connection with SMTP server
Here's my config:
$ email-config
Please enter your Fr
After upgrading to Windows 10, Cygwin smtp email doesn't work.
Get the error:
$ echo "this is a test"|email -s "test" pel...@yahoo.com
email: FATAL: Smtp error: Lost connection with SMTP server
Here's my config:
$ email-config
Please enter your From: name (e.g., John Doe) [Mike]:
Please ent
Greetings, Bill Stewart!
> On Mon, Mar 11, 2019 at 3:38 PM Achim Gratz wrote:
>> Try it with a group that has several hundred members. Then try with
>> several hundreds of such groups. Then try it again over a DSL line or
>> some VPN routing you across the globe that has a roundtrip measured i
On Mon, Mar 11, 2019 at 3:38 PM Achim Gratz wrote:
> Try it with a group that has several hundred members. Then try with
> several hundreds of such groups. Then try it again over a DSL line or
> some VPN routing you across the globe that has a roundtrip measured in
> tenths of seconds.
Underst
Bill Stewart writes:
> FWIW, not sure if you're using the IADsNameTranslate interface (
> https://docs.microsoft.com/en-us/windows/desktop/api/iads/nn-iads-iadsnametranslate).
[…]
> Init depends on a available AD server (GC in this example), of course, but
> seems pretty fast in my tests.
Try it w
On Thu, Feb 28, 2019 at 2:39 AM Corinna Vinschen wrote:
> > Since windows seems to adhere to the rule:
> > "Case preserving", but "case ignoring", what does it
> > mean to make sure all user and group names are
> > case-correct?
>
> This all started here:
> https://cygwin.com/ml/cygwin/2019-02/ms
On 2/28/2019 1:39 AM, Corinna Vinschen wrote:
This is all more or less moot as soon as OpenSSH 8.0 comes out, which
will contain patches to handle user and group names case-insensitive,
finally.
Please forgive my ignorance of cygwin's internals, but why does
cygwin1.dll need to do anything on
On Feb 27 19:11, L A Walsh wrote:
> On 2/27/2019 12:50 PM, Corinna Vinschen wrote:
> > The fix was this one:
> > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb
> > Corinna
> >
> >
>
> My question would be related to the comment with the fix:
>
> "made sure all u
On 2/27/2019 12:50 PM, Corinna Vinschen wrote:
> The fix was this one:
> https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb
> Corinna
>
>
My question would be related to the comment with the fix:
"made sure all user and group names are case-correct"
Since windows s
On 2/27/2019 12:50 PM, Corinna Vinschen wrote:
Apparently same problem as reported in
https://cygwin.com/ml/cygwin/2019-02/msg00301.html
The fix was this one:
https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb
Thanks. Yeah, our AD has 152 groups.
--
Problem reports:
On Feb 27 12:44, Jerry Baker via cygwin wrote:
> On 2/27/2019 12:23 PM, Jerry Baker via cygwin wrote:
> > I am also happy to report that cygwin1-20190226.dll fixes the issue.
>
> For the curious, the fix happened between cygwin1-20190219.dll and
> cygwin1-20190223.dll.
>
> Maybe the changes in se
On 2/27/2019 12:23 PM, Jerry Baker via cygwin wrote:
I am also happy to report that cygwin1-20190226.dll fixes the issue.
For the curious, the fix happened between cygwin1-20190219.dll and
cygwin1-20190223.dll.
Maybe the changes in sec_auth.cc. They look suspicious.
--
Problem reports:
On 2/27/19 2:19 PM, Jerry Baker via cygwin wrote:
> On 2/26/2019 10:55 PM, Brian Inglis wrote:
>> As Cygwin is a rolling release system, if you are not running current
>> releases,
>> some CVE security issues may remain unpatched, and your system may not be
>> compliant to your corporate security p
On 2/27/2019 12:19 PM, Jerry Baker via cygwin wrote:
I narrowed it down to my network. If I unplug the Ethernet cable the
problem disappears. If I plug it in, the problem returns. I can
reproduce it 100% for an hour straight, going back and forth.
I am also happy to report that cygwin1-20190226
On 2/26/2019 10:55 PM, Brian Inglis wrote:
As Cygwin is a rolling release system, if you are not running current releases,
some CVE security issues may remain unpatched, and your system may not be
compliant to your corporate security policies (you may want to check with your
IT security and/or IT
On Wed, Feb 27, 2019 at 4:45 AM Steven Penny wrote:
>
> On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote:
> > Well I guess it's a good thing there's only one possible state of
> > Windows 7 x64 which allows us to determine that there's no p
s, and
other newer hardware, are only supported under Windows 10 Enterprise, with
support for selected enterprise vendor systems with Skylake CPUs under Windows
7, and nothing newer.
A minimal datapoint might be running "cygcheck cygcheck" under cmd, with
whatever explicit path is requ
On Tue, 26 Feb 2019 18:01:27, Jerry Baker via cygwin" wrote:
> Trying to think of what could make 2.11.x work and 3.0.1 fail on the i7
> system. The only difference I can think of is that the i7 system is a
> member of a domain.
(first I would suggest a good night's sleep :-)
If you really be
> On Feb 26, 2019, at 8:55 PM, Jerry Baker wrote:
>
> I don't work for free,
This is open source. Given that the people here do, that's not a very good
argument.
> especially for hostile people with over inflated egos and crippling social
> disorders.
Don't feed it by arguing.
> The onus is on
On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote:
Well I guess it's a good thing there's only one possible state of
Windows 7 x64 which allows us to determine that there's no possibility
of a bug simply by running a single instance in one VM. We're go
t; Data Execution
Prevention tab. I am using the top setting (Turn on DEP for essential
Windows programs and services only) rather than (Turn on DEP for all
programs ad services except those I select). I'm not sure how Address
Space Layout Randomisation (ASLR) is managed on Windows 7, but I thin
istake to assume that the cygwin community was interested
in interoperability. I should have done more research before making
that unwarranted assumption.
it very much is your problem, as im using Windows 7 x64 just fine with
Cygwin.
Well I guess it's a good thing there's only one pos
ues.
> > There are about 3,700 workstations with this machine image just in this
> > building.
>
> Problem machine is an Intel i7 system with 16GB RAM. Ironically, the
> same Windows 7 on an old AMD Athlon X2 system with 4GB of RAM does not
> exhibit the issue at all.
>
> T
mmunity was interested in
interoperability. I should have done more research before making that
unwarranted assumption.
it very much is your problem, as im using Windows 7 x64 just fine with Cygwin.
and its your problem else you wouldnt have come here posting. you can start
threads with clickbait titles
On 2/26/2019 6:43 PM, Steven Penny wrote:
i would like to make that last point vividly clear: its on you to do that
testing. ive already given a clear refutation of your original point, so
the
ball is now squarely in your court.
Not really. I don't work for free, especially for hostile people
On Tue, 26 Feb 2019 17:50:10, "Jerry Baker via cygwin" wrote:
Glad to. Please let me know what evidence will suffice to prove that.
pretty simple
1. get the Windows 7 x64 from here
https://softlay.net/operating-system/windows-7-download.html
2. get virtualbox from here
https://virt
an Intel i7 system with 16GB RAM. Ironically, the
same Windows 7 on an old AMD Athlon X2 system with 4GB of RAM does not
exhibit the issue at all.
Trying to think of what could make 2.11.x work and 3.0.1 fail on the i7
system. The only difference I can think of is that the i7 system is a
problem?
So i am here to answer that question. I was concerned as *I* use Windows
7 x64
as well. I just tested with a pristine virtual machine with Windows 7
x64 and
Cygwin 3.0.1-1 and it works perfectly fine. Note it works fine with
Cygwin.bat
or with the shortcut.
And you installed all the
em?
So i am here to answer that question. I was concerned as *I* use Windows 7 x64
as well. I just tested with a pristine virtual machine with Windows 7 x64 and
Cygwin 3.0.1-1 and it works perfectly fine. Note it works fine with Cygwin.bat
or with the shortcut.
So *something* is wrong on your syst
On 2/26/2019 2:48 PM, Doug Henderson wrote:
Good. This tells us something important. Right after the path listing,
cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a
cygwin exe which uses cygwin1.dll, cygintl-8.dll, and cygiconv-2.dll.
That narrow the problem. These three DLLs m
On Tue, 26 Feb 2019 at 15:10, Jerry Baker via cygwin <> wrote:
>
> On 2/26/2019 1:56 PM, Doug Henderson wrote:
> > Two things.
> > 1. You can execute cygcheck by navigating to C:\cygwin or C:\cygwin64
> > in Explorer and opening a command or powershell window from explorer's
> > shift-context menu.
On 2/26/2019 2:10 PM, Jerry Baker wrote:
Thanks for the tips. I made a completely fresh install in a new
directory and attempted all three suggestions. Here are the results:
1. That command gets part way through and then hangs with the blinking
cursor after listing the directories in the path va
On 2/26/2019 1:56 PM, Doug Henderson wrote:
Two things.
1. You can execute cygcheck by navigating to C:\cygwin or C:\cygwin64
in Explorer and opening a command or powershell window from explorer's
shift-context menu. There, run the following command:
.\cygcheck.exe -csr > ..\home\CYGWINUSERNAME\
On Tue, 26 Feb 2019 at 13:00, Jerry Baker via cygwin <> wrote:
>
> On 2/26/2019 11:32 AM, Jerry Baker via cygwin wrote:
> > Yes, but by wiping out the whole tree and installing 64-bit. You filled
> > me with doubt, so I browsed around with a hex editor looking at quite a
> > few random executables
> On Feb 26, 2019, at 2:00 PM, Jerry Baker wrote:
>
> I just installed from scratch in a new directory. Same issue. Nothing runs.
If cygcheck doesn't run, then it would appear there's (at least) something
non-cygwin-related
going on. cygcheck isn't a cygwin program, i.e. it doesn't link to or d
On 2/26/2019 11:32 AM, Jerry Baker via cygwin wrote:
Yes, but by wiping out the whole tree and installing 64-bit. You filled
me with doubt, so I browsed around with a hex editor looking at quite a
few random executables and dll files in cygwin\bin and all of them I
checked are 64-bit.
I just in
On 2/26/2019 11:19 AM, Ken Brown wrote:
Here's a wild guess, based on the fact that your Cygwin installation is in
C:\cygwin rather than C:\cygwin64. Do you have a 32-bit Cygwin installation
that you updated using setup-x86_x64.exe instead of setup-x86.exe?
Yes, but by wiping out the whole tre
On 2/26/2019 1:59 PM, Jerry Baker via cygwin wrote:
> On 2/26/2019 10:44 AM, Vince Rice wrote:
>> What is also described on the page are the reporting guidelines. Please read
>> them again, paying special
>> attention to the bolded part.
Here's a wild guess, based on the fact that your Cygwin ins
Configuration Diagnostics
Current System Time: Tue Feb 26 09:42:22 2019
Windows 7 Professional Ver 6.1 Build 7601 Service Pack 1
Path: C:\ProgramData\Oracle\Java\javapath
C:\app\product\11.2.0\client_1\bin
C:\Program Files (x86)\Intel\iCLS Client\
C:\Program Files\Intel
> On Feb 26, 2019, at 12:37 PM, Jerry Baker wrote:
>
> That's why you're reading about it "on the appropriate list," as described on
> that page. It's a take it or leave it thing. I report it, and the cygwin
> community can do whatever they like with it - ignore it, investigate it,
> shoot the
On Tue, Feb 26, 2019 at 12:38 PM Jerry Baker via cygwin
wrote:
>
> That's why you're reading about it "on the appropriate list," as
> described on that page. It's a take it or leave it thing. I report it,
> and the cygwin community can do whatever they like with it - ignore it,
> investigate it, s
On 2/26/2019 10:30 AM, Houder wrote:
Jerry, short answer:
--
Problem reports: http://cygwin.com/problems.html
^^^
^^^
^^^
That
> On 2/26/2019 7:38 AM, Jerry Baker via cygwin wrote:
> > I have a large installation of cygwin on Windows 7 x64 for the last
> > decade that has been working without issue. When I use setup-x86_64.exe
> > (2.895) to upgrade the cygwin 2.11.2-1 package to cygwin 3.0.1-1,
1 - 100 of 860 matches
Mail list logo
