All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jack Howarth <howarth@bromo.msbb.uc.edu>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: autoheader and autoconf issues
Date: Mon, 07 Oct 2002 12:02:05 +0200	[thread overview]
Message-ID: <s5h7kgu4leq.wl@alsa2.suse.de> (raw)
In-Reply-To: <200210051334.JAA23819@bromo.msbb.uc.edu>

Hi Jack,

At Sat, 5 Oct 2002 09:34:00 -0400 (EDT),
Jack Howarth wrote:
> 
> Takashi,
>    In doing my weekly cvs pull from the alsa cvs and debian alsa package
> build, I discovered that we seem to have a dependency on autoheader and
> autoconf >= 2.5 now. Before I could always go into the alsa-lib and
> alsa-utils directory and do a './cvscompile' to prepare the directory
> for use as a replacement tarball. Now I find this fails under autoheader
> and autoconf 2.13...
> 
> howarth@bogus:~/alsacvs/alsa-lib$ ./cvscompile
> /usr/bin/autoheader2.13: Symbol `VERSION' is not covered by /usr/share/autoconf2.13/acconfig.h
> automake: configure.in: installing `./install-sh'
> automake: configure.in: installing `./mkinstalldirs'
> automake: configure.in: installing `./missing'
> configure.in: 85: required file `include/config.h.in' not found
> 
> If I edit both of the cvscompile scripts in alsa-lib and alsa-utils so
> that they explicitly call autoheader2.50 and autoconf2.50, then this
> works fine...
> 
> autoheader2.50: `include/config.h.in' is created
> 
> 
> Either we should get this fixed or somehow make sure autoheader/autoconf
> 2.50 or greater is called. 

it seems that i felt into a auto-tools' trap...

i get acconfig.h back to the tree so that the old autoheader should
work.  please give a try.


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

       reply	other threads:[~2002-10-07 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200210051334.JAA23819@bromo.msbb.uc.edu>
2002-10-07 10:02 ` Takashi Iwai [this message]
2002-10-07 10:31   ` Re: autoheader and autoconf issues Martin Langer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h7kgu4leq.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=howarth@bromo.msbb.uc.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.