Hello,
I use a bluetooth headset.
With some SDL applications[1][2][3][4] I got this error :
ALSA lib audio/pcm_bluetooth.c:1607:(audioservice_expect) BT_OPEN failed :
Invalid argument(22)
and audio doesn't work.
Whereas with other applications[5][6] I got no error message and the audio
works.
This is part of the reason that I use --prefix=/usr because the
/usr/includes/ are also affected by the --prefix option (i.e.
/usr/local/includes / which is empty). And I've never really gotten
into the changing $PATH part of things. But there's a whole slew of
-I and -L options (with a different
I think your statement here "
i.e. how exactly would you create your tarball? From a diff of an
entire backup before and after make install?
" best sums it up. Without a staging directory to "install" to, you
would have to parse the entire FS in order to find what the "make
install" step did.
I run opensuse. I'm not going to pretend to be an expert at pci slots, but the
cards never swapped around for me.
What you probably should do is find a forum related to Digidesign (protools?).
The boxes were used in multitrack audio recording prior to the availability of
multitrack sound cards
Another question i have decided to buy magma box 7 pci. Are you sure debian
6 always load the magma pci slots in the same order? Otherwise you can
understand that for me is an insurmountable problem
Thanks
Il giorno 16/giu/2011 18.42, ha scritto:
--
Ummm. I'm not sure if I follow you.
$ make
will build the objects and stuff in the current path of your source tree.
$ make install copies the executables to the system usable locations.
/usr/bin/ /lib/modules/. /usr/share/doc/.
(which is why you need to be root in a lot of cases to run
Hi Pierre Habraken!
On 2011.06.20 at 19:32:28 +0200, Pierre Habraken wrote next:
> I can imagine that this is a FAQ, but I could not find a clear answer :
> which precise difference(s) distinguish(es) plughw and hw from each other ?
> Does plughw apply sound processing that hw does not ?
plugh
On 06/20/2011 11:52 AM, Pierre Lorenzon wrote:
> Hi,
>
>
>
> From: David Henderson
> Subject: Re: [Alsa-user] First post
> Date: Sun, 19 Jun 2011 15:28:48 -0400
>
>> Thanks for the reply Pierre. I checked into the blfs book, but
>> it merely says "these five chapters will cover alsa" and then
>> g
Hello,
I can imagine that this is a FAQ, but I could not find a clear answer :
which precise difference(s) distinguish(es) plughw and hw from each other ?
Does plughw apply sound processing that hw does not ?
Thanks in advance for any explanation on this subject.
Pierre
--
Dear sender,
You will not receive any more courtesy notices from our members
for two days. Messages you have sent will remain in a lower
priority mailbox for our member to review at their leisure.
Future messages will be more likely to be viewed if you are on
our member's priority Guest List.
Currently there is no alsa installed in the custom distro, so there won't be
any overwritting. :) I just don't want to install the version of alsa I'm
compiling into my running version of Kubuntu because I'd rather use software
from it's package repositories to avoid the headaches mentioned by eve
If you're really into going it on your own. There's gentoo, and
there's LFS aka linux from scratch. Both of which impose a lot of
source compilation. The inherent problem with sources is that you run
into maintenance issues. i.e. If you use the same install for a long
enough time, it'll eventua
Hi Ady, thanks for contributing to the conversation. :) I have a couple
of questions based on your response below...
Why do I need to use the new system for compiling? Isn't there normally
'configure' and 'make' options that allow for compiling on one system so
the software can be packaged fo
Well many source packages default to /usr/local/
Many distros default to /usr/
And the distros IGNORE /usr/local/ unless otherwise told. It's not a
compile thing, it's a runtime thing. Of course you could always run
things with the full paths /usr/local/bin/alsamixer and such. But if
you add t
Thanks again for the continued help James. I knew '--prefix' was a
'configure' option, but thought one would use it when permanently
installing the software to a non-standard directory on the system.
Since this software is being compiled on a temp system and "installing"
to a staging director
hi all,
i have a machine with two pci devices of the same type. how can i ensure
persistent device indices?
the wiki [1] mentions a way for a way using vid/pid, but for pci devices it
suggests to write a udev rule. [2] has an example, but it only describes how to
set up the device names in /de
... or Sorcerer.
James, you need to use the new system for compiling, not some other one.
And how do you install applications on your "custom" system? By .deb
packages?!?! Come on, this is not a custom system! This is exactly what
Pierre said: reinventing the wheel. Like Ubuntu for Debian - who
From: James Shatto
Subject: Re: [Alsa-user] First post
Date: Sun, 19 Jun 2011 15:36:59 -0500
> A) If you want to overwrite your existing distro's versions, you
> probably want the --prefix=/usr option on your ./configure commands.
> If not, be sure to change your $PATH to look at /usr/local FIRST
Hi,
From: David Henderson
Subject: Re: [Alsa-user] First post
Date: Sun, 19 Jun 2011 15:28:48 -0400
> Thanks for the reply Pierre. I checked into the blfs book, but
> it merely says "these five chapters will cover alsa" and then
> gives you a basic "type configure && make". This is obviousl
19 matches
Mail list logo
