On 4/27/25 14:59, Jeremy Drake wrote:
On Sun, 27 Apr 2025, Jeremy Drake via Cygwin wrote:
On Sun, 27 Apr 2025, David Christensen via Cygwin wrote:
The procedure entry point cygfuse_report could not be
located in the dynamic link library C:\cygwin64\sshfs.exe.
-> OK
Does sshfs.exe have any ex
On Sun, 27 Apr 2025, Jeremy Drake via Cygwin wrote:
> On Sun, 27 Apr 2025, David Christensen via Cygwin wrote:
>
> > The procedure entry point cygfuse_report could not be
> > located in the dynamic link library C:\cygwin64\sshfs.exe.
> > -> OK
>
> Does sshfs.exe have any exports? Should it?
>
> (
I was asked an interesting question on a github issue about rust
backtraces: is there an API in Cygwin to get a list of loaded modules? I
know the info is there in the dlls list, but I don't see an API to get at
it.
The question was in regards to whether rust should be using toolhelp32 on
Cygwin
On Sun, 27 Apr 2025, David Christensen via Cygwin wrote:
> The procedure entry point cygfuse_report could not be
> located in the dynamic link library C:\cygwin64\sshfs.exe.
> -> OK
Does sshfs.exe have any exports? Should it?
(It is legal for an exe to have exports, and for a DLL to reference t
On 4/26/25 12:51, Brian Inglis via Cygwin wrote:
$ gendef - /usr/bin/cygfuse-3.2.dll
or
$ gendef /usr/bin/cygfuse-3.2.dll
I thought I had uinstalled WinFsp, but I noted that C:\Program Files
(x86)\WinFSP was non-empty. So, I ran winfsp-2.0.23075.msi and told it
to uninstall WinFsp. sshfs
> Cygwin provides source packages python3{,6,7,8,9,12} and binary releases:
>
> 3.6.{13-{1,2},15-1}
> 3.7.{10-{1,2},12-1}
> 3.8.{10,12,16}-1
> 3.9.{10,16,18}-1
> 3.12.{8-2,9-1}
>
> as of a couple of hours ago.
It does, but that's very easy to miss (I did).
The "python3" package is available in ve
On 2025-04-27 03:49, Lee via Cygwin wrote:
On Sun, Apr 27, 2025 at 4:52 AM Kevin Schnitzius via Cygwin
wrote:
On Sunday, April 27, 2025 at 04:20:23 AM EDT, Lee via Cygwin
wrote:
On Sat, Apr 26, 2025 at 10:38 PM Keith Thompson wrote:
I see that Cygwin only supports Python 3.9.16 (or 3.9.
On Sun, Apr 27, 2025 at 4:52 AM Kevin Schnitzius via Cygwin
wrote:
>
> On Sunday, April 27, 2025 at 04:20:23 AM EDT, Lee via Cygwin
> wrote:
>
> > On Sat, Apr 26, 2025 at 10:38 PM Keith Thompson wrote:
> >>
> >> I see that Cygwin only supports Python 3.9.16 (or 3.9.18 as a test
> >> version), w
On Sunday, April 27, 2025 at 04:20:23 AM EDT, Lee via Cygwin
wrote:
> On Sat, Apr 26, 2025 at 10:38 PM Keith Thompson wrote:
>>
>> I see that Cygwin only supports Python 3.9.16 (or 3.9.18 as a test
>> version), which is a couple of years old.
>
>$ python3 --version
>Python 3.12.9
That's eithe
On Sat, Apr 26, 2025 at 10:38 PM Keith Thompson wrote:
>
> I see that Cygwin only supports Python 3.9.16 (or 3.9.18 as a test
> version), which is a couple of years old.
$ python3 --version
Python 3.12.9
$ uname -a
CYGWIN_NT-10.0-19045 i3668 3.6.0-1.x86_64 2025-03-18 17:01 UTC x86_64 Cygwin
Lee
Hi Roland,
On 4/25/2025 11:16 AM, Roland Mainz via Cygwin wrote:
[...]
FYI I updated
http://svn.nrubsig.org/svn/people/gisburn/code/sparsefiles/lssparse.c
to pass the Solaris/Illumos "cstyle" rules, e.g. the source now
conforms UNIX C formatting rules (no functional changes, this was just
to fo
11 matches
Mail list logo
