On 2025-03-31 12:49, Corinna Vinschen via Cygwin wrote:
On Mar 31 12:35, Brian Inglis via Cygwin wrote:
On 2025-03-29 13:08, Alejandro Colomar wrote:
On Sat, Mar 29, 2025 at 07:45:27PM +0100, Alejandro Colomar wrote:
Hi Bruno,
Oops, s/Bruno/Brian/ :)
On Sat, Mar 29, 2025 at 12:28:52PM -0
On Mar 31 12:35, Brian Inglis via Cygwin wrote:
> On 2025-03-29 13:08, Alejandro Colomar wrote:
> > On Sat, Mar 29, 2025 at 07:45:27PM +0100, Alejandro Colomar wrote:
> > > Hi Bruno,
> >
> > Oops, s/Bruno/Brian/ :)
> >
> > >
> > > On Sat, Mar 29, 2025 at 12:28:52PM -0600, Brian Inglis wrote:
>
On 2025-03-29 13:08, Alejandro Colomar wrote:
On Sat, Mar 29, 2025 at 07:45:27PM +0100, Alejandro Colomar wrote:
Hi Bruno,
Oops, s/Bruno/Brian/ :)
On Sat, Mar 29, 2025 at 12:28:52PM -0600, Brian Inglis wrote:
On 2025-03-29 05:43, Bruno Haible via Cygwin wrote:
Regarding what acl_extended
On 3/31/25 12:26, Corinna Vinschen wrote:
ls(1) always potentially shows a past state anyway.
Sure, but traditionally (and I'm talking about 7th edition Unix) a
single output line of 'ls' corresponded to a state obtained atomically
from the file system. I realize we can't always do that nowad
On Mar 31 12:12, Paul Eggert via Cygwin wrote:
> On 3/31/25 11:27, Pádraig Brady wrote:
> > The file could be deleted at any time.
> > We're just suppressing errors in the edge case it's deleted
>
> More generally, though, the file could be renamed and another put in its
> place, which means that
On 3/31/25 11:27, Pádraig Brady wrote:
The file could be deleted at any time.
We're just suppressing errors in the edge case it's deleted
More generally, though, the file could be renamed and another put in its
place, which means that an attacker could cause 'ls' to generate a line
that does
On 31/03/2025 17:32, Paul Eggert wrote:
On 2025-03-30 07:26, Pádraig Brady wrote:
On 30/03/2025 13:50, Corinna Vinschen wrote:
In terms of coreutils, I think either ls(1) gobble_file() or
file_has_aclinfo_cache() should still handle ENOENT from
file_has_aclinfo() and not print any error message
On Monday, March 31, 2025 at 04:28:16 AM EDT, Corinna Vinschen via Cygwin
wrote:
> On Mar 31 11:25, Duncan Roe via Cygwin wrote:
> > On Sun, Mar 30, 2025 at 05:32:44PM +0800, cygwin wrote:
> > > Code to reproduce:
> > >
> > >
> > > #include
> > > #include
> > > #include
> > > #include
> > >
>
On 2025-03-30 07:26, Pádraig Brady wrote:
On 30/03/2025 13:50, Corinna Vinschen wrote:
In terms of coreutils, I think either ls(1) gobble_file() or
file_has_aclinfo_cache() should still handle ENOENT from
file_has_aclinfo() and not print any error message. After all, due to
the preconditions fo
On Mon, 31 Mar 2025 at 11:38, Mark Geisert via Cygwin wrote:
>
> On 3/31/2025 1:26 AM, Cedric Blancher via Cygwin wrote:
> > On Tue, 11 Mar 2025 at 11:14, Corinna Vinschen via Cygwin
> > wrote:
> >>
> >> On Mar 10 21:51, Brian Inglis via Cygwin wrote:
> >>> On 2025-03-10 14:01, Corinna Vinschen v
On 2025-03-31 03:37, Mark Geisert via Cygwin wrote:
On 3/31/2025 1:26 AM, Cedric Blancher via Cygwin wrote:
On Tue, 11 Mar 2025 at 11:14, Corinna Vinschen via Cygwin wrote:
On Mar 10 21:51, Brian Inglis via Cygwin wrote:
On 2025-03-10 14:01, Corinna Vinschen via Cygwin wrote:
On Mar 7 15:43,
That does not help. Looks like that is too old.
running build_ext
generating cffi module
'build/temp.cygwin-3.6.0-x86_64-cpython-312/_padding.c'
creating build/temp.cygwin-3.6.0-x86_64-cpython-312
generating cffi module
'build/temp.cygwin-3.6.0-x86_64-cpython-312/_openss
Hi,
a colleague and I are facing a problem with unhandled exceptions in our C++
programs in Cygwin.
The C++ standard guarantees, that std::terminate() shall be called for thrown
exceptions, that are not caught [0].
Unfortunately for C++ applications compiled for Cygwin64 running on recent
Windo
Hello,
at the moment, I ported qtbase from Qt6 and I contributed patches to
the friends at Qt codereview.
Hopefully, many of these patches have been accepted and they should be
available into the next version 6.9, because I don't think that they
will be backported to 6.8.x.
There are still few thin
Hi Jörg,
On Mar 31 09:00, Joerg Markus (LBC) via Cygwin wrote:
> Hi,
>
> a colleague and I are facing a problem with unhandled exceptions in
> our C++ programs in Cygwin. The C++ standard guarantees, that
> std::terminate() shall be called for thrown exceptions, that are not
> caught [0]. Unfor
On 3/31/2025 1:26 AM, Cedric Blancher via Cygwin wrote:
On Tue, 11 Mar 2025 at 11:14, Corinna Vinschen via Cygwin
wrote:
On Mar 10 21:51, Brian Inglis via Cygwin wrote:
On 2025-03-10 14:01, Corinna Vinschen via Cygwin wrote:
On Mar 7 15:43, Cedric Blancher via Cygwin wrote:
On Fri, 7 Mar 2
On Mar 30 22:58, Jeremy Drake via Cygwin wrote:
> On Mon, 31 Mar 2025, Christoph Reiter via Cygwin wrote:
>
> > Starting with 3.6.0 when cmake calls into make/ninja/gcc there is a chance
> > of
> > that failing, for example like this:
> >
> > CMake Error: Generator: build tool execution failed, c
On Tue, 11 Mar 2025 at 11:14, Corinna Vinschen via Cygwin
wrote:
>
> On Mar 10 21:51, Brian Inglis via Cygwin wrote:
> > On 2025-03-10 14:01, Corinna Vinschen via Cygwin wrote:
> > > On Mar 7 15:43, Cedric Blancher via Cygwin wrote:
> > > > On Fri, 7 Mar 2025 at 13:24, Corinna Vinschen wrote:
> >
On Mar 31 09:14, Cedric Blancher via Cygwin wrote:
> On Sun, 15 Oct 2023 at 02:14, Mark Geisert via Cygwin
> wrote:
> >
> > Mark Geisert via Cygwin wrote:
> > >
> > >> Are there Qt6 - https://www.qt.io/product/qt6 - packages for Cygwin
> > >> available?
> > >
> > > Does setup.exe show it/them as
On Mar 31 11:25, Duncan Roe via Cygwin wrote:
> On Sun, Mar 30, 2025 at 05:32:44PM +0800, cygwin wrote:
> > Code to reproduce:
> >
> >
> > #include
> > #include
> > #include
> > #include
> >
> > int main() {
> > void* handle = dlopen("/usr/bin/cygwin1.dll", RTLD_LAZY | RTLD_LOCAL);
> >
On Sun, 15 Oct 2023 at 02:14, Mark Geisert via Cygwin wrote:
>
> Mark Geisert via Cygwin wrote:
> >
> >> Are there Qt6 - https://www.qt.io/product/qt6 - packages for Cygwin
> >> available?
> >
> > Does setup.exe show it/them as a choice? No? No they aren't available.
> > We could
> > use a ma
21 matches
Mail list logo
