From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001604]: alsa-utils compilation dies - undefined reference to `snd_mixer_selem_get_capture_dB'
Date: Mon, 28 Nov 2005 19:39:29 +0100 [thread overview]
Message-ID: <7cb4acdf0946d4dacb854eba70ad6a42@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1604>
======================================================================
Reported By: Twey
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 1604
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
Distribution: Fedora Core 4
Kernel Version: 2.6.14-1.1637_FC4
======================================================================
Date Submitted: 11-27-2005 19:39 CET
Last Modified: 11-28-2005 19:39 CET
======================================================================
Summary: alsa-utils compilation dies - undefined reference to
`snd_mixer_selem_get_capture_dB'
Description:
Compilation of alsamixer dies. Full errors attached. Note that the output
given here is using gcc32, but gcc4 gives the same errors.
======================================================================
----------------------------------------------------------------------
tiwai - 11-28-05 19:13
----------------------------------------------------------------------
Did you install to the correct directory? IIRC, FC4 has libasound in /lib.
----------------------------------------------------------------------
Twey - 11-28-05 19:39
----------------------------------------------------------------------
It may not be obvious here, as I mentioned it in the "build" field -- the
"version" field being a <select> box only going up to 1.0.9 -- but I was
trying to compile 1.0.10.
Issue History
Date Modified Username Field Change
======================================================================
11-27-05 19:39 Twey New Issue
11-27-05 19:39 Twey Distribution => Fedora Core 4
11-27-05 19:39 Twey Kernel Version => 2.6.14-1.1637_FC4
11-28-05 18:56 tiwai Note Added: 0006866
11-28-05 19:11 Twey Note Added: 0006867
11-28-05 19:13 tiwai Note Added: 0006868
11-28-05 19:39 Twey Note Added: 0006869
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-11-28 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 18:39 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 9:56 [ALSA - driver 0001604]: alsa-utils compilation dies - undefined reference to `snd_mixer_selem_get_capture_dB' bugtrack
2005-12-08 9:54 bugtrack
2005-12-07 19:45 bugtrack
2005-12-02 13:48 bugtrack
2005-11-28 18:13 bugtrack
2005-11-28 18:11 bugtrack
2005-11-28 17:56 bugtrack
2005-11-27 18:39 bugtrack
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=7cb4acdf0946d4dacb854eba70ad6a42@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox