[Users] Checking for strdup

[Erik Schnetter]

Michael

Wow -- your email remained unanswered for a long time. Apologies.

This problem has been solved in the development branch; in short, the
test CCTK_CHECK_HAS_PROTOTYPE
was rewritten. This should probably be backported to the release branch.

-erik


On Fri, Jun 12, 2015 at 2:10 AM, Michael Clark <michael.clark at gatech.edu>
wrote:

> With intel-13.2.146 compiler, I've observed that the configure check for
> strdup (lib/make/configure.in line 494, using CCTK_CHECK_HAS_PROTOTYPE)
> can fail despite strdup being defined in string.h.
>
> The test for this seems to rely on compilation of "int strdup()" failing
> if this prototype exists, but on a machine I'm using currently, the intel
> compiler only generates a *warning*, not an *error*, and considers
> compilation to have "succeeded."  Since compilation "succeeded", the test
> fails, even though strdup's prototype is available.
>
> This can be worked around by adding -diag-error 147 (the id code for this
> diagnostic) to CFLAGS.  Is this what end-users should be expected to do?
>
> -Michael Clark
>
> _______________________________________________
> Users mailing list
> Users at einsteintoolkit.org
> http://lists.einsteintoolkit.org/mailman/listinfo/users
>
>


-- 
Erik Schnetter <schnetter at cct.lsu.edu>
http://www.perimeterinstitute.ca/personal/eschnetter/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/users/attachments/20150626/4b34767a/attachment.html