Funny behavior from autoconf

2005-10-23 Thread Brian Lloyd
The following Makefile.am does not work as expected. This is a stripped down version of the complete makefile. It still shows the same problem as the complete file, which is more than twice as large. The way it works, one of either BOOST1_33, BOOST1_31, or BOOST1_28 will be defined. The am__ve

Re: AC_FOREACH public?

2005-10-23 Thread Ben Pfaff
Keith Marshall <[EMAIL PROTECTED]> writes: > But "Reply-to-All" is *not* the most appropriate solution -- > it's what I used here, so *you* can have *two* copies of this > message. Personally, I configure my mailreader to discard duplicates. -- Ben Pfaff email: [EMAIL PROTECTED] web: http://ben

[OT] reply-to (was: AC_FOREACH public?)

2005-10-23 Thread Allan Clark
Keith Marshall wrote: On Saturday 22 October 2005 10:08 am, Allan Clark wrote: You might want to consider switching to elm, mutt, or a Mozilla-based client (if you're a graphical guy); they have these features, and are fairly well-tested. I don't have any option to do this -- I am obli

Re: [Hubert Chan] Bug#332713: autoconf: checking for fork does not work for C++

2005-10-23 Thread Ben Pfaff
Paul Eggert <[EMAIL PROTECTED]> writes: > CVS autoconf does this instead. I presume the AC_INCLUDES_DEFAULT > fixes the same problem in a different way? Yes, it does. I've applied the change to Debian's Autoconf package. Thanks for your help. -- "Then, I came to my senses, and slunk away, hop

Re: [Hubert Chan] Bug#332713: autoconf: checking for fork does not work for C++

2005-10-23 Thread Paul Eggert
CVS autoconf does this instead. I presume the AC_INCLUDES_DEFAULT fixes the same problem in a different way? AC_DEFUN([_AC_FUNC_FORK], [AC_CACHE_CHECK(for working fork, ac_cv_func_fork_works, [AC_RUN_IFELSE( [AC_LANG_PROGRAM([AC_INCLUDES_DEFAULT], [ /* By Ruediger Ku