Re: How to force using a module in Gnulib? (expl() on OpenBSD)

[Assaf Gordon]

Hello,

On 04/15/2014 05:20 AM, Pádraig Brady wrote:
> On 04/15/2014 12:54 AM, Assaf Gordon wrote:
> > It seems "expl()" is broken on OpenBSD5.4.
>
> You can set an override var for the configure run,
<...>
> However, since you have a simple enough test
> it seems it would be better to incorporate that to
> the gnulib check, so that all can benefit.

Attached is my attempt at detecting buggy expl() in the "expl.m4" file.

The test runs correctly in multiple environments, and sets a variable (gl_cv_func_expl_buggy) to 
"yes" or "no" .

However, I do not know how to overturn the gnulib detection of the native expl (see the 
"TODO" comment in the patch) - so it's a no-op at the moment.

While this test works in its current form, there might be some portability 
issues (since it uses 'fabs', 'exp' and 'expl') and those might require 
additional headers or libraries or special declarations.

The tests runs correctly on:
  Debian 7, x86_64, gcc 4.7.2
  CentOS, x84_64, gcc 4.4.7
  FreeBSD 10, x86_64, clang 3.3
  OpenBSD 5.4, X84_64, gcc 4.2.1
  Hurd, i386, gcc 4.8.2
  DilOS 1.3.5 (akin to SunOS 5.11), gcc 4.7.3

In OpenBSD it is set to "yes" (indicating buggy expl). In all others - "no".

buggy_expl_m4_2014_04_15.patch
Description: Text Data