> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
Martin> (XEmacs redefines AC_DEFINE)
Tom> Wow, why?
To support the --extra-verbose option
dnl Redefine AC_DEFINE* to provide more output if extra_verbose
dnl Set VARIABLE to VALUE, verbatim, or 1.
dnl AC_DEFINE(VARIABLE [, VALUE])
define([
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
Martin> To support the --extra-verbose option
Tom> Why is this important? Can't people just read config.h?
I introduced the option for myself years ago, and I continue to find
it useful.
Martin> XEmacs also modifies several of the other bas
>>>>> "AO" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
AO> On Feb 25, 2000, Martin Buchholz <[EMAIL PROTECTED]> wrote:
>> cd foo-1.9; configure; make; make install
>> login to other machine
>> cd foo-1.9; configure; make; make instal
Akim> Now, there's a README-alpha which is rather explicit.
Martin> Did you know that this autoconf uses $SHELL instead of
Martin> ${CONFIG_SHELL-/bin/sh}?
Akim> Where?
(martin@wobble) /usr/share/autoconf $ g -w SHELL acgeneral.m4
acgeneral.m4:211:SHELL=${CONFIG_SHELL-/bin/sh}
acgeneral.m4:69
>>>>> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
>>>>> "Martin" == Martin Buchholz <[EMAIL PROTECTED]> writes:
Martin> I've ranted about config.cache before, but it's probably time
Martin> again, because of th
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
Alexandre> The unfortunate side-effect of your proposal is that these
Alexandre> tests would suddenly start working, *unless* someone used a
Alexandre> cache file.
AD> Sorry, but I don't understand the relationship here. Whether there is
A
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
Martin> The config,cache is friendly mostly to Cygnus employees,
Martin> hostile to everyone else. Let's optimize for the newbies, not
Martin> the pros.
Tom> I don't disagree. I like Alexandre's idea of enabling it only when a
Tom> cache fi
>>>>> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
>>>>> "Martin" == Martin Buchholz <[EMAIL PROTECTED]> writes:
Martin> But this is just a special case that will reduce the
Martin> mismatches, but leave the most damagi
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
AD> I'm lost. You are saying we're right, XEmacs is wrong, right?
Correct.
AD> | I'll just redefine AC_PREREQ(2.13) to be a == test, not a <= test.
AD> Why? Give us a chance to catch up. But first, tell us what use of
AD> SHELL you do.
> "ILT" == Ian Lance Taylor <[EMAIL PROTECTED]> writes:
ILT> I personally don't really see why shell functions and unset matter
ILT> much for autoconf proper. You can already use m4 and weird shell
ILT> constructs to implement the same functionality (e.g., instead of
ILT> unsetting a cache v
> "PR" == Pavel Roskin <[EMAIL PROTECTED]> writes:
PR> 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-runnin
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> Because I want to try a different _configuration_:
Pavel> CFLAGS=-ggdb3 ./configure --enable-cute-feature --without-bloat
AD> Pavel, we need evangelists for the new support o
> "PR" == Pavel Roskin <[EMAIL PROTECTED]> writes:
>> Oops. Actually I'm not doing it by hand - I was thinking of what
>> happens when you change configure.in rather than Makefile.am. Changes
>> to configure.in are typically somewhat rarer.
PR> ... and the person doing them is supposed to
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
===
RC
> "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
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:
Did you know that Linux Mandrake 7.0's autoconf claims to be version 2.14.1?
(martin@wobble) /xemacs/build $ autoconf --version
Autoconf version 2.14.1
Did you know that this autoconf uses $SHELL instead of ${CONFIG_SHELL-/bin/sh}?
This would fail in the most obvious way if the user's shell was
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
AD> Your AC_OUTPUT section is frightening...
AD> Well, I realize the copy I have is dead broken:
AD> echo " Athena header include path: $athena=
AD> _h_path"
AD> fi
AD> test "$with_dnet" =3D yes && echo " Co
It feels like the body of AC_OUTPUT has different quoting levels
between 2.13 and latest CVS.
Notice that AC_DEFINE seems to get undefined because of its appearance
in a _comment_ in AC_OUTPUT. Bizarre! Changing that comment to
dnl XXAC_DEFINE
does not change things.
The dnl comment in AC_OU
AC_INIT_NOTICE claims:
# Generated automatically using Autoconf version ]AC_ACVERSION[
# Copyright (C) 1992, 93, 94, 95, 96, 98, 99, 2000
# Free Software Foundation, Inc.
#
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
AD> So I pulled out the definition of the macro out of AC_OUTPUT, removed
AD> the useless (or have I missed something) changequote (changequote is
AD> *hell*), and it works.
AD> dnl CPP_MAKEFILE(CPPFLAGS,filename)
AD> define([CPP_MAKEFILE],
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
Martin> It's true. But all C source files should #include ,
Martin> and other files will often be architecture-independent files
Martin> like lex&yacc files.
Tom> That's true for XEmacs, maybe, but it isn't true for the world. For
Tom> inst
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
AD> dnl CPP_MAKEFILE(CPPFLAGS,filename)
AD> define([CPP_MAKEFILE],
AD> [echo creating $dir/[$2]
AD> $CPP -I. -I${top_srcdir}/src [$1] junk.c \
AD> dnl Delete line directives inserted by $CPP
AD> | sed -e 's/^\#.*//' \
AD> dnl
>>>>> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
>>>>> "Martin" == Martin Buchholz <[EMAIL PROTECTED]> writes:
Martin> Notice that AC_DEFINE seems to get undefined because of its
Martin> appearance in a _comment_ in AC_OU
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
AD> We can introduce a Copyright diversion, where you could easily append
AD> your notices. Would that be enough?
I think so.
I do actually think rms cares, because he is a stickler for these
sorts of things. The obvious thing is to co
> "AD" == Akim Demaille <[EMAIL PROTECTED]> writes:
Martin> Even better would be to look for exact symbols in the output
Martin> that have a definition, so the word AC_ in the output would
Martin> generate no error message, while AC_DEFINE would.
AD> s/DEFINE/DEFUN/, don't you?
Of course.
I just discovered this post from jwz. (Jamie, I don't actually read
the autoconf mailing list regularly - please cc me)
>> I'm not proposing that the config.cache feature be removed, only that
>> it not be made the _default_.
>
> Sounds reasonable to me. How about only enabling it when given
Functions like accept are known to have THREE different prototypes:
int accept (int, struct sockaddr *, socklen_t *); /* Linux, Unix98 */
int accept (int, struct sockaddr *, size_t *); /* Solaris 2.6 */
int accept (int, struct sockaddr *, int *); /* DEC OSF 4.0e */
I think autoconf should have
> "lb" == lars brinkhoff <[EMAIL PROTECTED]> writes:
lb> For comparision, this is what I use in an application of mine. I
lb> haven't heard any complaints from Solaris users, but I guess they have
lb> just ignored any compilations warnings.
I don't include . The standard says I shouldn't h
>>>>> "PE" == Peter Eisentraut <[EMAIL PROTECTED]> writes:
PE> Martin Buchholz writes:
>> Functions like accept are known to have THREE different prototypes:
>>
>> int accept (int, struct sockaddr *, socklen_t *); /* Linux, Unix98 */
>>
30 matches
Mail list logo
