All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Compiling alsa-utils
Date: Mon, 26 Jul 2010 11:17:24 +0200	[thread overview]
Message-ID: <4C4D52A4.3000003@ivitera.com> (raw)
In-Reply-To: <s5hr5iqwqwt.wl%tiwai@suse.de>

Takashi Iwai napsal(a):
> At Mon, 26 Jul 2010 10:58:09 +0200,
> Pavel Hofman wrote:
>> Hi,
>>
>> after clean git clone of  git://git.alsa-project.org/alsa-utils.git I
>> got the following error:
>>
>> pavel@sara:~/install/alsa/alsa-utils$ autoheader
>> configure.in:268: error: `po/Makefile.in' is already registered with
>> AC_CONFIG_FILES.
>> ../../lib/autoconf/status.m4:311: AC_CONFIG_FILES is expanded from...
>> configure.in:268: the top level
>> autom4te: /usr/bin/m4 failed with exit status: 1
>> autoheader: '/usr/bin/autom4te' failed with exit status: 1
>>
>>
>> After deleting po/Makefile.in from the list of AC_OUTPUT in
>> configure.in:268 the compilation proceeded fine.
>>
>> Ubuntu 9.10.
> 
> It's f*** auto-tools, that tells everything :)
> 
> Doesn't the simple gitcompile work after the clean clone?
> 
> 

Thanks, the gitcompile script works fine. I followed the procedure in
INSTALL:

        aclocal
        gettextize
        autoheader
        automake --foreign --copy --add-missing
        autoconf
        ./configure
        make



Perhaps we could either update this sequence (but I have no idea how :)
), or delete the procedure and just mention the gitcompile script (that
one I can post as a patch).

Thanks,


Pavel.

  reply	other threads:[~2010-07-26  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26  8:58 Compiling alsa-utils Pavel Hofman
2010-07-26  9:09 ` Takashi Iwai
2010-07-26  9:17   ` Pavel Hofman [this message]
2010-07-26  9:32     ` Takashi Iwai

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=4C4D52A4.3000003@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.