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 <[email protected]> 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 > [email protected] > http://lists.einsteintoolkit.org/mailman/listinfo/users > > -- Erik Schnetter <[email protected]> http://www.perimeterinstitute.ca/personal/eschnetter/
_______________________________________________ Users mailing list [email protected] http://lists.einsteintoolkit.org/mailman/listinfo/users
