Re: autoconf 2.63 fails a test

Hi Bob, * Bob Friesenhahn wrote on Wed, Sep 10, 2008 at 07:42:24PM CEST: > If autoconf 2.63 fails this test under Solaris 10 with GNU m4 1.4.11, is > it safe to use? > > 144: Input/OutputFAILED (base.at:303) Please send tests/testsuite.log. Thanks, Ralf ___

Re: Condition evaluation removed

Hello Giles, * Giles Anderson wrote on Thu, Sep 11, 2008 at 05:45:38PM CEST: > Is there a way to populate the file output from my '.in' file with only the > result of a condition evaluation not the condition itself? Yes. > So my dev.ini.in file looks like: > > > export [EMAIL PROTE

Re: default $(libdir) and bi-arch systems

Hello, * Bob Friesenhahn wrote on Wed, Sep 10, 2008 at 06:26:34PM CEST: > > Multilib support via libtool has been on the wish list for quite a while > but implementing it is either a Big Job for libtool, or for the build > environments which drive it. It seems to me that if libtool supports the

Re: AC_PATH_PROG: Using a variable for prog-to-check-for

Hi Harlan, * Harlan Stenn wrote on Sat, Sep 13, 2008 at 05:23:41AM CEST: > I wrote: > > > > PATH_NET_SNMP_CONFIG=whatever > > AC_PATH_PROG([PATH_NET_SNMP_CONFIG], [$PATH_NET_SNMP_CONFIG]) > > > > and that doesn't work (with autoconf 2.59). What doesn't work with it? It seems to work fine in

Re: make -s, how to make it quiet?

Hello Joakim, Thomas, * Joakim Tjernlund wrote on Sun, Sep 07, 2008 at 11:38:54PM CEST: > On Sun, 2008-09-07 at 10:23 -0400, Thomas Dickey wrote: > > On Sun, 7 Sep 2008, Joakim Tjernlund wrote: > > > > > So I see that out builds uses automake 1.4-p6, maybe that is too old? Yes, recent Automake v

Re: make -s, how to make it quiet?

* Joakim Tjernlund wrote on Sat, Sep 13, 2008 at 10:37:37AM CEST: > > > Anyhow, I am upgrading to newer automake but I get a ton of: > > > ecn_ss/ecn_ppp_bl/Makefile.am:52: pppd_LDADD must be set with `=' before > > > using `+=' > > > ne/ecn_ss/ecn_ppp_bl/Makefile.am:57: relayd_LDADD must be set w

Re: make -s, how to make it quiet?

Joakim, please quote only relevant parts of the message you reply to. Thanks. * Joakim Tjernlund wrote on Sat, Sep 13, 2008 at 11:40:46AM CEST: > > > > #! /bin/sh > > set -e > > LC_ALL=C > > export LC_ALL > > adds=adds.$$ > > inits=inits.$$ > > tmp=tmp.$$ > > for file in `find . -name Makefile.am

upgrading from Automake 1.4 (was: make -s, how to make it quiet?)

* Joakim Tjernlund wrote on Sat, Sep 13, 2008 at 12:12:10PM CEST: > Noticed i get a ton of theses too with automake 1.8: > ne/oa_uai_if/Makefile.am: object `up_oa_uai.$(OBJEXT)' created both with > libtool and without This is addressed here:

Re: [autoconf 2.63] 95 of 353 tests fail

Hello Howard, Thanks for the report. Please, if possible, do not start new threads for messages to the same topic. Thanks. * Howard Larson wrote on Wed, Sep 17, 2008 at 06:25:01PM CEST: > > Obviously something is broken. Need advice on next course of action; tear > down the entire system and

Re: [autoconf 2.63] 95 of 353 tests fail

* Eric Blake wrote on Thu, Sep 18, 2008 at 05:25:16AM CEST: > Please don't top-post. > > > I have performed a search for a conftest.obj file and it does not exist. As > > I mentioned in an earlier email, build of libtool failed to produce any .obj > > files. > > > > I have installed MinGW. Does

Re: Issue in autoconf with config.status generation

Hello Evan, * Evan Hunter wrote on Thu, Sep 18, 2008 at 05:20:08PM CEST: > > As I understand it, the 'config.status --recheck' command is supposed > re-run the configure script using all the same options as it was > originally run with. > The problem I'm finding is that the command-line options a

Re: Error while autoconf on Ubuntu

Hello Mahendra, * mahendra panpalia wrote on Wed, Sep 24, 2008 at 05:42:38AM CEST: > > Ubuntu system is giving error, when tried to do autoconf for generating > > scripts for configuration. > > (i run autoconf with configure.in file) > > > > errors are as below > > > > aclocal.m4:22: error: m4_def

Re: Error while autoconf on Ubuntu

* mahendra panpalia wrote on Wed, Sep 24, 2008 at 07:57:21AM CEST: > On Wed, Sep 24, 2008 at 6:41 AM, Ralf Wildenhues <[EMAIL PROTECTED]>wrote: > > * mahendra panpalia wrote on Wed, Sep 24, 2008 at 05:42:38AM CEST: > > > > > > > > aclocal

Re: Error while autoconf on Ubuntu

* Ralf Wildenhues wrote on Wed, Sep 24, 2008 at 08:06:44AM CEST: > * mahendra panpalia wrote on Wed, Sep 24, 2008 at 07:57:21AM CEST: > > On Wed, Sep 24, 2008 at 6:41 AM, Ralf Wildenhues <[EMAIL PROTECTED]>wrote: > > > * mahendra panpalia wrote on Wed, Sep 24,

Re: Error while autoconf on Ubuntu

Hello mahendra, Please do not top-post. Thanks. * mahendra panpalia wrote on Wed, Sep 24, 2008 at 08:20:18AM CEST: > On Wed, Sep 24, 2008 at 7:11 AM, Ralf Wildenhues wrote: > > > > > on your system? What is in line 22 (and around) of the file > > > > > ac

Re: how to install a bashcompletion file?

Hello Lorenzo, * Lorenzo Bettini wrote on Sat, Sep 27, 2008 at 04:04:07PM CEST: > > I'd like to install a bashcompletion file that comes in the tarball for > a GNU program I'm mantaining (source-highlight). The file should be > installed in an etc subdirectory that bashcompletion uses. Then

Re: sed on binary files

Hi Eric, * Eric Blake wrote on Thu, Oct 02, 2008 at 04:51:58AM CEST: > > Is there any portable way to process files that contain NUL bytes? tr? If you only need to compare for equality, then use cmp. > The Solaris man > pages mention that /usr/xpg4/bin/tr can handle NUL bytes, but not > /usr/b

Re: sed on binary files

* Eric Blake wrote on Thu, Oct 02, 2008 at 02:46:38PM CEST: > > I'll add a blurb to the autoconf manual on sed mentioning that it cannot > be used on binary files (although Posix already says that), Isn't that obvious? I mean, of all classic unix text-related tools, only very few operate on non-

Re: Can't open configure

Hello Braden, thanks for providing feedback! * Braden McDaniel wrote on Fri, Oct 03, 2008 at 09:17:42AM CEST: > On Tue, 2008-01-29 at 07:54 +0100, Ralf Wildenhues wrote: > > * Paulo J. Matos wrote on Mon, Jan 28, 2008 at 10:34:30PM CET: > > > After running: > > >

Re: Can't open configure

* Braden McDaniel wrote on Sun, Oct 05, 2008 at 07:23:40PM CEST: > On Sun, 2008-10-05 at 12:21 +0200, Ralf Wildenhues wrote: > > * Braden McDaniel wrote on Fri, Oct 03, 2008 at 09:17:42AM CEST: > > > $ autoreconf > > > acinclude.m4:6596: the serial nu

Re: Can't open configure

* Braden McDaniel wrote on Mon, Oct 06, 2008 at 03:29:46AM CEST: > On Sun, 2008-10-05 at 19:36 +0200, Ralf Wildenhues wrote: > > OK, the issue is that in the libltdl directory, aclocal.m4 is > > regenerated, and configure is a symlink that points to a read-only > > locatio

Re: [RFH] zsh shell function portability issue

* Paolo Bonzini wrote on Mon, Oct 13, 2008 at 11:59:22AM CEST: > You will remember the shell function portability issue in zsh... Yes; sigh. > Do you think that these functions: reindented to: ac_func_c_try_compile() { rm -f conftest.$ac_objext if { (ac_try="$ac_compile" ca

Re: Extracting configuration info from config.status

Hello Barry, * Barry Leslie wrote on Wed, Oct 15, 2008 at 05:57:01PM CEST: > It would be really useful if there was a configure option that would allow > you to point to another location and tell configure to get it's settings > from there. Yeah. I once ventured on a patch trying to let config.s

Libtool test failure with current master

bootstraping recent Libtool with current git Autoconf gives this failure: $ make check-local TESTSUITEFLAGS="-k config.lt -v -d -x" [...] ../../libtool/tests/early-libtool.at:216: $ACLOCAL -I m4 stderr: configure.ac:4: error: m4_divert_require: circular dependency of _AS_LINENO_PREPARE

Re: Autoconf Transforms

Hi Tom, * Tom Browder wrote on Tue, Oct 14, 2008 at 10:24:58PM CEST: > I am trying to use some raw shell commands in my 'configure.ac' file > and find that some constructs are not permitted without some care, > e.g., regex classes, where 's/[^0-9]//' becomes 's/^0-9//' unless one > doubles the squ

Re: Extracting configuration info from config.status

* Barry Leslie wrote on Thu, Oct 16, 2008 at 04:45:05PM CEST: > > My solution to this problem was to get the CC flags I wanted from the MySQL > MakeFile instead of trying to get them out of config.status. > > It is still a bit frustrating when you know all the data you need is in > config.status

Re: cache problem

Hello Markus, thanks for the reports. * Duft Markus wrote on Thu, Oct 16, 2008 at 03:46:51PM CEST: > > > > I just noticed, that when i enable a config.cache that is used by more > > than one package is problematic, when the first on checks for the build > > system type only, and the second for b

Re: [CFT] Shell functionization patch (if you don't know what that means, it's faster Autoconf and leaner configure scripts)

Hi Paolo, * Paolo Bonzini wrote on Thu, Oct 16, 2008 at 06:38:19PM CEST: > Also, the zsh issue has to be understood better (and could be a deal > breaker, though I don't think so). It basically means that you cannot call exit nor trap inside a shell function. Nor can you use $? at the start of a

Re: cache problem

* Duft Markus wrote on Fri, Oct 17, 2008 at 09:00:16AM CEST: > > I haven't been able to do so yet. Here's what I tried. Please modify > > the example so that it shows the failure (maybe it only needs different > > flags passed to configure?) > > Hehe, the problem occured when using the same cach

Re: [RFH] zsh shell function portability issue

* Paolo Bonzini wrote on Fri, Oct 17, 2008 at 09:14:20AM CEST: > > But the only arguments in the eval *when the eval appears in shell > functions* (I don't care about user code relying on _AC_DO, because it > will appear outside functions) are: > > $ac_cpp > $ac_compile > $ac_link > ./con

Re: [CFT] Shell functionization patch (if you don't know what that means, it's faster Autoconf and leaner configure scripts)

* Paolo Bonzini wrote on Fri, Oct 17, 2008 at 09:18:30AM CEST: > > > [...] you will want to put something like > > $as_debug > > > > at the start of each function (either being empty, or 'set -x'), for > > ksh. > > Do you want to put that in AS_REQUIRE_SHELL_FN? It's fine by me. I'd love to.

Re: cache problem

* Duft Markus wrote on Fri, Oct 17, 2008 at 09:26:44AM CEST: > It happens when: > > *) configuring automake 1.9.6 with ./configure --cache-file=../cache > *) bootstrapping libtool 1.5.24 or 26 with autoconf 2.59 > *) configuring libtool with the same cache: ./configure > --cache-file=../cache

Re: config.status --recheck

Hello Lorenzo, Eric, * Eric Blake wrote on Thu, Oct 23, 2008 at 05:09:19AM CEST: > > I also recall that Ralf Wildenhues checked in a fix that lets newer > automake insert additional .PHONY designations to .m4 files, so that make > coupled with autoreconf can proceed after a renamed .

Re: config.status --recheck

Hi Peter, * Peter Johansson wrote on Thu, Oct 23, 2008 at 04:57:35PM CEST: > Ralf Wildenhues wrote: >> * Eric Blake wrote on Thu, Oct 23, 2008 at 05:09:19AM CEST: >> >>> I also recall that Ralf Wildenhues checked in a fix that lets newer >>> automake insert

Re: autconf, configure & purify...

Hello Antony, * Boggis, Antony wrote on Fri, Oct 24, 2008 at 01:47:43AM CEST: > After much googling and no answers (and least, none I can understand) > I am resorting to querying the wisdom of this list (and excuse me if > cc'ing is frowned upon). Yeah, it's usually nicer to choose one list only;

Re: autconf, configure & purify...

Hi Eric, * Eric Blake wrote on Fri, Oct 24, 2008 at 01:16:53PM CEST: > According to Ralf Wildenhues on 10/24/2008 12:39 AM: > >> AC_CHECK_PROGS(PURIFY,purify purify2002) > >> > >> if test -z $PURIFY; then > > > > This however does need quoti

Re: use of AC_TRY_EVAL broken

* Eric Blake wrote on Fri, Oct 24, 2008 at 04:15:34AM CEST: > According to Bruno Haible on 10/23/2008 5:09 PM: > > There is a need for autoconf macros to compile and execute programs that > > they have created with AC_LANG_CONFTEST > > 1) without having to build up the compile or link command by

Re: autconf, configure & purify...

Hi Andreas, * Andreas Schwab wrote on Fri, Oct 24, 2008 at 11:19:09PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > - many vendor shells complain about 'test -z' without further argument: > > A POSIX-compliant test won't, and returns zero.

Re: autconf, configure & purify...

* Boggis, Antony wrote on Fri, Oct 24, 2008 at 11:28:28PM CEST: > > >Remains the question: does anything in your Makefile.am files use > >$(PURIFY)? > > No. > > There is a "if PURIFY" though... Well, Automake conditionals only work if you declare them using AM_CONDITIONAL in configure.ac; see <

Re: use of AC_TRY_EVAL broken

Hi Bruno, * Bruno Haible wrote on Fri, Oct 24, 2008 at 11:28:06PM CEST: > Ralf Wildenhues wrote: > > a suggestion for a new name: AC_EVAL_IFELSE. > > There's actually two cases to consider, if you want to make it easy to use > for the developer: > - the case o

Re: configure.lineno and config.status

Hi Eric, * Eric Blake wrote on Mon, Oct 27, 2008 at 07:22:37PM CET: > So, even though config.status has code in place to check for a broken > lineno, the check passes rather than fails, because it doesn't contain > instances of $LINENO any more; also, error messages printed on behalf > of config.s

Re: Define a complete rule via autoconf (quoting issue, AC_SUBST)

Hi Daniel, * Daniel Leidert wrote on Mon, Oct 27, 2008 at 11:04:34PM CET: > > I want to place a rule in several Makefiles. So I thought about putting > > @DESKTOP_DATA_RULE@ > > into every Makefile.am and define the rule via configure.ac. However, I > can't get it to work. Should be possible w

Re: Disable the present-but-cannot-be-compiled header warning?

Hi Eric, all, * Eric Blake wrote on Fri, Oct 31, 2008 at 05:06:33AM CET: > --- a/doc/autoconf.texi > +++ b/doc/autoconf.texi > @@ -5803,9 +5803,20 @@ Generic Headers > header file is available, consider using @code{AC_CHECK_HEADERS} > instead. > > [EMAIL PROTECTED] is a series of include dire

Re: Define a complete rule via autoconf (quoting issue, AC_SUBST)

Hello Daniel, re. the part that has not been addressed yet: * Daniel Leidert wrote on Sat, Nov 01, 2008 at 11:21:11PM CET: > > schemas_DATA = `echo "$(schemas_in_files)" | sed > 's/.schemas.in$$//;$(transform);s/$$/.schemas/'` > > Running the install target fails, because the installation rule

Re: Setting different debug and release locations

Hello Dan, * Dan Smithers wrote on Fri, Oct 31, 2008 at 01:11:15PM CET: > I have several applications that want to use the same home-rolled > library. Currently each application and library is a separate source > tree with its own autotools tree. > > I've been adding > CFLAGS and LDFLAGS to the c

Re: Add tr to common programs

Hello Eric, * Eric Blake wrote on Tue, Nov 04, 2008 at 02:21:05PM CET: > A bug report on the autoconf list recently reported that autoconf has been > producing configure files for several years now with a dependence on > tr[1], I didn't see it, where exactly would that be? > 2008-11-04 Eric Bla

Re: some numbers

Hi Paolo, * Paolo Bonzini wrote on Thu, Nov 06, 2008 at 11:51:19AM CET: > On GNU Smalltalk with M4 1.4.8: > > 2.61 10.0sec 1037568 bytes > 2.62 7.0sec 1057356 bytes > 2.63 7.5sec 1058211 bytes > 2.63+funcs 6.0sec 742044 bytes > git 4.6sec

Re: [PATCH 6/6] use print or printf or cat as $ECHO

Hello, * Eric Blake wrote on Mon, Nov 10, 2008 at 05:30:27PM CET: > Paolo Bonzini gnu.org> writes: > > > 1) these tests do cost a few subshells (which can be as expensive as a > > fork on bash, even if the executed command is a builtin). In the > > attached patch I conditionalized it on ${TMOUT

Re: [PATCH 6/6] use print or printf or cat as $ECHO

* Eric Blake wrote on Mon, Nov 10, 2008 at 09:50:39PM CET: > Ralf Wildenhues gmx.de> writes: > > > Where did you get the idea that TMOUT is a reliable way to detect ksh? > > You're right - the existence of TMOUT is not a reliable way to detect > ksh, and I had b

Re: Problems with ./configure

Hello Michel, * debutant wrote on Thu, Oct 30, 2008 at 11:38:18AM CET: > I just moved from mandriva 2006 to mandriva 2009-1 and I try to installed > on the last distribution programs that I installed without problems on the > former > one. > > Now when I use ./configure I have the following mess

Re: testsuite --list: wrap keywords?

* Eric Blake wrote on Wed, Nov 12, 2008 at 03:46:53AM CET: > According to Ralf Wildenhues on 11/11/2008 3:02 PM: > > tests/testsuite --list > > > > produces some long lines due to long keyword lists. Should they be > > wrapped? > > Do you know a quic

Re: cache problem

Hello Markus, sorry for the long delay. * Duft Markus wrote on Mon, Oct 20, 2008 at 08:48:48AM CEST: > > * Duft Markus wrote on Fri, Oct 17, 2008 at 09:26:44AM CEST: > > > It happens when: > > > > > > *) configuring automake 1.9.6 with ./configure > --cache-file=../cache > > > *) bootstrapping

Re: distclean vs. clean order dependency

Hi Eric, old old thread: * Eric Blake wrote on Sat, Apr 05, 2008 at 02:56:43PM CEST: > I was trying to silence warnings during 'automake -Wall' for autoconf. > However, I can't figure out what to do for this last warning, that > autoconf is overriding automake's definition of distclean-generic.

Re: verbose testsuite output contains 1M newlines

* Eric Blake wrote on Sun, Nov 23, 2008 at 03:56:49PM CET: > According to Ralf Wildenhues on 11/23/2008 6:23 AM: > > running > > make check-local TESTSUITEFLAGS=-v > > > > on M4 (git master) produces lots of output on GNU/Linux/bash. > Hmm, this particular test

Re: Detailed structure checks

Hi Peter, * Peter O'Gorman wrote on Sat, Nov 29, 2008 at 07:22:06AM CET: > Tim Post wrote: > > > > Thank you. I'm not sure how I could have missed that. Autoconf is > > probably one of the best documented projects available .. the manual is > > so massive that sometimes its easy to get lost :) >

Re: Checking for sed... spurrious output ?

Hello Michel, thanks for the report. * Michel Briand wrote on Tue, Dec 02, 2008 at 02:17:07AM CET: > my configure outputs this: > > checking for a sed that does not truncate output... ./configure: line 3764: > echo: write error: Broken pipe > /bin/sed > > Is it intended to have this broken pip

Re: help2man missing

* Patrick Welche wrote on Thu, Dec 04, 2008 at 10:20:50AM CET: > On Wed, Nov 12, 2008 at 07:55:28PM +0100, Ralf Wildenhues wrote: > > * Bob Friesenhahn wrote on Wed, Nov 12, 2008 at 06:33:12PM CET: > > > While building libtool HEAD today, I encountered this problem: > >

Re: Recursive directory Installation

Hello Jeremiah, this would rather be an Automake question than an Autoconf one. * Jeremiah Benham wrote on Mon, Dec 08, 2008 at 10:49:17PM CET: > I want to recursively install everything that exists within a directory. > I originally had it as this in an install hook in Makefile.am: > > install-

Re: Getting data from a nested configure script?

Hi Benoit, * Benoit Sigoure wrote on Tue, Dec 09, 2008 at 11:11:17AM CET: > Say that I use AC_CONFIG_SUBDIRS([foo]), is there a standard way for > the parent configure to retrieve some information from foo's > configure? The standard way to extract information computed by configure is using confi

Re: m4_version_prereq

Hi Paolo, all, * Paolo Bonzini wrote on Thu, Dec 18, 2008 at 06:09:44PM CET: > > BTW, I'm still planning to look at the zsh bug reported by Ralf > a while ago. Which one was that? > After this, I think we're ready for Autoconf 2.63a, aren't we? :-) I still need to fix Autotest signal handling

Re: LIBEXT

Hello Werner, * Werner LEMBERG wrote on Sun, Jan 04, 2009 at 09:39:14AM CET: > > What about adding a test to find out the extension of (static) > libraries? Having a LIBEXT variable would be quite helpful. You can use Libtool to find this out. If that is overkill for you, you can alternati

Re: Cannot set correct path for libltdl.so. How to run configure?

Hello Gary, this is a Libtool question. It belongs on neither autoconf nor the autoconf-patches list. * Gary Yang wrote on Tue, Jan 06, 2009 at 10:41:48PM CET: > > I got errors when I do the cross compile for powerpc. Below are the > error messages. It looks for /usr/lib/libltdl.so instead of >

Re: Can't repeat build.

Hello Dan, * Dan Smithers wrote on Wed, Jan 21, 2009 at 03:19:06PM CET: > I have configure.ac in the top directories and Makefile.am in all source > directories and top directories. > > I use a sequence > > autoreconf --install > cd build > ../configure > make > > Sometime this works fine. On

Re: Can't repeat build.

Hello Dan, * Dan Smithers wrote on Thu, Jan 22, 2009 at 11:35:32AM CET: > >> Sometime this works fine. On other occasions I get an error > >> > >> automake-1.10: no Automake input file found for > >> `activation_analyser/src/Makefile.in' > >> automake-1.10: no input file among supplied arguments.

Re: Can't repeat build.

* Dan Smithers wrote on Fri, Jan 23, 2009 at 03:22:18PM CET: > bin_PROGRAM=exec > exec_SOURCES=exec.c > exec_LDADD=$(top_builddir)/../libname/src/.libs -lname > >>> Please replace this line with > >>> exec_LDADD=$(top_builddir)/../libname/src/libname.la > >>> > >>> but I do wonder:

Re: Hello all autoconf users - AC_PROG_FC question

Hello Sébastien, and welcome, * Sébastien Le Roux wrote on Sat, Jan 31, 2009 at 11:32:36PM CET: > > Thus I have a question concerning the behavior of the 'configuration' > process, I would like to understand how does the AC_PROG_FC check for > any Fortran compiler. If you use AC_PROG_FC without

Re: autotools usage question

Hello Oguz, * Oguz Yarimtepe wrote on Sat, Jan 31, 2009 at 10:21:44PM CET: > ./configure --host="sh4-linux" --prefix="/st710x/usr/local/efls" > --x-includes="/opt/STM/STLinux-2.2/devkit/sh4/target/usr/X11R7/include" > --x-libraries="/opt/STM/STLinux-2.2/devkit/sh4/target/usr/X11R7/lib" > > make

Re: Hello all autoconf users - AC_PROG_FC question

[ resending to the list only, as some mail server thinks I am sending inappropriate content to Sébastien; apologies for dupes ] Hello Sébastien, and welcome, * Sébastien Le Roux wrote on Sat, Jan 31, 2009 at 11:32:36PM CET: > > Thus I have a question concerning the behavior of the 'configuratio

Re: Workaround for incorrect gcc exit code?

Hello Stephen, * Stephen P. Schaefer wrote on Fri, Jan 30, 2009 at 03:07:47AM CET: > I'm seeing the following in config.log; > > configure:8972: checking for setpcred > configure:9022: gcc -o conftest -O2 -march=i386 -mcpu=i686 -g -fpie > -I/usr/kerberos/include -I/usr/kerberos/include/gssapi -Wa

Re: Macro to give option to preprocessor depending on the compiler ?

Hello Sébastien, * Sébastien Le Roux wrote on Tue, Feb 03, 2009 at 07:59:11PM CET: > > I have prepared a 'configure.ac' which tests both for Fortran > compilers and MPI library. If configure is done using '--with-mpi' > option then the configure looks for MPI libs and if succeed ad the > option

Re: Macro to give option to preprocessor depending on the compiler ?

I should add that Sébastien's mail server does not accept mail from any of my accounts, so on-list communication is the only one that will work. Please stick to it. Everyone else, sorry for the noise. Cheers, Ralf ___ Autoconf mailing list Autoconf@gn

Re: marking a test in autotest as expected to fail

Hello Rikki, Eric, * Eric Blake wrote on Tue, Feb 10, 2009 at 01:58:43PM CET: > > AT_XFAIL_IF([AT_EXPR_RESPONSE_TEST_P([test.1], ['"i,j&i > According to Rikki McQueary on 2/9/2009 3:20 PM: > > > > My question is: Is this correct? And also in the output instead of the > > test passing with an o

Re: running tests when cross-compiling

Hello Vadim, * Vadim Zeitlin wrote on Wed, Feb 11, 2009 at 06:11:43PM CET: > Configure is smart enough to not try to run the tests when cross-compiling > which is usually, of course, the right thing to do. However in some > situations you can actually run the program even when cross-compiling: th

Re: Workaround for incorrect gcc exit code?

Hi Stephen, * Stephen P. Schaefer wrote on Mon, Feb 02, 2009 at 05:29:31PM CET: > > Thank you for suggesting config.site. I see that it is discussed in > Chapter 14 of the manual, although it doesn't appear in the index. Thanks, also for the macros to work around the bug (we might consider usi

Re: Library version thru autoconf ?

Hello Sébastien, Warren, all, > On Fri, 2009-02-13 at 11:09 -0700, Warren Young wrote: > > Sébastien Le Roux wrote: > > > > > > I wonder if there is a way (a macro ?) to obtain the version of a library. > > > > Maybe, but the Autoconf Way is to test for features, not versions. A couple of usefu

Re: wondering if this is acceptable

Hello Matt, * Matt Rice wrote on Thu, Feb 05, 2009 at 11:51:58AM CET: > ac_configure_args="$ac_configure_args foo=$ac_pwd" > AC_CONFIG_SUBDIRS(stuff) > > none of the build dir variants appeared to be set at the time. > it looks like adding things ac_configure_args is fairly common > but neither o

Re: CFLAGS is for the user in GNU

nk about this, for the Automake manual? The Ordering node seems to fit better with the context (the variables which are listed are not all user variables), and it links to the `User Variables' node, and is mostly discusses the quirks. Thanks, Ralf 2009-02-16 Ralf Wildenhues * doc/autom

Re: How to check the size of pthread_t?

Hello Vasil, * Vasil Dimov wrote on Fri, Feb 27, 2009 at 07:47:49AM CET: > > I am trying to create an autoconf script that does check the size of > pthread_t, > but I am experiencing some troubles in the way. > > To be precise, what I need is a macro like SIZEOF_PTHREAD_T, similar to > SIZEOF_L

Re: using atlocal variables in autotest macros

Hello John, * John Wohlbier wrote on Wed, Feb 25, 2009 at 08:03:00PM CET: > For the life of me I can't figure out how to use variables I've set in > atlocal.in in my macros defined in my *.at files. I think it must be due to > my lack of understanding of the m4 language, and maybe more specificall

Re: library search test fails, please help

Hello Alejandro, all, I'm late to the long thread this post started: * aaragon wrote on Sat, Feb 21, 2009 at 10:23:33PM CET: > I want to check for a particular static library that I created. > Thus, I put the following in the configure.ac file > > AC_CHECK_LIB([cpputils], [flip],,[AC_MSG_ERROR(l

Re: make distcheck

Hi Patrick, * Patrick Welche wrote on Mon, Mar 02, 2009 at 01:10:44PM CET: > Just a quick "Am I doing something silly?" N! > In a project, using autoconf 2.61, automake 1.10.1, libtool 1.5.26, > make distcheck succeeds. If I untar the created .tar.bz2 file, and > /path/to/untar/configure && make

Re: make distcheck

* Patrick Welche wrote on Mon, Mar 02, 2009 at 08:52:26PM CET: > > I thought that running make distcheck in the source directory should > fail? Not sure why you think that. distcheck does a build with build tree != source tree. But nothing in Automake prohibits packages from allowing both trees

Re: make distcheck

* Patrick Welche wrote on Tue, Mar 03, 2009 at 12:04:00AM CET: > On Mon, Mar 02, 2009 at 09:57:28PM +0100, Ralf Wildenhues wrote: > > Not sure if "srcdir" is a directory name here, but config.h should not > > be created in the source tree, but in the build tree, to faci

Re: documentation through doxygen stopped working

* aaragon wrote on Tue, Mar 03, 2009 at 06:54:35AM CET: > > aara...@~/Workspace/080427 cpputils$./autogen.sh > configure.ac:58: error: AC_SUBST: `DX_FLAG_[]DX_CURRENT_FEATURE' is not a > valid shell variable name > acinclude.m4:77: DX_REQUIRE_PROG is expanded from... > acinclude.m4:117: DX_ARG_AB

Re: using atlocal variables in autotest macros

* John Wohlbier wrote on Mon, Mar 02, 2009 at 04:51:27AM CET: > m4_define([AT_MPIRUN_PROGRAM], > [echo "$MPI_LIBS" > AS_IF([test -n "$MPI_LIBS"], >[AT_BANNER([executing mpirun -n $2 $1]) > AT_TESTED([$1]) > AT_SETUP([$1]) > AT_CHECK([mpirun -n $2 $1],[0],[ignore],[i

Re: documentation through doxygen stopped working

well. Please, I asked for a lot more information: > Ralf Wildenhues wrote: > > That smells of M4 overquoting somewhere. Find out what changed, the > > Autoconf version, or any third-party macro code, or configure.ac. > > In case of doubt, please post a small example to r

Re: using atlocal variables in autotest macros

* John Wohlbier wrote on Tue, Mar 03, 2009 at 05:13:17PM CET: > > I got the basic functionality to work with the following. > > m4_define([AT_MPIRUN_PROGRAM], > [AT_BANNER([executing mpirun -n $2 $1]) > AT_SETUP([$1]) > AT_CHECK([test -n "$MPI_LIBS" || exit 77]) > AT_TESTED([$1]) > AT_CHECK([

Re: using atlocal variables in autotest macros

* John Wohlbier wrote on Tue, Mar 03, 2009 at 09:09:09PM CET: > That seems like a reasonable suggestion. What I have a hard time seeing > though is how exactly I'd get that test to execute just once for serial, and > a test writer specified number of times with different numbers of processors > for

Re: Portably setting library search paths by passing -R or -rpath

Hello Frank, * Frank Lahm wrote on Thu, Mar 05, 2009 at 07:39:54PM CET: > 2009/3/5 Frank Lahm : > > In order to properly test and use the library at , we must pass > > -R or -Wl,-rpath= with LDFLAGS/CFLAGS on some (maybe > > all?) platforms. Neither of which is very portable, exactly. > I have

Re: recording flags specified to configure scripts

* Mike Frysinger wrote on Tue, Mar 10, 2009 at 08:01:49AM CET: > i like to record the flags used when running `./configure` to be shown when > running --version info with programs. Undocumented (so watch out when updating Autoconf), but: eval "$ac_configure_args" should provide you with what y

Re: recording flags specified to configure scripts

Hello Keith, * Keith Marshall wrote on Tue, Mar 10, 2009 at 11:49:12AM CET: > On Tuesday 10 March 2009 07:18:26 Ralf Wildenhues wrote: > > Undocumented (so watch out when updating Autoconf), but: > >   eval "$ac_configure_args" > > Didn't that get clobbered,

bootstrapping Autoconf with 2.63

Hello bug-autoconf readers, when I try to run Cygwin's /usr/bin/autoconf (2.63) on the git Autoconf tree, I get approximately \infty many instances of this warning: | /usr/bin/m4:configure.ac:23: Warning: m4_eval: bad expression (bad input): + _m4_bmatch_( That's not good. git Autoconf should

Re: about documentation of AC_CHECK_HEADERS

Hello Vincent, thanks for the report. * Vincent Torri wrote on Sat, Mar 14, 2009 at 05:51:21PM CET: > more precisely, if foo.h exists and bar.h does not: > > 1) with: > > AC_CHECK_HEADERS([foo.h bar.h], [have_headers="yes"], [have_headers="no"]) > > have_headers value is "no" > > 2) with: > > hav

Re: resync auto{make,m4te} perl modules?

Hi Eric, * Eric Blake wrote on Sat, Mar 14, 2009 at 11:17:40PM CET: > > Ralf's recent work on adding silent-rules to automake modified the > lib/Automake/ChannelDefs.pm file on branch je-silent. This file used to > by synchronized into autoconf's lib/Autom4te (module difference in the > package

Re: Portability problems of "Usual Tools" not described in manual

Hello, * Eric Blake wrote on Tue, Mar 17, 2009 at 03:43:32PM CET: > According to Russ Allbery on 3/12/2009 10:32 PM: > > 2. On HP-UX 11.23, regexp matching with expr does not allow multiple sub- > >expressions: > > > > bash-3.1$ expr 'Xfoo' : 'X\(f\(oo\)*\)$' > > expr: More than one

Re: OT: The autoconf-archive maintainer

Hello Allan, * Allan Caffee wrote on Wed, Mar 25, 2009 at 08:56:01PM CET: > Can someone please verify that the autoconf-archive maintainer address > is ? Yes, Peter maintains > http://autoconf-archive.cryp.to > I sent a patch series in almost a month and a half ago and still have > not recieved

Re: Bison and flex target

Hello Philip, * Philip Herron wrote on Fri, Apr 03, 2009 at 02:51:50PM CEST: > I am not sure if this is autoconf or automake. If you use Automake, then this is an Automake question. :-) > I see there is AC_PROG_YACC and AC_PROG_LEX to get the apropriate > programs for the configure.ac. But how

Re: AC_TRY_COMPILE() annoyances with 2.63b

Hello Mike, Eric, * Mike Frysinger wrote on Mon, Apr 06, 2009 at 03:16:53PM CEST: > --- a/lib/m4sugar/m4sh.m4 > +++ b/lib/m4sugar/m4sh.m4 > @@ -607,7 +607,7 @@ m4_define([_AS_IF], > ]) > m4_define([_AS_IF_ELSE], > [m4_ifvaln([$1], > -[else > +[else : >$1])]) > > m4_defun([AS_IF], I like

Re: AC_TRY_COMPILE() annoyances with 2.63b

* Eric Blake wrote on Tue, Apr 07, 2009 at 04:25:12AM CEST: > I'm also leaning towards omitting the else if $1 is provably blank, OK with me. > otherwise providing the : in case non-blank $1 ultimately expands to a > blank (unless someone finds a shell where 'if false ; then :; fi; echo $?' > fai

Re: AC_TRY_COMPILE() annoyances with 2.63b

* Ralf Wildenhues wrote on Tue, Apr 07, 2009 at 07:38:10AM CEST: > > But that isn't what you need here. There are situations in which you > cannot prove whether $1 is blank or not. In that case, we should add > both the ":\n" as well as $1. Actually, $1 can ju

  1   2   3   4   5   6   7   8   9   10   >