All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sentinel <sentinel@optonline.net>
To: alsa-devel@alsa-project.org
Subject: spdif/iec958 outputs at VT1708S not recognized
Date: Tue, 26 May 2009 22:57:31 -0400	[thread overview]
Message-ID: <000f01c9de76$e100e810$a302b830$@net> (raw)

Okay I figured out my own problem. 

 

This is specific to those who run 64bit OS.

 

for anyone who is getting register_sound_special_device error when
attempting to compile ALSA, on a 64 bit OS make sure your running your
configure properly.  Most likely your distro has ALSA libraries located in
the /usr/lib64 path not in /usr/lib and most likely the ld.so.conf is set to
look in /usr/lib64 before it searches /usr/lib which is the default for  the
configure script.  As a warning I'd not try to change that order especially
if you have built any 32bit compatibility drivers into /usr/lib

 

./configure -prefix=/usr/lib64

 

Although it wouldn't be a bad idea for the configure to detect that if
possible.

             reply	other threads:[~2009-05-27  2:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  2:57 Sentinel [this message]
2009-05-27  5:35 ` spdif/iec958 outputs at VT1708S not recognized Takashi Iwai
     [not found]   ` <003401c9dee9$322399f0$966acdd0$@net>
2009-05-27 16:51     ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2009-05-27  3:19 Sentinel
2009-05-26 14:24 Sentinel
2009-05-26  3:04 Sentinel
2009-05-24  4:24 linux user
2009-04-29 12:25 Peter Niemayer
2009-04-29 15:07 ` Takashi Iwai
2009-05-05 10:48   ` Peter Niemayer
2009-05-07 14:17     ` Takashi Iwai
2009-05-07 14:17     ` Takashi Iwai
2009-05-08  9:21       ` Peter Niemayer
2009-05-08  9:30         ` Takashi Iwai
2009-05-11  8:56           ` Peter Niemayer
2009-04-29 15:19 ` David Douglas
2009-04-29 16:41   ` Vedran Miletić

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='000f01c9de76$e100e810$a302b830$@net' \
    --to=sentinel@optonline.net \
    --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.