On 16 May 2001 00:22:43 +0200, Ralf Corsepius wrote:
> Until now this package's configure.in has been using AC_EXEEXT alone
> (w/o AC_PROG_CC), now I seem to need adding AC_PROG_CC, but ..
> .. Adding AC_CANONICAL_HOST would give sense, but this also
> apparently isn't sufficient.
This does seem
On 12 May 2001 15:47:10 +0200, Akim Demaille wrote:
>
> On a second thought, the right way to handle this depends upon the
> nature of $1: is it always a literal, or can it be a shell variable?
> If it's always a literal, then your first approach but using
> translit([HAVE_DECL_$1], [a-z], [A-Z])
Sorry for the delay in replying; my home PC suffered a minor heat
stroke and will be out of action for a while :-)
On 12 May 2001 15:36:53 +0200, Akim Demaille wrote:
> > "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
>
> Tim> The only call is
>
> Tim> gcc_AC_CHECK_PROG_VER(MAKEINFO,
¿©·¯ºÐ¿¡°Ô °¡Àå ÇÊ¿äÇÏ°í À¯ÀÍÇÑ ÄÄÇ»ÅÍ °ü·ÃÇÁ·Î±×·¥À»
ÆÄ°ÝÀûÀ¸·Î ½Ñ °¡°Ý¿¡ °ø±ÞÇÕ´Ï´Ù
ÃֽŰÔÀÓ. À¯Æ¿°ü·ÃÇÁ·Î±×·¥. MP3. ºñµð¿À½Ãµð µîµî
¸ðµç ÇÁ·Î±×·¥À» ÆǸÅÇÕ´Ï´Ù. 5¿ù ÃֽŸ®½ºÆ®ÀÔ´Ï´Ù
¹°·Ð ½Å¿ë °ÆÁ¤À» ÀüÇô ½Å°æ¾²Áö ¸¶½Ê½Ã¿ä
¾ÐÃàÈÀϼÓÀÇ ³»¿ëÀ» º¸½ÅÈÄ Àüȳª ¸ÞÀÏ·Î ¿¬¶ôÁֽʽÿä
ÀÌ ¸ÞÀÏÀ» º¸³½ ¾Æ
On May 14, 2001, "Steve M. Robbins" <[EMAIL PROTECTED]> wrote:
> Is it common to use a macro that expands to an lvalue?
We've been using this to rename variables but keep them working for
backward compatibility.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat
Akim Demaille wrote:
>
> > "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
>
> Ralf> Hi,
>
> Hi!
>
> Ralf> With autoconf-cvs AC_EXEEXT doesn't do anything anymore. I.e.
> Ralf> configure-scripts which are using AC_EXEEXT, but do not
> Ralf> explicitly call AC_PROG_CC, silently break w
> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> Hi,
Hi!
Ralf> With autoconf-cvs AC_EXEEXT doesn't do anything anymore. I.e.
Ralf> configure-scripts which are using AC_EXEEXT, but do not
Ralf> explicitly call AC_PROG_CC, silently break with autoconf-cvs
Ralf> (@EXEEXT@ will not
Hi,
With autoconf-cvs AC_EXEEXT doesn't do anything anymore. I.e.
configure-scripts which are using AC_EXEEXT, but do not explicitly
call AC_PROG_CC, silently break with autoconf-cvs (@EXEEXT@ will not
be substituted).
Can't autoconf at least warn about using AC_EXEEXT w/o AC_PROG_CC?
Ralf
$1 for AM_CONFIG_HEADER is just inserted into config.status verbatim
without being flattened. You can write "pretty" lists for AC_CONFIG_FILES
but not for AM_CONFIG_HEADER - some consistency would be nice.
Lars J
