Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
Cc: perex@suse.cz, m@iriXx.org,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: errors in symlinks in alsa-oss rc1 with mandrake 9.0
Date: Tue, 17 Dec 2002 11:48:27 +0100	[thread overview]
Message-ID: <s5hr8cgsyys.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DFEFA01.10600@gmx.de>

At Tue, 17 Dec 2002 11:18:41 +0100,
Friedrich Ewaldt wrote:
> 
> Hi!
> 
> Exactly the same problem for me.
> ./configure fails for alsa-oss-0.9.0rc1 (extracted from 
> alsa-oss-0.9.0rc1.tar.bz2) because /usr/share/automake doesn't exist. 
> (There's only a /usr/share/automake-1.4 directory in my mandrake 9.0 
> installation).
> 
> here's part of 'ls -l alsa-oss-0.9.0rc1' output after extracting from 
> the tarball:
> [...]
> lrwxrwxrwx    1 root     root           30 Dez 17 11:02 install-sh -> 
> /usr/share/automake/install-sh
> lrwxrwxrwx    1 root     root           27 Dez 17 11:02 missing -> 
> /usr/share/automake/missing
> lrwxrwxrwx    1 root     root           33 Dez 17 11:02 mkinstalldirs -> 
> /usr/share/automake/mkins
> These 3 links are pointing to a path that doesn't exist.

ah, that explains the cause.  we missed --copy option for automake.
anyway, cvscompile should work (as long as you installed autoconf,
automake and libtool).


Jaroslav, could you repackage the alsa-oss tarball at the next
release?


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

      reply	other threads:[~2002-12-17 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 17:44 errors in symlinks in alsa-oss rc1 with mandrake 9.0 iriXx
2002-12-16  9:58 ` Thierry Vignaud
2002-12-17 10:18 ` Friedrich Ewaldt
2002-12-17 10:48   ` Takashi Iwai [this message]

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=s5hr8cgsyys.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=friedrich.ewaldt@gmx.de \
    --cc=m@iriXx.org \
    --cc=perex@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox