Re: silly question about editor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to aaragon on 3/4/2009 9:46 PM: > Hi, > > Maybe this is a silly question, but I found that the macros that I write in > the configure.ac sometimes fail depending on the spaces and tabs that I use. > Is there a way to automatically indent the

Re: problem with ifelse

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Vincent Torri on 3/4/2009 1:34 PM: > > dnl use: ECORE_CHECK_MODULE(Foo, default-enabled[, dependancy[, > ACTION-IF-FOUND[, ACTION-IF-NOT-FOUND]]]) > AC_DEFUN([ECORE_CHECK_MODULE], > [ > pushdef([UP], translit([$1], [a-z], [A-Z]))dnl > pus

Re: problem with ifelse

Hey, thanks for all the typo. Unfortunately, we want to support old versions of the autotools, so i will have to check that the m4 macro are not too recent. The problem is with ifelse([$2], [no] *) Whatever the 2nd parameter is ("yes" or "no"), it seems that the test always fails. I t

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

Hello all, in our package (netatalk) we consume Berkeley-DB. We have a configure option --with-bdb that can take a 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. As the correct way to give that option that m

Re: silly question about editor

I guess what I mean is that if you put an space between the MACRO and the starting parenthesis, the macro fails and it's not like the error will point you to the line in the configure.ac file. Besides it's quite hard to keep track of all closing parenthesis and to get the quotation right. So there

Re: silly question about editor

Alejandro, Dig out the M4 manual and read the first chapter. M4 is much like the C preprocessor in many ways. In C, if you put a space between a macro name and the opening paren in the definition, the preprocessor won't recognize the macro as a function-like macro either. How do you handle th

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

2009/3/5 Frank Lahm : > Hello all, > > in our package (netatalk) we consume Berkeley-DB. > We have a configure option --with-bdb that can take a > > 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. Well, a l

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

using input files in autotest

I'm in the process of switching our build system over to using autotest. We have several tests that use input files that we keep in their test directory. When testsuite runs it apparently creates subdirectories in which it runs, and then removes them on success. Is there a way to tell the testsuite

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

2009/3/5 Ralf Wildenhues : >> I have two stages where I must be able to compile, link and run code >> using the lib: >> A. conftest code at configure time >> B. the build product at runtime (of course) >> >> B is working by means of autoconf/libtool. > > Correct. > >> A is giving me problems becaus

Re: using input files in autotest

Nevermind, I think I solved my own problem. In my macros I'll define a variable INPUTFILES that can be set on the ./testsuite command line, and if it's nonempty I'll do a cp "$at_dir/$INPUTFILE" "`pwd`" I'll set TESTSUITEFLAGS appropriately in the makefiles for the tests that have input files. j

Re: problem with ifelse

On Thu, 5 Mar 2009, Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Vincent Torri on 3/4/2009 1:34 PM: dnl use: ECORE_CHECK_MODULE(Foo, default-enabled[, dependancy[, ACTION-IF-FOUND[, ACTION-IF-NOT-FOUND]]]) AC_DEFUN([ECORE_CHECK_MODULE], [ pushdef([UP], transl

Re: problem with ifelse

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Vincent Torri on 3/5/2009 8:33 AM: > > Hey, > > thanks for all the typo. Unfortunately, we want to support old versions > of the autotools, so i will have to check that the m4 macro are not too > recent. Most of the m4sugar macros I ref

Re: silly question about editor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [please don't top-post on technical lists] According to aaragon on 3/5/2009 9:08 AM: > I guess what I mean is that if you put an space between the MACRO and the > starting parenthesis, the macro fails and it's not like the error will point > you to th

Re: problem with ifelse

On Thu, 5 Mar 2009, Eric Blake wrote: Most of the m4sugar macros I referred to are quite old. The nice thing about git development is that it is easy to find when something was introduced. For example, m4_toupper was only mentioned in two commit messages: I have looked in the ChangeLog fil