On 3 Jul 2000, Akim Demaille wrote:
>
> | Here is the input from configure.in.
> |
> | AC_CHECK_FUNC(BSDgettimeofday, AC_DEFINE(HAVE_BSDGETTIMEOFDAY),
> | AC_CHECK_FUNC(gettimeofday, , AC_DEFINE(NO_GETTOD)))
> | AC_MSG_CHECKING([for gettimeofday declaration])
> | AC_EGREP_HEADER(gettime
| [EMAIL PROTECTED] (Johan Danielsson) writes:
| > This doesn't work with newer autoconf since it explicitly checks for
| > ` and $.
|
| Isn't this infact a bug?
|
| AC_INIT(configure.in)
| AC_CONFIG_HEADER(config.h)
| zz=X
| AC_DEFINE_UNQUOTED($zz, 1, test)
|
| produces an emp
> "Larry" == Larry W Virden <[EMAIL PROTECTED]> writes:
Hi Larry!
Larry> What is the preferred method of submitting changes to autoconf?
Small patches against the current CVS version sent to
[EMAIL PROTECTED] Be sure to read the `coding style' node in
the CVS documentation.
Akim
| mo(~/project/tcl/unix)% autoconf
| configure.in:154: warning: AC_STRUCT_ST_BLKSIZE:
| your code should no longer depend upon `HAVE_ST_BLKSIZE', but
| `HAVE_STRUCT_STAT_ST_BLKSIZE'. Remove this AC_WARNING and
| the `AC_DEFINE' when you adjust the code.
|
| Here is the b
| | mo(~/project/tcl/unix)% autoconf
| | configure.in:154: warning: AC_STRUCT_ST_BLKSIZE:
| | your code should no longer depend upon `HAVE_ST_BLKSIZE', but
| | `HAVE_STRUCT_STAT_ST_BLKSIZE'. Remove this AC_WARNING and
| | the `AC_DEFINE' when you adjust the code.
| |
| |
# AC_PROG_F77_C_O
# ---
# Test if the Fortran 77 compiler accepts the options `-c' and `-o'
# simultaneously, and define `F77_NO_MINUS_C_MINUS_O' if it does not.
#
# The usefulness of this macro is questionable, as I can't really see
# why anyone would use it. The only reason I inclu
> "Martin" == Martin Wilck <[EMAIL PROTECTED]> writes:
Martin> Are you aware of the fact that automake inserts -c -o in the
Martin> build rule automatically? This makes the usefulness of this
Martin> test even more questionable, at least in connection with
Martin> automake.
I'm all for the
Akim Demaille <[EMAIL PROTECTED]> writes:
> | [EMAIL PROTECTED] (Johan Danielsson) writes:
> | > This doesn't work with newer autoconf since it explicitly checks for
> | > ` and $.
> |
> | Isn't this infact a bug?
> |
> | AC_INIT(configure.in)
> | AC_CONFIG_HEADER(config.h)
> | zz=X
On 16 Jul 2000, Russ Allbery wrote:
> My macro instead does *tzname = "UTC". I'm not aware of any platform that
> uses these variables but doesn't allow the user to modify them, so that
> seems to work.
Seems reasonable, but the fact that you have to wonder in the first place
makes this the see
| Akim Demaille <[EMAIL PROTECTED]> writes:
| > | [EMAIL PROTECTED] (Johan Danielsson) writes:
| > | > This doesn't work with newer autoconf since it explicitly checks for
| > | > ` and $.
| > |
| > | Isn't this infact a bug?
| > |
| > | AC_INIT(configure.in)
| > | AC_CONFIG_HEADER(conf
Akim Demaille <[EMAIL PROTECTED]> writes:
> It cannot have ever *properly* worked.
Did in 2.13, as I said.
> Pay attention that you're referring to the creation of config.h.in.
Yes.
> Maybe AC_DEFINE(`echo FOO`) used to be understood by autoheader, but
> it was a misfeature. In the general c
| > Maybe AC_DEFINE(`echo FOO`) used to be understood by autoheader, but
| > it was a misfeature. In the general case, this cannot be done,
| > hence it must never work :)
|
| AC_DEFINE_UNQUOTED(`echo FOO`). Why can't it work? What happened in
| 2.13 was that you ended up with
|
| cat << END
|
: On 17 Jul 2000, Akim Demaille wrote:
: > | Akim Demaille <[EMAIL PROTECTED]> writes:
: > | > | AC_DEFINE_UNQUOTED($zz, 1, test)
: > | Yes, but this is *_UNQUOTED. If it can't possibly accept a third
: > | argument, why is it documented as doing so? And it *did* work in 2.13.
: >
: > I mean
Does this make sense? Kinda silly to have to run autoheader before
running autoreconf.
/Johan
--- autoreconf.sh 2000/07/10 14:03:12 1.43
+++ autoreconf.sh 2000/07/17 18:38:06
@@ -350,7 +350,7 @@
stamp_num=`test "$tcount" -gt 1 && echo "$tcount"`
stamp=$template_dir/sta
On 17 Jul 2000, Akim Demaille wrote:
> : I missed this thread: what is your counter-example?
>
> I know what you are going to say: we don't need autoheader, we should
> just spit a cleaned up version of confdefs.h, as your patch does. But
> I don't share this opinion, so yes, it is important to
On 17 Jul 2000, Akim Demaille wrote:
> | Akim Demaille <[EMAIL PROTECTED]> writes:
> | > | AC_DEFINE_UNQUOTED($zz, 1, test)
> | Yes, but this is *_UNQUOTED. If it can't possibly accept a third
> | argument, why is it documented as doing so? And it *did* work in 2.13.
>
> I meant the AC_DEFIN
On 17 Jul 2000, Akim Demaille wrote:
>
> | > Maybe AC_DEFINE(`echo FOO`) used to be understood by autoheader, but
> | > it was a misfeature. In the general case, this cannot be done,
> | > hence it must never work :)
> |
> | AC_DEFINE_UNQUOTED(`echo FOO`). Why can't it work? What happened in
>
Akim Demaille <[EMAIL PROTECTED]> writes:
> :) This is what I call not to work properly :) Try with your $x for
> instance. It would work only for trivial examples.
Not really, since that code is evaluated in a context (in configure)
where $x is set properly.
> Then do not use this, this is a
On 17 Jul 2000, Johan Danielsson wrote:
> They do their job by using m4 to translate characters, but this will
> never work for shell variables.
( indeed - but he doesn't want us to use shell variables ;-)
--
T.E.Dickey <[EMAIL PROTECTED]>
http://dickey.his.com
ftp://dickey.his.com
Akim Demaille writes:
> I'm all for the removal of this macro.
> I'm for the removal of C's one too (there is none for C++ right?), but
> here we are hitting the backward compatibility barrier. In fact, this
> macro should move under GNU Make's responsibility, since it's probably
> the only use
On Mon, Jul 17, 2000 at 08:15:17PM +0200, Akim Demaille wrote:
> : I missed this thread: what is your counter-example?
>
> I know what you are going to say: we don't need autoheader, we should
> just spit a cleaned up version of confdefs.h, as your patch does. But
> I don't share this opinion, s
On Jul 17, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> Maybe AC_DEFINE(`echo FOO`) used to be understood by autoheader, but
> it was a misfeature. In the general case, this cannot be done, hence
> it must never work :)
If autoheader doesn't understand it, it's fine: it's perfectly
acceptab
eisentrp <[EMAIL PROTECTED]> writes:
> On 16 Jul 2000, Russ Allbery wrote:
>> My macro instead does *tzname = "UTC". I'm not aware of any platform
>> that uses these variables but doesn't allow the user to modify them, so
>> that seems to work.
> Seems reasonable, but the fact that you have to
I'd like to draw your attention to the following problem:
There is one thing the autoconf/automake support for Fortran 77
is currently lacking: dependency tracking like for C/C++.
First of all, an automake-generated makefile refuses to work
if there is no C source file specified in Makefile.am
24 matches
Mail list logo
