On Wed 01 Mar 2017 21:27, Thomas Klausner writes:
> $NetBSD: patch-lib_signal.in.h,v 1.1 2016/12/03 03:15:33 marino Exp $
>
> DragonFly support.
>
> --- lib/signal.in.h.orig 2016-06-29 09:12:27 UTC
> +++ lib/signal.in.h
> @@ -61,6 +61,7 @@
> #if (@GNULIB_PTHREAD_SIGMASK@ || defined GNULIB_P
On Wed 01 Mar 2017 21:28, Thomas Klausner writes:
> Another pkgsrc patch concerns itself with supporting older Darwin
> releases, attached. Can you please merge it?
> Thomas
>
> $NetBSD: patch-libguile_stime.c,v 1.1 2016/10/19 14:56:17 adam Exp $
>
> Fix building on Darwin.
>
> --- libguile/stim
On Wed 01 Mar 2017 21:29, Thomas Klausner writes:
> --- libguile/filesys.c.orig 2016-12-15 00:03:33.0 +
> +++ libguile/filesys.c
> @@ -1486,6 +1486,15 @@ SCM_DEFINE (scm_i_mkstemp, "mkstemp!", 1
>mode_bits = scm_i_mode_bits (mode);
> }
>
> +#ifdef __APPLE__
> + /* ht
On Fri 03 Mar 2017 15:32, Mike Gran writes:
> I also can replicate the Cygwin problem as originally described.
I understand that with the fix in 2.1.8, that things are working
correctly now; closing the report. Thanks for the sleuthing, szgyg and
Mike!
Andy
On Wed 01 Mar 2017 17:43, Andy Wingo writes:
> On Sun 19 Feb 2017 09:41, ilove zfs writes:
>
>> On macOS 10.11 and 10.12 building with Xcode 8, guile 2.1.7 fails to
>> compile with several errors saying "address argument to atomic
>> operation must be a pointer to _Atomic type." I
>> can avoid t
Found a bug in the modifications you made. Sorry for not catching this
before it got included into the Guile 2.1.8 release.
When constructing the candidates for the guile executable
(_guile_candidates), the version numbers essentially get reverse. This
is not noticeable for 2.2 since 2.2 reversed
On Tue 14 Mar 2017 15:25, Freja Nordsiek writes:
> Found a bug in the modifications you made. Sorry for not catching this
> before it got included into the Guile 2.1.8 release.
Thank you! Applied. Note that in the gnu coding standards you need an
entry in the commit log for every file you modi
Andy Wingo writes:
> On Mon 13 Mar 2017 19:10, taylanbayi...@gmail.com (Taylan Ulrich
> "Bayırlı/Kammer") writes:
>
>> If I do binary I/O, the following situations are possible:
>>
>> 1. I'm guaranteed to get any possible bytes that happen to form a valid
>>BOM at the start of the stream as-
On Tue 14 Mar 2017 16:03, taylanbayi...@gmail.com (Taylan Ulrich
"Bayırlı/Kammer") writes:
> Andy Wingo writes:
>
>> On Mon 13 Mar 2017 19:10, taylanbayi...@gmail.com (Taylan Ulrich
>> "Bayırlı/Kammer") writes:
>>
>>> If I do binary I/O, the following situations are possible:
>>>
>>> 1. I'm gua