From: Chris Pemberton <cjpembo.mailing.lists@gmail.com>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Request for test (1.0.18 final)
Date: Tue, 28 Oct 2008 16:10:39 -0500 [thread overview]
Message-ID: <49077FCF.1000801@gmail.com> (raw)
In-Reply-To: <490615B8.8070707@gmail.com>
Chris Pemberton wrote:
> Jaroslav Kysela wrote:
>> On Mon, 27 Oct 2008, Chris Pemberton wrote:
>>
>>
>>> /home/cjpembo/LatestALSA/alsa-driver-1.0.18rc3.17.gd338c.191.ge29c1/acore/../alsa-kernel/core/jack.c:108:
>>> error: 'SW_LINEOUT_INSERT' undeclared (first use in this function)
>>>
>>
>> Could you try again latest snapshot? I just included the patch which
>> should fix this issue.
>>
>> Jaroslav
>>
>> -----
>> Jaroslav Kysela <perex@perex.cz>
>> Linux Kernel Sound Maintainer
>> ALSA Project, Red Hat, Inc.
>>
>>
>>
> Alsa-driver compiles fine now; as does alsa-lib.
> I've moved on to testing alsa-utils and I'm getting the following error:
>
>
> I/O error : Attempt to load network entity
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
> warning: failed to load external entity
> "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"
> compilation error: file /tmp/xmlto-xsl.FIhlna line 4 element import
> xsl:import : unable to load
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
> make[2]: *** [alsactl_init.7] Error 1
> make[2]: Leaving directory
> `/home/cjpembo/LatestALSA/alsa-utils-1.0.18rc3.5.gd7f90/alsactl'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory
> `/home/cjpembo/LatestALSA/alsa-utils-1.0.18rc3.5.gd7f90/alsactl'
> make: *** [install-recursive] Error 1
>
> I have internet connectivity, so that shouldn't be the problem. In
> addition, I can download the file OK using wget:
>
> wget
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
>
> Chris
>
>
alsa-utils -> ok (just needed to install a docbook-xsl package)
alsa-driver -> ok
alsa-lib -> ok
alsa-plugins -> ok.
alsa-tools -> fails
1. The qlo10k1 stuff fails; so I just comment-out "qlo10k1" in the
"SUBDIRS =" line of the Makefile and keep compiling.
2. It fails again later when compiling a ui with the QT toolkit. It
needs an older version than I have installed. I'm convinced it would
probably compile clean if I were to downgrade, but I'm not going to try.
So I can say all the packages compile fine in Archlinux with a 2.6.27
kernel, gcc version 4.3.2, in both 32 and 64-bit environments.
Chris
next prev parent reply other threads:[~2008-10-28 21:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 13:54 Request for test (1.0.18 final) Jaroslav Kysela
2008-10-27 14:47 ` Colin Guthrie
2008-10-27 15:00 ` Takashi Iwai
2008-10-27 17:14 ` Chris Pemberton
2008-10-27 18:18 ` Jaroslav Kysela
2008-10-27 18:56 ` Takashi Iwai
2008-10-27 19:25 ` Chris Pemberton
2008-10-28 21:10 ` Chris Pemberton [this message]
2008-10-28 8:06 ` Clemens Ladisch
2008-10-28 9:28 ` Takashi Iwai
2008-10-28 11:53 ` Clemens Ladisch
2008-10-28 12:00 ` Takashi Iwai
2008-10-28 13:24 ` Clemens Ladisch
2008-10-27 20:41 ` Alan Horstmann
2008-10-28 6:56 ` Takashi Iwai
2008-10-29 8:48 ` Jaroslav Kysela
2008-10-29 8:53 ` Takashi Iwai
2008-10-29 8:56 ` Jaroslav Kysela
2008-10-29 13:25 ` Request for test (1.0.18 final) (2.4 Kernel report) Alan Horstmann
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=49077FCF.1000801@gmail.com \
--to=cjpembo.mailing.lists@gmail.com \
--cc=alsa-devel@alsa-project.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.