On 09/15/2014 01:31 PM, Assaf Gordon wrote:
I've encountered a compilation error when compiling gnulib with TCC ( Tiny C
Compiler, http://bellard.org/tcc/ ):
it seems the "#include_next" is not working properly, but "m4/include_next.m4"
does not detect it.
Tested with TCC version 0.9.26 from t
Hello,
I've encountered a compilation error when compiling gnulib with TCC ( Tiny C
Compiler, http://bellard.org/tcc/ ):
it seems the "#include_next" is not working properly, but "m4/include_next.m4"
does not detect it.
Tested with TCC version 0.9.26 from the standard debian/stable package.
T
On 09/15/2014 07:11 AM, Pádraig Brady wrote:
Did you forget to git add m4/qsort_r.m4 ?
Oops, yes I did. Thanks for catching that. I added it as per attached.
>From 41473cf94a0e9eef96870b76eed9070f87d0c01a Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Mon, 15 Sep 2014 08:59:18 -0700
Subj
> Pushed with the "C" guards also on the extern variables,
> since both extern functions and variables are subject
> to C++ linkage.
Thanks!
Werner
Did you forget to git add m4/qsort_r.m4 ?
On 09/15/2014 08:25 AM, Werner LEMBERG wrote:
>
> Ping ping ping ping ping :-)
>
> Paul had some questions that I wasn't able to answer, cf.
>
> http://lists.gnu.org/archive/html/bug-gnulib/2014-02/msg00042.html
>
> However, this shouldn't be a hindrance to apply my small bug fix, so
> please
> Pushed your fix at:
> http://git.sv.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=b8e2c7f
Thanks!
Johannes
Ping ping ping ping ping :-)
Paul had some questions that I wasn't able to answer, cf.
http://lists.gnu.org/archive/html/bug-gnulib/2014-02/msg00042.html
However, this shouldn't be a hindrance to apply my small bug fix, so
please...
Werner
=