Re: Autom4te, autoconf problem

2002-09-05 Thread Akim Demaille
> "f" == f l writes: f> It's m4 1.4pre2 and I tried with m4 1.4 but I obtained the same f> output message. f> I think: "autom4te -F autoconf.m4f autoconf.m4" it 's correct, f> isn't it ? f> I just want to build frozen file "autoconf.m4f". Wow! So *you* are the autom4te user :) Yes, that

../configure question

2002-09-05 Thread Troy Cauble
I am cleaning up some autoconf scripts to support multiple builds against the same source, as in mkdir build_dir1 cd build_dir1 ../configure In the middle of this large autoconf based project there's a third party module that does not use autoconf. "./configure" style builds work becau

Re[1] Autom4te, autoconf problem

2002-09-05 Thread f l
It's m4 1.4pre2 and I tried with m4 1.4 but I obtained the same output message. I think: "autom4te -F autoconf.m4f autoconf.m4" it 's correct, isn't it ? I just want to build frozen file "autoconf.m4f". __ Boîte aux lettres - Lycos - http://www

Autom4te, autoconf problem

2002-09-05 Thread f l
It's m4 1.4pre2 and I tried with m4 1.4 but I obtained the same output message. I think: "autom4te -F autoconf.m4f autoconf.m4" it 's correct, isn't it ? I just want to build frozen file "autoconf.m4f". __ Boîte aux lettres - Lycos - http://www

Re: Porting to Sparc64 question

2002-09-05 Thread Peter Eisentraut
Bill Moseley writes: > Is there anything in autoconf that will help determine this required > alignment size? The PostgreSQL source tree contains a macro to do that. You call PGAC_CHECK_ALIGNOF(type) and it defines ALIGNOF_TYPE to the required alignment. You can find it in http://developer.

Re: Autom4te, autoconf problem

2002-09-05 Thread Earnie Boyd
/usr/bin/m4 --version? Earnie. f l wrote: > > Hi all, > > when I execute this command: > > autom4te -F autoconf.m4f autoconf.m4 > > I obtain this output: > > autoconf.m4:108: /usr/bin/m4: Warning: Too few arguments to > built-in 'patsubst' > > Anyone know what is the problem ? > > Thanks

Autom4te, autoconf problem

2002-09-05 Thread f l
Hi all, when I execute this command: autom4te -F autoconf.m4f autoconf.m4 I obtain this output: autoconf.m4:108: /usr/bin/m4: Warning: Too few arguments to built-in 'patsubst' Anyone know what is the problem ? Thanks __ Boîte aux lettres -

Re: config variables in config.h

2002-09-05 Thread Dan Kegel
Alexandre Duret-Lutz wrote: > I've stopped hard-coding absolute paths in my package because it > hinders relocation of binary packages. > > Instead, at configure-time (not everybody will like this) I turn > each pathname into a path relative to $(prefix), and guess > $(prefix) at run-time. > > S

Re: Problem with symlinks and VPATH Builds

2002-09-05 Thread Paul Eggert
> From: Alexandre Duret-Lutz <[EMAIL PROTECTED]> > Date: Thu, 05 Sep 2002 16:58:00 +0200 > > FWIW, I've installed CVS Automake on Solaris 8 today and fixed a > few things until `make check' succeed. Still that was with perl > 5.6, and without libtool/texinfo/gcj (32 tests were skipped), so > I g

Re: config variables in config.h

2002-09-05 Thread Viktor Pavlenko
> "GD" == Guido Draheim <[EMAIL PROTECTED]> writes: GD> Es schrieb Viktor Pavlenko: >> >> Hello, >> >> I would like my program to know where it has been installed, in >> particular, the location of $datadir. Looks like a natural way >> to do it is to have a #defi

Re: Problem with symlinks and VPATH Builds

2002-09-05 Thread Alexandre Duret-Lutz
>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes: [...] Paul> I have to get Automake working on my usual platform Paul> (Solaris 8). Automake is badly broken right now (it Paul> assumes Perl 5.6, it assumes GNU make, and probably some Paul> other unportable assumptions like that). FWIW

Re: config variables in config.h

2002-09-05 Thread Alexandre Duret-Lutz
>>> "Earnie" == Earnie Boyd <[EMAIL PROTECTED]> writes: Earnie> Alexandre Duret-Lutz wrote: >> >> for an example. >> >> (Obviously there are situation wheres computing relative paths is not >> always possible -- think A:\foo C:\bar -- but I can live with that.) Earnie> Why should this p

Re: config variables in config.h

2002-09-05 Thread Earnie Boyd
Alexandre Duret-Lutz wrote: > > for an example. > > (Obviously there are situation wheres computing relative paths is not > always possible -- think A:\foo C:\bar -- but I can live with that.) Why should this present problems? Earnie.

Re: config variables in config.h

2002-09-05 Thread Alexandre Duret-Lutz
>>> "Viktor" == Viktor Pavlenko <[EMAIL PROTECTED]> writes: [...] Viktor> I tried the following in configure.in: Viktor> AC_DEFINE_UNQUOTED(MYPROG_DATA_DIR,$datadir,[myprog data directory]) Viktor> but it doesn't work ($prefix/share is inserted and not expanded). I Viktor> would appreciate

Re: Problem with symlinks and VPATH Builds

2002-09-05 Thread Paul Eggert
> From: Akim Demaille <[EMAIL PROTECTED]> > Date: 04 Sep 2002 10:45:05 +0200 > > The Autoconf documentation was documenting how to work around the > CDPATH issues without `unset', because in Makefiles that's usually > what's done. For instance, with CVS Automake: > > % grep CDPATH Makefile > am

Re: config variables in config.h

2002-09-05 Thread Paul Eggert
> From: Viktor Pavlenko <[EMAIL PROTECTED]> > Date: Wed, 4 Sep 2002 20:39:48 -0400 > > I would like my program to know where it has been installed, in > particular, the location of $datadir. Looks like a natural way to do > it is to have a #define in config.h, like this: > > /* > * myprog data

Re: config variables in config.h

2002-09-05 Thread Guido Draheim
Es schrieb Viktor Pavlenko: > > Hello, > > I would like my program to know where it has been installed, in > particular, the location of $datadir. Looks like a natural way to do > it is to have a #define in config.h, like this: > > /* > * myprog data directory > */ > #define MYPROG_DATA_DIR "