>On Saturday, January 6, 2024 at 01:45:09 AM PST, marco atzeri via Cygwin
> wrote:
>On Sat, 6 Jan 2024, 10:28 Brian Inglis via Cygwin, wrote:
>> On 2024-01-05 18:07, asebian via Cygwin wrote:
>> > package: liguile3.0_1
>> > version: 3.0.9-2
>> >
>> >
>> > Problem
>> >
>> >
> On Monday, June 26, 2023 at 04:36:30 PM PDT, David Karr via Cygwin
> wrote:
> m seeing a problem with someone else's Cygwin setup, sort of similar to a
> problem I asked about a couple of weeks ago, in that it's a problem with
> the same user, but seemingly a completely different problem.
> Ok, well, we managed to resolve this, but I don't understand why what we
> did would fix this.
> In system environment variables in Windows, they added "c:\cygwin64\bin" to
> the end of the PATH. That fixes the problem. That just doesn't make any
> sense to me. In a Cygwin shell, "/usr/bin" is
Hello Cygwin-
I just wanted to double-check my understanding that binding
an abstract socket (a NULL-prefixed filename) is not currently
supported on Cygwin. I think there used to be some sort
of emulation of abstract sockets, but, that's not true anymore,
right?
With the sample program below,
On Thu, Jun 01, 2023 at 07:51:55AM +0200, Marco Atzeri via Cygwin wrote:
> Hi Mike,
> download the source package.
> You can use setup to install it or going directly to one of the mirror like
>
> https://mirrors.kernel.org/sourceware/cygwin/x86_64/release/guile3.0/
>
> All the patches and the
On Saturday, May 13, 2023 at 11:40:01 PM PDT, Marco Atzeri via Cygwin-announce
via Cygwin wrote:
> Version 3.0.9-2 of
> guile3.0
> libguile3.0-devel
> libguile3.0_1
> have been uploaded for cygwin.
Hello Marco and Cygwin:
Where can I find the source patches that Cygwin uses for
On Tue, Oct 04, 2022 at 08:06:00PM +0200, Hannes M�ller wrote:
> Hi Guile-Maintainer,
> Hi Marco Atzeri,
>
> with e.g. guile 3.0.8-1 I noticed serveral problems.
>
> Most important one is not working readline support. You may check in
> guile via e.g.:
> (begin (use-modules (ice-9
Hello Cygwin-
I was reading the webpage "Building and Using DLLs".
That page suggests looking at mingw.org for more information.
mingw.org is no more. I don't know when or if it will return.
Thanks,
Michael
--
Problem reports: https://cygwin.com/problems.html
FAQ:
Hi-
Is it possible use Cygwin to run an autotools 'configure' script but have the
compiler be MSVC?
Thanks,
Michael
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info:
On Sun, May 12, 2019 at 08:22:36PM +0200, Agner Fog wrote:
> I have noticed that the gcc and clang compilers have defined the
> preprocessing macro __unix__, but not __WINDOWS__, _WIN32, or _WIN64 when
> compiling a windows executable.
>
> Why is this?
As I understand it, when using the cygwin
Hello good people,
This isn't a question so much as a random musing...
From what I understand, Cygwin works by translating POSIX-like calls
into Windows API. Or, to be more specific, the version of newlib that
Cygwin provides links to Windows-provided dlls that make Windows API
calls.
And
On Sun, Feb 24, 2019 at 10:18:58AM +0100, Corinna Vinschen wrote:
> On Feb 23 22:58, Mike Gran via cygwin wrote:
> > Hi-
> >
> > There is an unusual behaviour with setitimer/getitimer and I'm not
> > sure if it is a bug or not.
> >
> > Basically
Hi-
There is an unusual behaviour with setitimer/getitimer and I'm not
sure if it is a bug or not.
Basically, if I call setitimer to set an SIGALRM, and then call
getitimer *after* the alarm goes off, I rather expect the time I
receive from getitimer should be {tv_sec = 0, tv_usec = 0}, but, in
13 matches
Mail list logo
