-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Jeff Squyres on 3/16/2009 4:54 PM: > This mail could probably be considered a followup to this thread > introduced by Rolf Vandevaart from Sun back in Jan 2009: > > http://lists.gnu.org/archive/html/bug-autoconf/2009-01/msg00056.html
> - Or should there be a new AC_RESTRICT test that makes a solution for > both the C and C++ compilers? That's the goal for autoconf 2.64. > It seems that AC_C_RESTRICT can sometimes find "restrict" for the PGI C > compiler, but it can sometimes find "__restrict". Both of these values > work for the PGI C compiler, but only "__restrict" works for the PGI C++ > compiler. The reasons for AC's difference in answers appear to do with > the PGI C compiler installation and the version of the GCC/glibc > installed, distro/version, ...etc. I didn't delve too deeply to figure > out why this happened. See the thread starting here for more details: > > http://www.open-mpi.org/community/lists/users/2009/03/8402.php Thanks for the pointer. Can you please verify whether this test, recently added in autoconf.git, correctly detects that your situation is not yet accommodated? http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=ee55d77 It is the testsuite followup to the earlier patch: http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=aa30765 but that patch was indeed Sun specific. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm+3LMACgkQ84KuGfSFAYAvngCg1iIwD8jyLGqoTT4dClKWZrF2 2VcAoIQMXvtk4A5f/DwH3Udu1J/ysrqp =bl83 -----END PGP SIGNATURE-----
