In message [EMAIL PROTECTED], Pavel
Roskin writes:
Hello, Martin!
Let's think about when you would ever want to reuse a cache within a
simple single GNU package. I claim you _never_ want to reuse that
config.cache file sitting in your foo-1.9 directory. Why are you
re-running configure,
In message [EMAIL PROTECTED], Akim Demaille writes:
"Olly" == Olly Betts [EMAIL PROTECTED] writes:
Olly It also saves a lot of time if you're using automake and doing
Olly work that involves changing your Makefile.am-s. Whenever one is
Olly modified, running make will run automake
In article [EMAIL PROTECTED], Morten Eriksen wrote:
[EMAIL PROTECTED] (Olly Betts) writes:
Also might it not be better to try each compiler in the list which
exists in turn and using the first working one, rather than just
trying the first compiler which exists?
The problem
This is with autoconf 2.60.
After mail from a user who'd tried to specify -llibrary in LDFLAGS
I was suprised to realise that the output of ./configure --help
doesn't mention LIBS at all. I think it should - while the autoconf
info manual documents both LDFLAGS and LIBS and the distinction
SGI's compiler on IRIX appears to treat #error as a warning. And IRIX
uses #error in stdint.h if it's included in non-C99 mode (either C89 or C++)
and doesn't define the types if this is the case.
So trying to compile #include stdint.h works as far as configure is
concerned, but none of the
On 2007-11-21, Karl Berry [EMAIL PROTECTED] wrote:
Since there is no reason to prefer [, it is good to keep using test,
because of the quoting, and for consistency with all the existing code
that does so.
Using `[' is better in a particular case in makefiles - there the
Solaris VPATH rewriting
On 2008-01-09, Brad Larsen [EMAIL PROTECTED] wrote:
I have a project that has been mostly switched to use autotools. Seems to
work OK with the GNU compilers. When attempting to build on a cluster we
have using the Portland Group toolchain, configure bails out saying the
preprocessor is
On 2008-10-16, Ralf Wildenhues [EMAIL PROTECTED] wrote:
How do you get two concurrent configure scripts updating the same
config.cache file?
Open terminal (or screen) windows for two subdirectories of the combined
tree and in each modify a file which causes configure to be rerun (e.g.
On 2008-10-17, Eric Blake [EMAIL PROTECTED] wrote:
According to Olly Betts on 10/16/2008 7:40 PM:
On 2008-10-16, Ralf Wildenhues [EMAIL PROTECTED] wrote:
How do you get two concurrent configure scripts updating the same
config.cache file?
Open terminal (or screen) windows for two
On 2010-07-02, Eric Blake ebl...@redhat.com wrote:
[*] You can use either of the above signature files to verify that
the corresponding file (without the .sig suffix) is intact. First,
be sure to download both the .sig file and the corresponding tarball.
Then, run a command like this:
gpg
autoreconf is documented to work outside the current directory, and used
to in autoconf 2.59. The patch below fixes that.
To reproduce, pick any autoconf-ed project, change to the directory
above and run autoreconf PROJECTDIRECTORY.
I also notice a worrying mismatch between the comment and the
On 2009-11-24, Ralf Wildenhues ralf.wildenh...@gmx.de wrote:
-mkdir $cache, 0755
+mkdir $cache
The umask argument to mkdir is required by older versions of Perl. I think
it became optional in 5.6. I'm not sure if automake has a minimum Perl
version it aims to support (it doesn't seem
12 matches
Mail list logo
