Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 7138 - alsa-driver compiled with gcc3.2 resulted in unresolved symbols
Summary: alsa-driver compiled with gcc3.2 resulted in unresolved symbols
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: Highest critical (vote)
Assignee: Brandon Low (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-27 16:26 UTC by Joshua Bergland
Modified: 2003-02-04 19:42 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Bergland 2002-08-27 16:26:04 UTC
I have emerged alsa-driver using gcc3.2 against the current gentoo-sources
kernel. The drivers are compiled with any problems and the emerge is completed
fine. However, upon trying to use the module, it results in a few errors stating
'unresolved sysmbol' and the module fails to load.

I tried this multiple time, making sure that it wasn't an issue with a kernel
that was recompiled. Always results in the same error.

The command I am using to load the module - insmod snd-ens1371

Doing lsmod lists that the dependent modules are loaded, just the sound card
driver fails.
Comment 1 Bjarke Istrup Pedersen (RETIRED) gentoo-dev 2002-08-27 16:29:59 UTC
I have the same problem, right now i'm reinstalling gentoo.
Within a few days, I will get some new discs, and I will reinstall it.
If it makes the same problems, I will post a lot detailed comment.
Comment 2 Joshua Bergland 2002-08-28 11:12:37 UTC
One additional note: I built this system with stage1-x86-1.4.tbz2 from the
.1.4/x86 directory on ftp.ibiblio.org
Comment 3 Arcady Genkin (RETIRED) gentoo-dev 2002-09-01 14:55:28 UTC
I don't have a system with gcc-3.2 to try to replicate this.  Unfortunately, I'm
using gcc-2.95 on all my computers (and not intending to switch in the nearest
future); I have not had any problems as in this bug report (I'm using the ALSA
module for ens1371 chip on one of my boxes).

Perhaps our GCC-3.2 team is a better assignee for this bug (punting back to
bug-wranglers).
Comment 4 Seemant Kulleen (RETIRED) gentoo-dev 2002-09-01 16:21:52 UTC
sorry lolo, to keep piling stuff on you :(
Comment 5 Brandon Low (RETIRED) gentoo-dev 2002-09-02 21:36:12 UTC
I need more specific modprobe output, can you please also test this after
updating to lolo-sources-2.4.19.9_rc2.  Please also post your glibc and gcc
versions.
Comment 6 Artur Brodowski 2002-09-04 13:26:27 UTC
are you sure you recompiled your kernel first with gcc 3.2?
did you recompile glibc as well?
this could happen if kernel and modules are compiled with different gcc versions.
i recently upgraded gcc on my box (2.95.3->3.2) and my alsa drivers (remerged
after i recompiled kernel) work fine...
Comment 7 Brandon Low (RETIRED) gentoo-dev 2002-10-21 18:16:58 UTC
I squish bug, original reporter hasn't responded in a long time and it was most 
likely a pebkac in the first place.