> Le 18 mai 2019 à 20:21, Paul Eggert a écrit :
>
> Akim Demaille wrote:
>
>> How about this?
>
> Looks OK to me; thanks.
Installed. Thanks!
Mohammad Akhlaghi wrote:
> > It is be possible to search libraries using AC_RUN_IFELSE instead of
> > AC_LINK_IFELSE, and add -rpath options as needed. The AC_LIB_LINKFLAGS
> > macro from gnulib does this. It appears that you used the stock Autoconf
> > macro, which does not do this.
>
> You are r
On 5/18/19 1:58 AM, Bruno Haible wrote:
It is be possible to search libraries using AC_RUN_IFELSE instead of
AC_LINK_IFELSE, and add -rpath options as needed. The AC_LIB_LINKFLAGS
macro from gnulib does this. It appears that you used the stock Autoconf
macro, which does not do this.
You are rig
While it is hard to make a decision for all packages altogether, specific
packages should have an easy way to set their preferred default.
2019-05-18 Bruno Haible
threadlib: Provide an easy way to avoid mingw's winpthreads library.
* m4/threadlib.m4 (gl_AVOID_WINPTHREAD): New
On 18.05.2019 16:07, Bruno Haible wrote:
> Opinions?
I don't use gnulib much, but as far as threads are concerned:
Applications can use Windows threading APIs, if they need limited threading
support and know exactly what they want, and if the developers know how to use
Windows API correctly.
Por
Akim Demaille wrote:
How about this?
Looks OK to me; thanks.
Hi,
What should be the default threading API used by the module 'threadlib'
(and thus also 'lock', 'rwlock', 'cond', etc.) on mingw. There are two choices:
--enable-threads=windows
does not need non-Microsoft DLLs.
--enable-threads=posix
links against winpthreads.dll.
(Whereas Ross Johnson
> > > > error: expected identifier or '(' before numeric constant
> > > > pthread_sigmask (int how, const sigset_t *new_mask, sigset_t *old_mask)
> > > > ^
I'm reproducing this error now, by compiling gettext-0.20.1 with
--enable-threads=windows.
Or, more simply, with a testdir:
./gnulib-tool
Hi Paul!
> Le 18 mai 2019 à 09:52, Paul Eggert a écrit :
>
> Akim Demaille wrote:
>> + };
>> \
>
> Thanks, that looks good except I don't see why some of the lines like the
> above have semicolons while others don't.
You
Akim Demaille wrote:
+ }; \
Thanks, that looks good except I don't see why some of the lines like the above
have semicolons while others don't.
Bruno made a bug report some time ago: make check failed for Bison on Solaris.
The problem was the use of $< in some non-implicit rules. This syntax-check
caught them.
See
http://lists.gnu.org/archive/html/bug-bison/2019-05/msg9.html
and
https://lists.gnu.org/archive/html/bison-patches/2019
11 matches
Mail list logo