Re: [GNU Autoconf 2.69] OSX autotools: `aclocal.m4' not being output by `autom4te'

directories are on a FAT32 disk. Indeed, the Autotools configuration worked as expected with a copy of the source tree stored on an HFS disk. Is it expected behaviour that GNU Autotools are incompatible with some file systems natively supported by the OS? Cheers, Jeff. > On 21 Jun 2014, at 11

Re: openmpi: FTBFS: Compilation errors

ttp://lists.gnu.org/archive/html/bug-autoconf/2010-10/msg00016.html +AS_VAR_PUSHDEF([type_var], + m4_translit([[ompi_cv_f90_have_$1]], [*], [p])) # Determine Fortran datatype size. # First arg is type, 2nd arg is config var to define -- Jeff Squyres jsquy...@cisco.com For cor

Re: openmpi: FTBFS: Compilation errors

lready available here: https://svn.open-mpi.org/trac/ompi/ticket/2559 -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

Problems with AC 2.66 AC_CHECK_SIZEOF

tmp/bogus/ac266-install/bin/autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 $ - -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

AC_TYPE_INT8/16/32/64_T fail

The AC_TYPE_INT*_T macros worked for me with 2.64, but now they don't with 2.65. The AC_TYPE_UINT*_T macros still work. I have verified that reverting back to 2.64 does work for me. I don't have the output of make check to provide, but I do have the output from my config.log for my software w

Minor type in autoconf.texi

IRE([TESTB])[echo in C]]) AC_DEFUN([OUTER], [[echo in OUTER] -A -C]) +TESTA +TESTC]) OUTER @end example -- Jeff Squyres jsquy...@cisco.com

Minor buglet in config.log

. Thanks! -- Jeff Squyres Cisco Systems

Re: AC_C_RESTRICT

Lifting all such restrictions while still allowing to create mixed language code is pretty difficult in general (but would be nice to have!). Cheers, Ralf -- Jeff Squyres Cisco Systems

Re: AC_C_RESTRICT

onfig.log from the reporter and let's go from there. Thanks! -- Jeff Squyres Cisco Systems

Re: AC_C_RESTRICT

| defined(__cplusplus) #undef restrict #define restrict #endif It's definitely sub-optimal, but we're pretty sure it's safe. Would it be a tragedy to repeat the guts of the AC_C_RESTRICT test with the C++ compiler and then know what the two different values are? The value o

Re: AC_C_RESTRICT

lthough, perhaps confusingly, also discovered by a different Sun employee). I'll reply more on Ralf's post. -- Jeff Squyres Cisco Systems

AC_C_RESTRICT

if you're compiling in C or C++. - Or should there be a new AC_RESTRICT test that makes a solution for both the C and C++ compilers? - Or ...? (please reply all so that the others CC'ed on this post also see the followups; thanks!) -- Jeff Squyres Cisco Systems

re_compile_pattern change

In gettext-0.16.1 and findutils-4.2.29, the version of autoconf used was 2.61 and 2.60a respectively. gettext-0.14.5, findutils-4.2.27, tar-1.16.1, coreutils-5.96, diffutils-2.8.1, grep-2.5.1a, and inetutils-1.5 all used 2.60 or older. The reason I bring this up is that the outcome of re_compile_pa

netatalk bug

Got this while running configure: configure: WARNING: gssapi/gssapi_krb5.h: present but cannot be compiled configure: WARNING: gssapi/gssapi_krb5.h: check for missing prerequisite headers? configure: WARNING: gssapi/gssapi_krb5.h: proceeding with the preprocessor's result configure: WARNING: