couldn't compile without
the option you mentioned above, so I don't think it's a libtool
thing... Anyway:
$ libtool --version
ltmain.sh (GNU libtool) 1.4.2a (1.922.2.100 2002/06/26 07:25:14)
Thanks again!
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages
' where symlinks to
/usr/lib/automake/...' or something to that extent. I copied the ones
from the libs tarball and the compile went fine... but I thought I'd
mention it incase it wasn't mentioned already.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages
prefix is still there.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace of Metallica
http://home.earthlink.net/~jaymzh666/ http://www.ipom.com/
They that can give up essential liberty to obtain a little temporary
safety deserve
Peter Heatwole wrote:
On 2002.10.23 12:52 Phil Dibowitz wrote:
In rc3 my driver was called snd_via686
In rc4 my driver is called snd_via82xx
The snd_ prefix was removed from the module parameters, not the
driver modules themselves (which are prefixed by snd-).
OK... so when I modprobe I
.
For example, if you used modprobe snd-via82xx snd_mpu_port=xxx, it
would now be modprobe snd-via82xx mpu_port=xxx. Or in modules.conf,
it would no longer be options snd-via82xx snd_mpu_port=xxx, it would
now be options snd-via82xx mpu_port=xxx.
Ahhh. Crystal Clear. thanks.
--
Phil Dibowitz
: 2.95.4
I'll gladly provide more info if needed... I just figure proc type and
ram, other software, and the like are a bit unapplicable here. =)
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace of Metallica
http
Phil Dibowitz wrote:
Everytime something (such as an IM) produces sound I got a pop before
the sound, then the sound, then a pop-pop afterwards. It's REALLY
annoying... Is there a way to fix this? Here's some extra info:
After soem more testing, this is only happening in a select group
]: Leaving directory `/home/phil/alsa/alsa-lib-0.9.0rc4/src'
make: *** [all-recursive] Error 1
I'm running a custom 2.4.19 kernel in Debian testing... been running
ALSA 0.9.0rc3 for a few weeks with no major problems.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware
support (provided you tell them
to use their alsa9 drivers, respectively), but if one of them is using
the sound device the other will block waiting for access to the sound
device.
Is this supposed to work? I'm just curious...
Thanks.
--
Phil Dibowitz [EMAIL PROTECTED
to share. For example I can't get alsaplayer and
xmms to play at the same time... but xmms is using its libalsa plugin...
I'm confused... any help would be much appreciated...
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace
to be smart and chose a specific device as its
default...
Thanks!
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
They that can give up essential liberty
Hmmm.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
They that can give up essential liberty to obtain a little temporary
safety deserve neither
Florian Schmidt [EMAIL PROTECTED] wrote:
Phil Dibowitz [EMAIL PROTECTED] wrote:
Clemens Ladisch wrote:
You have to configure all those applications to use the
default
device. In theory, this should be the default (obviously :-) ,
but
it's often something like hw:0 or plughw:0
13 matches
Mail list logo