From: Andrei Boros <andrei@srr.ro>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa-utils cvscompile
Date: Thu, 25 Sep 2003 06:00:10 +0300 [thread overview]
Message-ID: <3F725A3A.11C24B19@srr.ro> (raw)
In-Reply-To: s5hllsel1db.wl@alsa2.suse.de
Takashi Iwai wrote:
>
> hmm, check whether depcomp file at the top directory is empty.
> if so, try to remove depcomp.
> it must come from automake, but the combination of the old automake
> and the new libtool can be problematic.
removed an empty depcomp and problem solved. Thanks.
> anyway, the best way would be to upgrade (or even downgrade) the all
> GNU auto-tools to the sane combination. i'm not sure which version
> combinations are correct, though.
>
> upgrading them to the latest version would be fine for ALSA, but it
> might not work on others occasionally. sigh.
I don't know, I just upgraded severla weeks ago the compiler, gnu auto*,
libtool, make to the versions required to compile glibc-2.2.5, so they
are all pretty new.
It is true, however, that I downloaded the cvs tree few months ago, and
only did updates from then on, attempting to make it work.
--
ing. Andrei Boros
mailto:andrei@srr.ro / +40-21-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-25 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 9:13 alsa-utils cvscompile Andrei Boros
2003-09-23 14:38 ` Takashi Iwai
2003-09-24 11:25 ` Andrei Boros
2003-09-24 14:14 ` Takashi Iwai
2003-09-25 3:00 ` Andrei Boros [this message]
2003-09-25 9:20 ` 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=3F725A3A.11C24B19@srr.ro \
--to=andrei@srr.ro \
--cc=alsa-devel@lists.sourceforge.net \
--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.