Greg> In fact I would go so far as to suggest that "config.cache" is
Greg> only truly safe in its current form when it is used for nested
Greg> configure scripts, and then only when the nested scripts are all
Greg> directly realted in heritage to each other.
If by "heritage" you mean its direct a
[ On Friday, February 25, 2000 at 16:49:42 (-0500), Harlan Stenn wrote: ]
> Subject: Re: config.cache considered harmful
>
> I'd almost like to see a "version" number in the cache, which I can "bump"
> whenever I make a "significant" change to the logic which has the effect
> of...
It has always
Martin> ftp; get foo-1.9.tar.gz; gunzip; tar xf;
Martin> cd foo-1.9; configure; make; make install
Martin> login to other machine
Martin> cd foo-1.9; configure; make; make install
Martin> # Phew! That was easy!
Tom> This only really works if you generate a config.h and you are
Tom> lucky. If an
On Feb 25, 2000, "Paul D. Smith" <[EMAIL PROTECTED]> wrote:
> 1) Cross-compilation should be turned off unless some autoconf macro
> exists that says "this package is cross-compiler capable".
Agreed.
> If the compiler can't run the compiler test program and this
> special macro isn
> "Ian" == Ian Lance Taylor <[EMAIL PROTECTED]> writes:
Ian> The GNU binutils use this macro to detect this case:
Ian> dnl See whether we need a declaration for a function.
Ian> AC_DEFUN(BFD_NEED_DECLARATION,
There is something like this in Autoconf now:
Generic Declaration Checks
---
From: Akim Demaille <[EMAIL PROTECTED]>
Date: 26 Feb 2000 08:44:20 +0100
[ About the 8-bit bug on Ultrix ]
Finally, I'd like to understand how this turns out to be a malign bug.
I mean, I do see the 8th bits are set while they should not, but if
such a bug could have leaved inside
Date: Sat, 26 Feb 2000 14:59:49 +0500 (KGT)
From: CyberPsychotic <[EMAIL PROTECTED]>
What I am actually trying to figure out is whether certain function
prototypes (printf, fprintf etc) are defined in includes by passing
-pedantic-error switch to compiler. I've got a few notices t
Your AC_OUTPUT section is frightening...
Well, I realize the copy I have is dead broken:
echo " Athena header include path: $athena=
_h_path"
fi
test "$with_dnet" =3D yes && echo " Compiling in support for DNET."
I used wget on cvsweb though :( Any better means
> "Martin" == Martin Buchholz <[EMAIL PROTECTED]> writes:
Martin> (If you want to try this yourself, get the latest xemacs-21.2
Martin> configure.in. See http://cvs.xemacs.org/ )
I'm looking at it, but frankly, why don't you use m4/*.m4 files? Your
configure.in is just huge, and splitting
With my last patch for SHELL, xemacs' configure is compatible with the
Autoconf 2.14.1 from Mandrake Linux 7.0.
However, CVS autoconf utterly breaks xemacs. AC_DEFINE is not
defined, despite the fact that I define it. I have no idea how to
debug this.
The messages I get are:
configure.in:806:
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
AD> |I was wrong when I said XEmacs' configure indiscriminately uses
AD> |`unset'. In fact it does something like this:
AD> |
AD> |
AD> |if test -n "$ZSH_VERSION"; then
AD> | dnl zsh's Bourne shell emulation options
AD> | setopt NO_BAD_PA
Hello people,
Is there a way to pass command line switches to compiler when it tries to
detect whether certain function is present with AC_CHECK_FUNCS f.e.?
What I am actually trying to figure out is whether certain function
prototypes (printf, fprintf etc) are defined in includes by passing
-pe
2000-02-26 Martin Buchholz <[EMAIL PROTECTED]>
* configure.in: Unconditionally define SHELL, to allow working
with (unreleased) autoconf 2.14.1, found on Mandrake 7.0 systems.
Index: configure.in
===
RCS file: /usr
Ian Lance Taylor <[EMAIL PROTECTED]> writes:
> I've seen this argument before, but I don't entirely believe it. There
> is a lot of autoconf lore that is the result of people reporting
> problems. People then forget just what the problems were. But that
> does not mean that the problems were n
Martin Buchholz <[EMAIL PROTECTED]> writes:
> Of course, it goes without saying here that a careful user will always
> rm -rf;tar xzf to create a new pristine tree to build and install. We
> all do that, right? Dirty trees are only for hacking. But we should
> try to do the Right Thing even wh
> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
Paul> Perhaps eventually, but I suspect that it's premature to do it
Paul> now.
Ooops, sorry, it already went in :(
Paul> Part of the problem is that STDC_HEADERS is currently specific
Paul> to ANSI C (1989); it hasn't been modernized to I
> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
Harlan> I'd almost like to see a "version" number in the cache, which
Harlan> I can "bump" whenever I make a "significant" change to the
Harlan> logic which has the effect of...
Wel, consider your `bumping action' is `rm config.cache' :)
17 matches
Mail list logo
