From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: m@iriXx.org
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: errors in symlinks in alsa-oss rc1 with mandrake 9.0
Date: Mon, 16 Dec 2002 10:58:13 +0100 [thread overview]
Message-ID: <m2of7ms2tm.fsf@vador.mandrakesoft.com> (raw)
In-Reply-To: <3DFCBF9A.2090108@iriXx.org> (iriXx's message of "Sun, 15 Dec 2002 17:44:58 +0000")
iriXx <m@iriXx.org> writes:
> just a note to say i had to modify the symlinks to 'missing',
> 'mkinstalldirs' and 'install-sh' to get alsa-oss-0.9.0rc1 to install
> under mandrake 9.0.
alsa-oss just build fine, look at myt libalsa-oss0 package in mandrake
contribs.
> it seems that from 9.0 mandrake puts automake in
> /usr/share/automake-1.4 rather than /usr/share/automake.
mdk9.0 come with both automake-1.4 and automake-1.6 since some
packages need the latter and some other the first one.
there's nothing wrong in having versionnated directories such as
/usr/share/automake.
there's nothing enforcing having /usr/share/automake.
only automake should access such files.
> i dont know if anyone wants to add a detection for this to the
> config script?
you should not have to rely on automake macros being in
/usr/share/automake and i failled to see where such assumption is
made in alsa-oss build system in cvs.
so there's no point in such script.
if some tarball of some with a pre build configure and the like, and
if some links're broken, aclocal, libtoolize, automake and autoconf
are your friends to fix them.
anyway, generating them from cvs does works on any system having
automake & autoconf.
-------------------------------------------------------
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/
next prev parent reply other threads:[~2002-12-16 9:58 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 [this message]
2002-12-17 10:18 ` Friedrich Ewaldt
2002-12-17 10:48 ` 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=m2of7ms2tm.fsf@vador.mandrakesoft.com \
--to=tvignaud@mandrakesoft.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=m@iriXx.org \
/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.