From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001146]: Cannot compile alsa-utils
Date: Mon, 30 May 2005 15:06:23 +0200 [thread overview]
Message-ID: <861bce20bea4f5e3652f7892c3f501e5@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1146>
======================================================================
Reported By: Cimmo
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 1146
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution: Fedora Core 4 test3
Kernel Version: 2.6.11-1.1363_FC4-x86_64 (contains 2.6.12rc5)
======================================================================
Date Submitted: 05-30-2005 15:06 CEST
Last Modified: 05-30-2005 15:06 CEST
======================================================================
Summary: Cannot compile alsa-utils
Description:
Compiling alsa-utils 1.0.9 with gcc 4.0.0 I've this error:
Making all in alsactl
make[1]: Entering directory
`/home/cimmo/updates/alsa-utils-1.0.9/alsactl'
gcc -g -O2 -o alsactl alsactl.o state.o power.o names.o -lasound -lm
-ldl -lpthread
names.o(.text+0xdce): In function `probe_timers':
/home/cimmo/updates/alsa-utils-1.0.9/alsactl/names.c:425: undefined
reference to `snd_timer_ginfo_sizeof'
names.o(.text+0xdee):/home/cimmo/updates/alsa-utils-1.0.9/alsactl/names.c:425:
undefined reference to `snd_timer_ginfo_sizeof'
names.o(.text+0xe4e):/home/cimmo/updates/alsa-utils-1.0.9/alsactl/names.c:435:
undefined reference to `snd_timer_ginfo_set_tid'
names.o(.text+0xebf):/home/cimmo/updates/alsa-utils-1.0.9/alsactl/names.c:445:
undefined reference to `snd_timer_ginfo_get_name'
collect2: ld returned 1 exit status
make[1]: *** [alsactl] Error 1
make[1]: Leaving directory `/home/cimmo/updates/alsa-utils-1.0.9/alsactl'
make: *** [all-recursive] Error 1
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
05-30-05 15:06 Cimmo New Issue
05-30-05 15:06 Cimmo Distribution => Fedora Core 4 test3
05-30-05 15:06 Cimmo Kernel Version =>
2.6.11-1.1363_FC4-x86_64 (contains 2.6.12rc5)
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next reply other threads:[~2005-05-30 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 13:06 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-30 13:11 [ALSA - driver 0001146]: Cannot compile alsa-utils bugtrack
2005-05-30 13:36 bugtrack
2005-05-31 10:52 bugtrack
2005-05-31 11:03 bugtrack
2005-05-31 11:04 bugtrack
2005-05-31 11:27 bugtrack
2005-06-01 14:52 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=861bce20bea4f5e3652f7892c3f501e5@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