On Friday, May 23, 2025 at 09:04:11 AM EDT, Aurélien Couderc via Cygwin
wrote:
On Tue, May 13, 2025 at 9:07 PM Brian Inglis via Cygwin
wrote:
>
>> No one else is reporting any such problems, so it is your environment, with
>> your
>> network share, that is now having issues.
>
>I think no on
On Fri, 23 May 2025 at 14:47, Mark Liam Brown via Cygwin wrote:
> What is the official procedure to uninstall Cygwin properly? Just
> deleting C:\cygwin64 from Explorer yields lots of "malformed ACL
> warnings", and the registry still contains traces of Cygwin64
Uninstallation instructions are in
On Fri, 23 May 2025, Yuyi Wang wrote:
> On Fri, 23 May 2025, Jeremy Drake wrote:
> > Maybe. MSYS2 doesn't generally advise to rebase on x86_64, but I think
> > Cygwin does as part of its setup/postinstall hooks. As a hack, I was able
> > to work around this by setting the "dynamicbase" flag on t
On Fri, May 23, 2025 at 7:47 AM Mark Liam Brown wrote:
> What is the official procedure to uninstall Cygwin properly? Just
> deleting C:\cygwin64 from Explorer yields lots of "malformed ACL
> warnings", and the registry still contains traces of Cygwin64
If the malformed ACLs bother you, reset own
Greetings!
What is the official procedure to uninstall Cygwin properly? Just
deleting C:\cygwin64 from Explorer yields lots of "malformed ACL
warnings", and the registry still contains traces of Cygwin64
(We're not trying to quit using Cygwin, just want a clean way to
uninstall Cygwin and install
Thanks.
Just downloaded all the documents (the easy part), now comes the reading.
art
On 5/23/2025 6:40 AM, Jon Turney wrote:
On 23/05/2025 14:30, skidmarks via Cygwin wrote:
[...]
Thanks!
g++ -shared -flinker-output=dyn -o slip.dll *.o
ran with not errors.
Is there any documentation ava
On 23/05/2025 14:30, skidmarks via Cygwin wrote:
[...]
Thanks!
g++ -shared -flinker-output=dyn -o slip.dll *.o
ran with not errors.
Is there any documentation available on cygwin specific issues?
This seems like a question that I should be able to answer on my
own.
Indeed. We do ask people
> On 2025-05-22 12:37, Arthur Schwarz via Cygwin wrote:
> > I can't figure this one out.
> >
> > > clear;g++ -flinker-output=dyn -o slip.dll *.o
> >
> > generates:
> >
> >
/usr/lib/gcc/x86_64-pc-cygwin/12/../../../../x86_64-pc-cygwin/bin/ld:
/usr/lib/
> > gcc/x86_64-pc-cygwin/12/../../../../li
On Tue, May 13, 2025 at 9:07 PM Brian Inglis via Cygwin
wrote:
>
> On 2025-05-13 10:32, Aurélien Couderc via Cygwin wrote:
> > On Tue, May 13, 2025 at 5:41 PM Brian Inglis via Cygwin wrote:
> >> On 2025-05-13 02:33, Aurélien Couderc via Cygwin wrote:
> >>> On Mon, May 12, 2025 at 7:43 PM Brian Ing
On Fri, 23 May 2025, Jeremy Drake wrote:
> Maybe. MSYS2 doesn't generally advise to rebase on x86_64, but I think
> Cygwin does as part of its setup/postinstall hooks. As a hack, I was able
> to work around this by setting the "dynamicbase" flag on the dlls (it's a
> long story about why this hel
On 23/05/2025 02:59, Yuyi Wang via Cygwin wrote:
On Wed, 22 May 2025, Jeremy Drake wrote:
Ultimately, playing whack-a-mole in a 64-bit address space hoping that the
DLL will load in the same place as the parent is an exercise in futility,
especially in only 6 attempts.
Outside cygwin, rustc al
On Wed, 14 May 2025 at 10:35, Andrey Repin via Cygwin wrote:
>
> Greetings, Aurélien Couderc!
>
> > We always install Cygwin on a network drive, the CI runs as a separate
> > user and the IT department does not install Cygwin on the machines
> > itself. The test machines also do not have local use
12 matches
Mail list logo
