Daniel Pocock writes:
> Thanks for this - it may be just what we need to get some nasty hacks out
> of configure.in
> In case I use this as-is, can you kindly confirm that it is compatible
> with the Ganglia license?
> http://ganglia.svn.sourceforge.net/viewvc/ganglia/trunk/monitor-core/COPYING?
Russ Allbery wrote:
Daniel Pocock writes:
Thanks for that - the sed example appears to be the type of thing I want.
However, is there a more concise way to do this? I was thinking there may
be some way to invoke sed or m4 on a template in much the way that gcc is
invoked for *.c
Daniel Pocock writes:
> Thanks for that - the sed example appears to be the type of thing I want.
> However, is there a more concise way to do this? I was thinking there may
> be some way to invoke sed or m4 on a template in much the way that gcc is
> invoked for *.c
Half of that equation woul
Peter Johansson wrote:
Daniel Pocock wrote:
Therefore, I felt that I should be aiming to have the config files
generated at the last moment - probably during `make install', just
before they are installed. Can anyone suggest best practice for
doing this?
please refer to
http://www.gnu
Daniel Pocock wrote:
Therefore, I felt that I should be aiming to have the config files
generated at the last moment - probably during `make install', just
before they are installed. Can anyone suggest best practice for doing
this?
please refer to
http://www.gnu.org/software/autoconf/m
Hi,
I've been working on a project, Ganglia, that is built with autotools
Included in the source tree are templates for various configuration
files (e.g. modpython.conf.in). Some of these include hard coded paths.
It seems appropriate to replace the hardcoded paths with substitutions
(e.g
Thanks, I forwarded my original question.
nick
On Wed, Jan 13, 2010 at 13:06, Ralf Wildenhues wrote:
> Hello Nicolas,
>
> * Nicolas Bock wrote on Wed, Jan 13, 2010 at 08:41:35PM CET:
> > on Ubuntu 8.04 I find that if I specify CC when I run configure, the
> > configure script dies when it runs
Hello Nicolas,
* Nicolas Bock wrote on Wed, Jan 13, 2010 at 08:41:35PM CET:
> on Ubuntu 8.04 I find that if I specify CC when I run configure, the
> configure script dies when it runs config.sub. I get this output
>
> $ CC=/usr/local/gcc-4.3.0/bin/gcc ./config.guess
> x86_64-unknown-linux-
>
> b
Hello list,
on Ubuntu 8.04 I find that if I specify CC when I run configure, the
configure script dies when it runs config.sub. I get this output
$ CC=/usr/local/gcc-4.3.0/bin/gcc ./config.guess
x86_64-unknown-linux-
but when I run with the system compiler (gcc 4.2.4):
$ ./config.guess
x86_64-u
