Re: Autoconf distributions and xz dependency

s the trick. Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49-711-685-63607 <>___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf

Re: autoconf-2.68b released [beta]

small obstacle on the path to get autoconf installed. Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49-711-685-63607 <>___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailm

Re: autoconf-2.68b released [beta]

en if the "bad" versions would be used? Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49-711-685-63607 <> signature.asc Description: OpenPGP digital signature ___ Autoconf maili

Re: detecting windows

The problem of detecting MS Windows with autoconf is much deeper than not having a macro for it. You simply cannot run autoconf on MS Windows, as it requires other tools that are not available on Windows, so there is no macro to detect it. Or are you talking of Cygwin? Olaf -- Dr. rer. nat. Olaf Le

Re: detecting windows

Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49-711-685-63607 <>___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf

Re: acx_mpi and ac_lang_push

hese than the old A(C)X_MPI macro, as they are more reliable on unusual architectures. I think that they will also solve your problem. Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49-

Re: Request for inclusion [was: Re: Autoconf MPI macros]

from the one used for non-MPI files, as the compiler options used by Automake will be generated for the non-MPI compiler and might not work on the MPI-compiler. For example, on an IBM machine, this would cause trouble: configure CXX=g++ MPICXX=xlc_r Olaf -- Dr. rer. nat. Olaf Lenz Institut für C

Re: Request for inclusion [was: Re: Autoconf MPI macros]

I precisely because of the issues with the macro. Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49-711-685-63607 <>___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf

Re: Request for inclusion [was: Re: Autoconf MPI macros]

#x27;t want to compile *all* his code using the MPI compiler, but only some files. However, I have no clear idea why someone would want to do that... Does anybody here have an application for the old macros? If nobody has an idea, then we can as well deprecate the macro. Olaf -- Dr. rer.

Request for inclusion [was: Re: Autoconf MPI macros]

documentation of the older macro AX_MPI from here: https://github.com/olenz/autoconf-archive For reference, I have attached the new macros as well as the modified ax_mpi.m4 to this mailing. Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49-711

Re: Autoconf MPI macros

ap macro. I believe that it might be useful to people that want to use libtool and build shared libraries. One might consider the macro for inclusion to the autoconf macro archive. Cheers Olaf -- Dr. rer. nat. Olaf Lenz Institut für Computerphysik, Pfaffenwaldring 27, D-70569 Stuttgart Phone: +49

Autoconf MPI macros

ly, the MPI macro uses the standard macro AC_PROG_CC to find the compiler, and directly sets CC to a working MPI version. I propose to include these macros into the autoconf macro archive, and to extend the docs of AX_MPI to point to these macros. Greetings Olaf -- Dr. rer. nat. Olaf Lenz Institut

Re: Paralizing configure

ernatives worked there. > Extensible light-weight shells like 'rc' and 'es' > (http://en.wikipedia.org/wiki/Es_shell) can serve as an example. No, they can't, because they are not installed on unusual platforms by default. Sorry to be so much against these suggestion

Re: AW: MPI recognition

On 12/22/2010 06:40 PM, Carsten Heinrici wrote: > If a project requires a specialized tool chain, I would consider it wrong to > just silently fall back to something different as required. Well, the point is that our project doesn't require MPI, but it profits from it. If MPI is not available, y

Re: MPI recognition

Hi Ralf, Erik! On 12/22/2010 07:44 AM, Ralf Wildenhues wrote: > One problem with the above is that the settings 'gcc' and 'cc' will fail > to be correct MPI compilers, as they likely won't link in the MPI > library. Nowadays this doesn't happen so often any more but on some > systems it is good t

Re: MPI recognition

Hello again! On 12/21/2010 03:16 PM, Olaf Lenz wrote: > The problem seems to be that AC_PROG_CC doesn't work when using it in > a conditional, is that right? Is there any simple way to do what I > want? After some trial and error I have found a solution for my problem that is very

MPI recognition

characteristics and only afterwards finds the MPI compiler. If the MPI compiler understands completely different options than the standard compiler, this leads to massive problems. Best regards Olaf Lenz References: [1] http://espressomd.org [2] http://www.gnu.org/software/autoconf-ar

MPI and cross compilation

dd a macro that allows to introduce the old behaviour! Best regards, and keep up the good work, Olaf Lenz References: [1] http://espressowiki.mpip-mainz.mpg.de/wiki/index.php/Main_Page [2] http://de.wikipedia.org/wiki/Message_Passing_Interface -BEGIN PGP SIGNATURE- Version: Gn

C++ and AC_C_INLINE for small projects

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! I'm not an autoconf expert, so please excuse any novice errors. I'm working on AIX with the C++ compiler xlC 6. Because I have read the thread "Using AC_C_INLINE blows up C++ tests" in June, I've already updated autoconf to version 2.57b, so the