> I have some time available now and I will look again at the problem,
> but if some Python expert want to also look on it, I will appreciate.
MSYS2 does have a working Python 3.12.8
https://github.com/msys2/MSYS2-packages/tree/master/python
--
Problem reports: https://cygwin.com/problem
On 05/11/2024 17:48, rct+cygwin--- via Cygwin wrote:
The latest Python in Cygwin, 3.9, reaches end of life in less than a
year, 2025-10, according to [0].
Some packages (numpy) are dropping support for 3.9 [1].
Can we please get an update on the status of a newer Python for Cygwin?
Thanks
The latest Python in Cygwin, 3.9, reaches end of life in less than a year,
2025-10, according to [0].
Some packages (numpy) are dropping support for 3.9 [1].
Can we please get an update on the status of a newer Python for Cygwin?
Thanks!
[0] - https://devguide.python.org/versions/
[1
eri, where the test release of Python 3.9.18 was removed.
(The problem with 3.9.18 might have been related to "pip install occasionally
hangs" [2].
It looks like Python 3.9.16-1 is still the most current release.
Have I missed something, or can we get a status update?
Thanks!
0
On 2024-09-08 07:45, Mark Liam Brown via Cygwin wrote:
On Sun, Sep 8, 2024 at 10:50 AM Arthur Norman wrote:
I have been VERY happily pleased about how well Cygwin runs using
Prism on Windows/ARM64. I can build and test my x86_64 code there using it
despite the underlying CPU being an ARM. My g
On Sun, Sep 8, 2024 at 10:50 AM Arthur Norman wrote:
>
> I have been VERY happily pleased about how well Cygwin runs using
> Prism on Windows/ARM64. I can build and test my x86_64 code there using it
> despite the underlying CPU being an ARM. My genuine Windows/x86_64 machine
> is not that new the
on Windows/ARM64 you can of
course fire up WSL there which gives you a genuine Linux world, but at
present using that to cross-build for native Windows/ARM64 is something I
have not found good pointers about.
Arthur
On Sat, 7 Sep 2024, Mark Liam Brown via Cygwin wrote:
Greetings!
What is the
Greetings!
What is the current status of Cygwin on Windows/ARM64? Does it work?
Mark
--
IT Infrastructure Consultant
Windows, Linux
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
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
Am 18.06.2023 um 22:00 schrieb Ross Boulet via Cygwin:
I was looking at the settings for mintty and saw the new option (new as of
3.6.4 from March) for a status line. I decided to try it out. Sure enough, a
status line appeared at the bottom. All was well until I tried to open a new
mintty
I was looking at the settings for mintty and saw the new option (new as of
3.6.4 from March) for a status line. I decided to try it out. Sure enough, a
status line appeared at the bottom. All was well until I tried to open a new
mintty window and nothing seemed to happen. After a little
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
t a try.
>
> Thank you for providing the snapshot.
> I was able to get the values of SigBlk and SigIgn.
>
> Below are the results I have tried.
>
> $ cat /proc/$$/status
> Name: bash
> State: S (sleeping)
> Tgid: 1616
> Pid:1616
> PPid: 1615
> Uid:
values of SigBlk and SigIgn.
Below are the results I have tried.
$ cat /proc/$$/status
Name: bash
State: S (sleeping)
Tgid: 1616
Pid:1616
PPid: 1615
Uid:197609 197609 197609 197609
Gid:197121 197121 197121 197121
VmSize: 6720 kB
VmLck: 0 kB
VmRSS: 10112
On Mar 1 12:06, Corinna Vinschen wrote:
> On Mar 1 14:35, Ken SATO wrote:
> > Hello,
> >
> > When I run the following command, the values for SigBlk and SigIgn are zero.
> > How can I get the correct value?
>
> You can't. We don't have the information readily available without
> asking the pro
On Mar 1 14:35, Ken SATO wrote:
> Hello,
>
> When I run the following command, the values for SigBlk and SigIgn are zero.
> How can I get the correct value?
You can't. We don't have the information readily available without
asking the process itself. While we have a communication mechanism
in
Hello,
When I run the following command, the values for SigBlk and SigIgn are zero.
How can I get the correct value?
$ cat /proc/$$/status
Name: bash
State: S (sleeping)
Tgid: 1553
Pid:1553
PPid: 1552
Uid:197609 197609 197609 197609
Gid:197121 197121 197121 197121
VmSize
the Meetings/Task from Desktop/ Mobile
3. Get to know your field sales team work-status.
4. Record Sales details digitally
5. Calculate the distance travelled
6. Claim your Expenses Instantly
7. Instant Leave Application and Approvals
I’m also happy to arrange a brief
Thanks for the responses.
The uname output was already in my attachment. I executed cat as
/usr/bin/cat.exe. Cygcheck cat is also in my original attachment.
I attached the cygcheck -svr. The other Cygwin installations referenced
are from my debugging and are not active. The missing Perl f
On 2019-03-26 21:55, Chris Wagner wrote:
> Hi all. A few days ago I noticed that cat.exe was failing without printing
> any
> output or errors and exiting with status 3. I tried rebooting, updating my
> Cygwin, even a fresh install of Base only. I removed all recently install
Chris Wagner wrote:
Hi all. A few days ago I noticed that cat.exe was failing without printing any
output or errors and exiting with status 3. I tried rebooting, updating my
Cygwin, even a fresh install of Base only. I removed all recently installed
Windows software and nothing changed
On Tue, 26 Mar 2019 at 21:55, Chris Wagner <> wrote:
>
> Hi all. A few days ago I noticed that cat.exe was failing without
> printing any output or errors and exiting with status 3. I tried
Please show us the output of these three commands
uname -a
which -a cat
file $( which
Hi all. A few days ago I noticed that cat.exe was failing without
printing any output or errors and exiting with status 3. I tried
rebooting, updating my Cygwin, even a fresh install of Base only. I
removed all recently installed Windows software and nothing changed.
What's truly st
On Aug 21 16:53, Livio Bertacco wrote:
> Thanks Corinna, I tried the developer snapshot and the VmSize line from
> "status" file looks good now.
>
> What do you think about adding the VmPeak line too? (I can create the patch
> myself).
>
> > On second thought
Thanks Corinna, I tried the developer snapshot and the VmSize line from
"status" file looks good now.
What do you think about adding the VmPeak line too? (I can create the patch
myself).
> On second thought there's more wrong than just that.
> Just div
On Aug 17 19:14, Corinna Vinschen wrote:
> On Aug 17 16:05, Livio Bertacco wrote:
> > Hi,
> > While playing with reading process memory usage in Linux and cygwin, I
> > found that cygwin reports too large values in /proc/self/status (in 2.10.0
> > and earlier).
> >
On Aug 17 16:05, Livio Bertacco wrote:
> Hi,
> While playing with reading process memory usage in Linux and cygwin, I
> found that cygwin reports too large values in /proc/self/status (in 2.10.0
> and earlier).
> Whenever I was allocating a few kB in my test program, the VmSize
Hi,
While playing with reading process memory usage in Linux and cygwin, I
found that cygwin reports too large values in /proc/self/status (in 2.10.0
and earlier).
Whenever I was allocating a few kB in my test program, the VmSize line in
/proc/self/status was growing several times faster.
Small
On Jun 28 10:19, Timo Maier wrote:
> Hello Corinna,
>
> yes, pls send me the DLL, I will try.
Thanks for testing!
Turns out the drive in question returns a non-standard error code,
ERROR_NOT_READY rather than ERROR_NO_MEDIA_IN_DRIVE to indicate that no
media is present. This error code is not d
Hello Corinna,
yes, pls send me the DLL, I will try.
--
Timo
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
t; write and read the tape.
>
> Before starting to write I want to check if the tape is ready with "status",
> but no matter if the tape is in or not, status always says ONLINE.
>
> Can anyone help, please? Thanks in advance.
The ONLINE status is a result of the follow
if the tape is ready with "status",
but no matter if the tape is in or not, status always says ONLINE.
Can anyone help, please? Thanks in advance.
***
C:\Tools\cygwin64\bin>mt -f /dev/nst0 status 3
drive type : 01 (Unknown type of tape device)
On 12/11/2017 5:04 PM, Richard H Lee wrote:
>
> So if you lstat("//HEAD") and you are on a network that does DNS
> hijacking, Cygwin will attempt to connect to the ISP's server via SMB.
> As the ISP's server is a publicly facing IP address, it probably just
> black holes any incoming connection re
On 21/11/2017 10:27, Adam Dinwoodie wrote:
(I believe this is a bug in Git, on the grounds that (a) Git in general
supports POSIX systems and giving special meaning to paths starting with
`\\` is allowed, if unusual, POSIX behaviour, and (b) Git specifically
supports Cygwin, and this is very well
es: http://cygwin.com/problems.html.
>
> - The version of Git you're running, per `git --version`, if it hasn't
> been installed using Cygwin's setup-*.exe installers.
>
> - The current working directory when you run `git status`.
>
> - Details of the director
Original message "Re: Git status delay" from "Adam Dinwoodie
(a...@dinwoodie.org)" sent 21. listopadu 2017, 11:27:28,
msgid:20171121102728.gm20...@dinwoodie.org (3557 bytes):
> Your analysis is spot-on: Git is trying to find the directory that
> contains all th
Original message "Re: Git status delay" from "Adam Dinwoodie
(a...@dinwoodie.org)" sent 21. listopadu 2017, 11:27:28,
msgid:20171121102728.gm20...@dinwoodie.org (3557 bytes):
> Your analysis is spot-on: Git is trying to find the directory that
> contains all th
On Saturday 18 November 2017 at 09:13 pm +, Richard H Lee wrote:
> I have an issue with git where it hangs for 10 to 20 seconds on several
> commands, including "git status". For me this is reproducible on a fresh
> install of Cygwin x64 in Windows 7.
>
> I g
Greetings, Richard H Lee!
> I have an issue with git where it hangs for 10 to 20 seconds on several
> commands, including "git status". For me this is reproducible on a fresh
> install of Cygwin x64 in Windows 7.
> I get the feeling I am doing something wrong on my end a
On 11/20/2017 5:03 AM, Richard H Lee wrote:
> Can also confirm this on Windows 10.
>
I don't see an issue. Maybe your environment or some BLODA app.
--
cyg Simple
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: htt
Can also confirm this on Windows 10.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
I have an issue with git where it hangs for 10 to 20 seconds on several
commands, including "git status". For me this is reproducible on a fresh
install of Cygwin x64 in Windows 7.
I get the feeling I am doing something wrong on my end as "git status"
is a very commonly
Nvm. Just ran setup-x86 again and problem seems to have fixed itself. Wonder
what it was though.
saurabh
From: Saurabh T
Sent: Monday, June 26, 2017 8:54 AM
To: Cygwin
Subject: "man" failing all the time with status 3
n/t. Following is the error message:
man: command e
n/t. Following is the error message:
man: command exited with status 3: /usr/libexec/man-db/zsoelim |
/usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e
UTF-8 | tbl | nroff -mandoc -Tascii
I just upgraded cygwin and have (uname -a):
CYGWIN_NT-10.0-WOW tacuki 2.8.0
FYI: after the latest cygwin update to git v 2.12.3, this is no longer
a problem.
Setting an alias like "st = status -uno" works as expected. Many
thanks to the maintainer.
On Mon, May 15, 2017 at 8:54 AM, David Dombrowsky
<6thstreetra...@gmail.com> wrote:
> FYI: after the l
On Mon, Mar 27, 2017 at 9:24 AM, cyg Simple wrote:
>> st is also a prefix of "stash". Maybe it does not like aliases
>> that are prefixes of other commands?
Without the entry in the config file, `git st` results in the expected
git: 'st' is not a git command. See 'git --help'.
It's possible th
On 3/27/2017 8:23 AM, Eliot Moss wrote:
> On 3/27/2017 8:17 AM, David Dombrowsky wrote:
>> I'm not sure how to debug this one. I have a ~/.gitconfig that sets up
>> an alias for "git status" using the simple rule:
>>
>> [alias]
>> st = status
&g
On 3/27/2017 8:17 AM, David Dombrowsky wrote:
I'm not sure how to debug this one. I have a ~/.gitconfig that sets up
an alias for "git status" using the simple rule:
[alias]
st = status
Yet, something is failing when I run it from the command line:
$ git st
[nothing happen
I'm not sure how to debug this one. I have a ~/.gitconfig that sets up
an alias for "git status" using the simple rule:
[alias]
st = status
Yet, something is failing when I run it from the command line:
$ git st
[nothing happens]
$ git status
On branch 3.3-dev-davidd
Your
On Oct 21 12:50, Qian Hong wrote:
> Update:
>
> The script exit status issue is fixed in the Wine side in Wine Staging
> 1.7.53, patch commited as
> https://github.com/wine-compholio/wine-staging/commit/be51f622f7ed5a4f558bc54743314b310727ac4d
>
> (OT of OT: In WineConf
Update:
The script exit status issue is fixed in the Wine side in Wine Staging
1.7.53, patch commited as
https://github.com/wine-compholio/wine-staging/commit/be51f622f7ed5a4f558bc54743314b310727ac4d
(OT of OT: In WineConf2015, upstream WineHQ formally announced Wine
Staging become parts of
On Sep 8 01:13, Qian Hong wrote:
> Hi Corinna,
>
> Thanks again for the quick reply.
>
> On Mon, Sep 7, 2015 at 8:28 PM, Corinna Vinschen wrote:
> > The terminate_thread_frees_stack flag is set to false for XP/2003 and to
> > true for any newer OS. I guess this is a double-free because Wine's
>
Hi Corinna,
Thanks again for the quick reply.
On Mon, Sep 7, 2015 at 8:28 PM, Corinna Vinschen
wrote:
> Guys, no offense meant, but I'd really appreciate if you could peruse
> and refer to the original upstream Cygwin repo at
>
> https://sourceware.org/git/?p=newlib-cygwin.git
>
> This is what w
On Sep 7 19:02, Qian Hong wrote:
> Hi Corinna,
>
> Sorry for delay, our progress on this issue is slow.
>
> Many thanks for your great information, it does help us became closer
> to the reason.
>
> On Thu, Sep 3, 2015 at 6:55 PM, Corinna Vinschen
> wrote:
> > Comparing the straces, two intere
Hi Corinna,
Sorry for delay, our progress on this issue is slow.
Many thanks for your great information, it does help us became closer
to the reason.
On Thu, Sep 3, 2015 at 6:55 PM, Corinna Vinschen
wrote:
> Comparing the straces, two interesting facts are conspicuous:
> - After the forked scri
in32 error 6
After that, the pty master thread exits in both cases and then, for
some invisible reason, the "bad" process exits immediately, even
though it's not really finished:
170 2755070 [main] script 25 cygthread::terminate_thread: thread 'ptymf',
id 0x3
g statements are for the first hit point since I found
different status in the first hit point for different script.exe exit
status.
>From my test, whenever script.exe forwards the exit status correctly
(returns 5), oexitcode in pinfo::maybe_set_exit_code_from_windows is
set to 0x8000500; whene
On 5/8/2014 17:43, JonY wrote:
> On 5/8/2014 17:20, Rainer Emrich wrote:
>> I try to bootstrap gcc-4.9.0 for cygwin 64-bit, but this fails in adalib.
>> AFAIS upstream are still some patches missing which are in the gcc-4.8.2-3
>> source.
>>
>> Does anybody k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi JonY,
please CC me on answers, I'm not supscribed to the list.
The real question, is anybody working on getting these patches accepted
upstream?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird
On 5/8/2014 17:20, Rainer Emrich wrote:
> I try to bootstrap gcc-4.9.0 for cygwin 64-bit, but this fails in adalib.
> AFAIS upstream are still some patches missing which are in the gcc-4.8.2-3
> source.
>
> Does anybody knows the status for these patches?
>
I am working on t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I try to bootstrap gcc-4.9.0 for cygwin 64-bit, but this fails in adalib.
AFAIS upstream are still some patches missing which are in the gcc-4.8.2-3
source.
Does anybody knows the status for these patches?
-BEGIN PGP SIGNATURE-
Version
> Henry S Thompson writes:
> Anibal Morales writes:
>> I don't have a lot of free time but I miss my Xemacs. If I can make
>> a difference I would like to volunteer and help release this
>> package but I am a total cygwin package noob.
> Unfortunately it isn't (just) a
Anibal Morales writes:
> I don't have a lot of free time but I miss my Xemacs. If I can make
> a difference I would like to volunteer and help release this
> package but I am a total cygwin package noob.
Unfortunately it isn't (just) a packaging matter. Getting xemacs to
compile for 64-bit c
I don't have a lot of free time but I miss my Xemacs. If I can make a
difference I would like to volunteer and help release this package but I am
a total cygwin package noob.
er. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: SVNserve: PID 1216: 'SVNserve'
service stopped, exit status: 1.
Anything on this would be greatly appreciated.
Thanks,
Karthik Durairaja
On Wed, Mar 20, 2013 at 02:32:09AM -1000, Antonio Querubin wrote:
>On Tue, 19 Mar 2013, Christopher Faylor wrote:
>
>> http://cygwin.com/ is now available.
>
>Would it be too much to ask that the server be dual-stacked and given an
>IPv6 address? :)
It has been requested but apparently it isn't a
On Tue, 19 Mar 2013, Christopher Faylor wrote:
http://cygwin.com/ is now available.
Would it be too much to ask that the server be dual-stacked and given an
IPv6 address? :)
Antonio Querubin
e-mail: t...@lavanauts.org
xmpp: antonioqueru...@gmail.com
--
Problem reports: http://cygwi
http://cygwin.com/ is now available.
If anyone notices any problems please report them to the overseers
mailing list.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
On Tue, Mar 19, 2013 at 03:43:22PM -0400, David T-G wrote:
>Christopher (and everyone else) --
>
>...and then Christopher Faylor said...
>%
>% As you can see, email seems to be working on the new system.
>%
>% The old sourceware was a hodge podge of hand-built files installed in
>% nonstandard lo
Christopher (and everyone else) --
...and then Christopher Faylor said...
%
% As you can see, email seems to be working on the new system.
%
% The old sourceware was a hodge podge of hand-built files installed in
% nonstandard locations. I changed that on the new sourceware. It now
[snip]
Tha
As you can see, email seems to be working on the new system.
The old sourceware was a hodge podge of hand-built files installed in
nonstandard locations. I changed that on the new sourceware. It now
uses semi-official rpms for most of everything. I spent most of the day
yesterday chasing down p
Warren Young writes:
> I never have run the SQLite tests.
I see, thanks for letting me know. That adds another unknown in that
investigation, unfortunately.
> At this point, I'm about to give up on it and ship an updated version
> of my latetst test packages. That is, with FTS and such features
On 3/1/2013 08:11, Achim Gratz wrote:
how'd you work around the reams of errors in compiling the
testfixture (if you had to do anything)?
I never have run the SQLite tests.
The reason I brought it up is that it could possibly provide a
counterargument against the "svn + bdb breaks" report.
Hi Warren,
Warren Young etr-usa.com> writes:
> 4. Profit!
Still not sure about that... If I check out the 3.7.15.2 version and
just configure / make, I'll get a seemingly working sqlite3.exe, but
I can't compile the testfixture. How do you configure the build on
Cygwin and how'd you work aroun
Warren Young writes:
> Quoting that page: "They are contained in the same source tree as the
> SQLite core..." That means the Fossil repository, not the "amalgam"
> the Cygwin packages are built from.
Yes, I see that now.
> Steps:
[…]
What I've been missing is that by allowing Javascript on the
On 2/11/2013 15:00, Achim Gratz wrote:
Warren Young writes:
https://www.sqlite.org/testing.html
That doesn't seem tell me where to download the testsuite
Quoting that page: "They are contained in the same source tree as the
SQLite core..." That means the Fossil repository, not the "amalgam
On 11/02/13 21:51, Warren Young wrote:
As I saw it, I released some test builds, they caused a new problem,
I'm not sure you introduced a new problem - Subversion's 'bdb' tests
were locking up on both the .13 and .15 builds. Achim thought that this
might be to do with the version of BerkeleyD
Warren Young writes:
> https://www.sqlite.org/testing.html
That doesn't seem tell me where to download the testsuite and it's
definitely not in the tarball that Cygwin builds from. Is it in the
"canonical sources" somewhere, perhaps? And how to access those? Sorry
if that's obvious to you…
Re
On 2/11/2013 14:23, Achim Gratz wrote:
Warren Young writes:
From my perspective, though, I have a new problem, which is scraping
together enough free time to set up the SQLite test suite on a machine
here and set it to grinding, so I can exonerate the recent .15.1
build.
That's the second ti
Hi Warren,
Warren Young writes:
> From my perspective, though, I have a new problem, which is scraping
> together enough free time to set up the SQLite test suite on a machine
> here and set it to grinding, so I can exonerate the recent .15.1
> build.
That's the second time I hear you talking abo
On 2/5/2013 12:51, Achim Gratz wrote:
SQLite implements a
retry-on-failure, complete with exponentially increasing backoff times.
Thanks for the investigative reporting. :)
From my perspective, though, I have a new problem, which is scraping
together enough free time to set up the SQLite test
Yaakov (Cygwin/X) writes:
> So you're saying that it is more important for Cygwin's sqlite3 to work
> with a Windows program than it is for it to work properly with other
> Cygwin libraries and programs? That doesn't sound very pragmatic to me.
> Software built for Cygwin should _always_ follow *N
On 8/16/2012 12:41 AM, Achim Gratz wrote:
> $ sqlite3
> SQLite version 3.7.13 2012-06-11 02:05:22
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> CREATE TEMP TABLE two (id INTEGER NOT NULL, name CHAR(64) NOT NULL );
> Error: unable to open database file
> sql
realivlty quickly. I have set the AUTOSSH_DEBUG to yes but I am not
making heads or tails of the error
My main issue is that I keep getting ssh exited with error status 255;
restarting ssh
I have been using http://linux.die.net/man/1/autossh for most of my
info and I have been searching the
On Aug 31 10:59, Terris Linenbach wrote:
> Here is a scenario that involves Cygwin Perl only.
>
> I have a need for multiple Cygwin instances on the same box mainly due
> to DLL bases and CPAN modules. I've already read through the endless
> threads about both topics so there's no need to mention
Here is a scenario that involves Cygwin Perl only.
I have a need for multiple Cygwin instances on the same box mainly due
to DLL bases and CPAN modules. I've already read through the endless
threads about both topics so there's no need to mention them. I have
good reasons to do what I'm doing.
Ad
> Software built for Cygwin should _always_ follow *NIX behaviour.
>
> Yaakov
Amen!
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
> Sometimes I don't understand the antagonism towards interop with native
> Windows programs that don't do anything unusual and do things by the
> (Windows) book. It seems like it defeats the point of the project
> if that goes too far. What's wrong with being pragmatic sometimes?
There is n
Greetings, Corinna Vinschen!
> A "mand" mount option sounds like a really interesting idea, together
> with the special group permission settings as described in the Linux
> fcntl(2) man page. Maybe we can even relax that by making the "mand"
> option the default setting, so the correct file perm
On Aug 16 13:51, Warren Young wrote:
> On 8/16/2012 6:26 AM, Corinna Vinschen wrote:
> >On Aug 16 06:01, Warren Young wrote:
> >>Advisory locking only works when all players cooperate. We can't
> >>assume that on Windows, unless we set up an insular Cygwin ghetto.
> >
> >So, are you saying that Cy
Greetings, Warren Young!
> What are Fred's options?
Use commandline capabilities provided by TortoiseSVN.
> Option 1: Download the native Windows Subversion port. Sensible, but it
> means you have to use a crippled shell.
There's no such thing as "crippled shell" involved. Crippled knowledg
On 8/16/2012 7:08 PM, Yaakov (Cygwin/X) wrote:
> So you're saying that it is more important for Cygwin's sqlite3 to work
> with a Windows program than it is for it to work properly with other
> Cygwin libraries and programs? That doesn't sound very pragmatic to me.
> Software built for Cygwin shou
On Thu, 2012-08-16 at 21:31 +, James Johnston wrote:
> I was just about to start writing a similar message to this, but you did it
> for me very perfectly! What's the point of Cygwin if it can't play nice
> with other Windows programs on the system?
The "point" of Cygwin is clearly stated on
On 8/17/2012 02:22, Warren Young wrote:
> On 8/16/2012 10:34 AM, Brian Wilson wrote:
>>
>> Corina
>
> Corinna.
>
>> is correct, Cygwin is supposed to be a Posix compliant environment
>
> It's also supposed to interoperate with native Windows programs.
>
That's fine when it works, but that is n
> -Original Message-
> Sent: Thursday, August 16, 2012 18:22
> To: Cygwin-L
> Subject: Re: Promote sqlite 3.7.13-1 from test status?
>
> On 8/16/2012 10:34 AM, Brian Wilson wrote:
> > is correct, Cygwin is supposed to be a Posix compliant environment
&g
On 8/16/2012 6:26 AM, Corinna Vinschen wrote:
On Aug 16 06:01, Warren Young wrote:
Advisory locking only works when all players cooperate. We can't
assume that on Windows, unless we set up an insular Cygwin ghetto.
So, are you saying that Cygwin should use mandatory file locking?
Of course
On 8/16/2012 10:34 AM, Brian Wilson wrote:
Corina
Corinna.
is correct, Cygwin is supposed to be a Posix compliant environment
It's also supposed to interoperate with native Windows programs.
If you want to use Windoze tools, why are you using Cygwin?
First, instant 100 point credibilit
On 8/16/2012 9:34 AM, Brian Wilson wrote:
> Corina is correct, Cygwin is supposed to be a Posix compliant environment so
> the SQLite package should follow the Posix standard as the default
> behavior. If you want to use Windoze tools, why are you using Cygwin? If
> you really must, why not se
1 - 100 of 393 matches
Mail list logo
