From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "Takashi Iwai" <tiwai@suse.de>,
"Jörg Müller" <joerg.mueller7744@gmail.com>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Cannot combine audio devices with more than 64 channels
Date: Sat, 28 Jan 2017 08:14:52 +0900 [thread overview]
Message-ID: <f36e82bb-76a0-007d-f77c-faadf282864c@sakamocchi.jp> (raw)
In-Reply-To: <s5hd1f8hcc7.wl-tiwai@suse.de>
On Jan 27 2017 22:16, Takashi Iwai wrote:
> On Fri, 27 Jan 2017 14:03:16 +0100,
> Jörg Müller wrote:
>>
>> Thanks for the patch, that was fast!
>>
>> So I want to apply that patch to my system (Ubuntu Studio 14.04). How
>> do I proceed? I guess, the patch wont be available via apt-get soon,
>> right?
>
> I have no idea about Ubuntu. Ask Ubuntu people.
Ubuntu 14.04 is one of LTSs, while development for this release already
finished three years ago. Basically, packages for the release are not
updated unless some exceptions.
In your case, you can generate alsa-lib related packages with the patch
by your own. But no one can care of your packages and you need to do
everything to be required.; e.g. even if you encounter issues from the
generated packages, no one can help you.
$ sudo apt-get install build-essentials devscripts
$ sudo apt-get build-dep alsa-lib
$ cd /tmp
$ apt-get source alsa-lib
$ cd alsa-lib-*
(apply the patch)
$ dpkg-buildpackage -rfakeroot -uc -b
(packages are generated in higher directory by one level)
Perhaps, the above command lines are not enough. Some packages are still
missing for packaging.
Regards
Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2017-01-27 23:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 14:14 [Alsa-Devel] Cannot combine audio devices with more than 64 channels Jörg Müller
2017-01-26 16:12 ` Takashi Iwai
2017-01-26 16:13 ` Clemens Ladisch
2017-01-27 11:08 ` Takashi Iwai
2017-01-27 13:03 ` Jörg Müller
2017-01-27 13:16 ` Takashi Iwai
2017-01-27 23:14 ` Takashi Sakamoto [this message]
2017-01-31 17:00 ` Jörg Müller
2017-01-27 20:25 ` John Rigg
2017-01-31 17:18 ` Jörg Müller
2017-01-31 17:58 ` John Rigg
2017-01-31 18:46 ` Takashi Iwai
[not found] ` <20170131193159.GA17070@localhost.localdomain>
2017-02-08 14:12 ` Jörg Müller
2017-02-08 16:12 ` John Rigg
2017-02-08 16:20 ` John Rigg
2017-02-08 16:31 ` John Rigg
2017-02-08 17:22 ` Jörg Müller
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=f36e82bb-76a0-007d-f77c-faadf282864c@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=joerg.mueller7744@gmail.com \
--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.