[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new module 'iconv_open'
From: |
Bruno Haible |
Subject: |
Re: new module 'iconv_open' |
Date: |
Wed, 4 Apr 2007 13:20:12 +0200 |
User-agent: |
KMail/1.5.4 |
Simon Josefsson wrote:
> > Also, AC_PROG_YACC doesn't do this. It simply prints one line of output,
> > like most other autoconf tests.
>
> Right, but AC_PROG_YACC doesn't test whether there is a yacc tool
> installed.
Huh? Autoconf's doc says:
-- Macro: AC_PROG_YACC
If `bison' is found, set output variable `YACC' to `bison -y'.
Otherwise, if `byacc' is found, set `YACC' to `byacc'. Otherwise
set `YACC' to `yacc'.
Really I don't see a difference between the situations for bison, gperf, and
gaa. All three are development tools needed by the maintainer but not needed
for users of a tarball. All three are not among the set of tools required
by 'configure'.
The only difference I see is the immediate reference to the download location
in the gaa macro, but this is what an INSTALL or DEPENDENCIES file is good for,
no?
Bruno
- Re: new module 'iconv_open', (continued)
- Re: new module 'iconv_open', Simon Josefsson, 2007/04/02
- Re: new module 'iconv_open', Bruno Haible, 2007/04/02
- Re: new module 'iconv_open', John Darrington, 2007/04/02
- Re: new module 'iconv_open', Bruno Haible, 2007/04/02
- Re: new module 'iconv_open', Ben Pfaff, 2007/04/03
- Re: new module 'iconv_open', Bruno Haible, 2007/04/03
- Re: new module 'iconv_open', Ben Pfaff, 2007/04/03
- Re: new module 'iconv_open', Simon Josefsson, 2007/04/03
- Re: new module 'iconv_open', Bruno Haible, 2007/04/03
- Re: new module 'iconv_open', Simon Josefsson, 2007/04/04
- Re: new module 'iconv_open',
Bruno Haible <=
- Re: new module 'iconv_open', Simon Josefsson, 2007/04/04
Re: new module 'iconv_open', Bruno Haible, 2007/04/02