From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000005]: alsa-driver-1.0.2: unresolved symbols in snd.o
Date: Tue, 27 Jan 2004 22:18:57 +0100 (CET) [thread overview]
Message-ID: <20040127211857.44EAB25009@server.perex-int.cz> (raw)
A BUGNOTE has been added to this bug.
======================================================================
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000005
======================================================================
Reporter: ZlatkO
Handler: perex
======================================================================
Project: ALSA - driver
Bug ID: 5
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: block
Priority: immediate
Status: assigned
Distribution: Slackware 8.1
Kernel Version: 2.4.24
======================================================================
Date Submitted: 01-27-2004 21:31 CET
Last Modified: 01-27-2004 22:18 CET
======================================================================
Summary: alsa-driver-1.0.2: unresolved symbols in snd.o
Description:
snd.o fails to load due to an unresolved symbol ("sound_class") on a
Slackware 8.1 system, kernel 2.4.24 (plain vanilla from kernel.org),
modutils-2.4.16.
There is no "sound_class" in the kernel's own
/usr/src/linux-2.4.24/drivers/sound/sound_core.c - am I supposed to
replace it with alsa-kernel/sound_core.c? This was not necessary in
previous ALSA versions.
======================================================================
----------------------------------------------------------------------
perex - 01-27-2004 22:08 CET
----------------------------------------------------------------------
I cannot reproduce this bug, but it might be possible that removing
of line 'extern struct class_simple *sound_class;' in
alsa-driver/alsa-kernel/core/sound.c solves this bug.
Can you confirm?
I've recreated new alsa-driver package with date:
Jan 27 22:02 alsa-driver-1.0.2.tar.bz2
----------------------------------------------------------------------
khali - 01-27-2004 22:18 CET
----------------------------------------------------------------------
Doesn't work for me. Even worse, alsa-driver doesn't compile anymore after
I commented the line out:
sound.c: In function `snd_register_device_R1f4c5f07':
sound.c:239: `sound_class' undeclared (first use in this function)
sound.c:239: (Each undeclared identifier is reported only once
sound.c:239: for each function it appears in.)
sound.c: In function `alsa_sound_init':
sound.c:376: `sound_class' undeclared (first use in this function)
sound.c: At top level:
sound.c:41: warning: `device_mode' defined but not used
make[1]: *** [sound.o] Error 1
make[1]: Leaving directory `/usr/src/alsa-driver-1.0.2/acore'
make: *** [compile] Error 1
Bug History
Date Modified Username Field Change
======================================================================
01-27-04 21:31 ZlatkO New Bug
01-27-04 22:08 perex Bugnote Added: 0000005
01-27-04 22:08 perex Assigned To => perex
01-27-04 22:08 perex Status new => assigned
01-27-04 22:08 perex Priority normal => immediate
01-27-04 22:15 perex Category CORE - control => 0_compilation problem_!!!
01-27-04 22:18 khali Bugnote Added: 0000007
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-01-27 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 21:18 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-28 6:57 [ALSA - driver 0000005]: alsa-driver-1.0.2: unresolved symbols in snd.o noreply
2004-01-27 21:48 noreply
2004-01-27 21:48 noreply
2004-01-27 21:37 noreply
2004-01-27 21:08 noreply
2004-01-27 21:08 noreply
2004-01-27 20:31 noreply
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=20040127211857.44EAB25009@server.perex-int.cz \
--to=noreply@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 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.