Unresolved symbol
Building a pure USB alsa-driver set, I encountered the following situation (ARM target):
The function snd_compat_strlcpy() does sometimes not get build when only USB devices (no memory_wrapper.o being build). I guess this function should go elsewhere.
The result: unresolved symbols: snd_compat_strlcpy()
Best Regards,
Signature · 8 lines
Manuel Jander ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
At Tue, 5 Jul 2005 14:04:55 +0200,
Quoted 9 lines · Manuel Jander
Building a pure USB alsa-driver set, I encountered the following situation (ARM target):
The function
snd_compat_strlcpy()does sometimes not get build when only USB devices (no memory_wrapper.o being build). I guess this function should go elsewhere.The result: unresolved symbols:
snd_compat_strlcpy()
Which ALSA version? Did you try CVS?
Takashi
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
A message that is not in the archive (sent off-list or not yet received): [email protected]
At Tue, 5 Jul 2005 15:48:08 +0200,
Quoted 10 lines · Manuel Jander
Hi Takashi,
CVS, the same thing.... Somehow I believe that some few functions in acore are not were they should be. Indeed, some don't get exported because they seem to be in the wrong place: "EXPORT" statement in a different file than the function declaration.
I'm compiling with the WRTG54 (armv4b-hardhat-linux) toolchain. That fact may be providing more fun than necesary too (but its my job to do this kind of stuff).
Is it 2.4 or 2.6 based?
Quoted 4 lines
Compiling with only a usb-audio card, triggers the the problems I am encountering.
If I get something working, I will let you know. If there is any known stuff about I would be very interested to know.
memory_wrapper.c is a part of snd-page-alloc module and always built when PCM is selected. This means that usb-audio also must enable the compilation of memory_wrapper.c.
My rough guess was that configure script failed to detect the strlcpy, but I'm not sure now. Anyway check include/config.h.
Takashi
Quoted 15 lines
Best Regards,
ManuelQuoted 10 lines · Takashi Iwai
At Tue, 5 Jul 2005 14:04:55 +0200,
Quoted 8 lines · Manuel Jander
Building a pure USB alsa-driver set, I encountered the following situation (ARM target):
The function
snd_compat_strlcpy()does sometimes not get build when only USB devices (no memory_wrapper.o being build). I guess this function should go elsewhere.
Quoted 13 lines
Quoted 7 lines
Quoted 1 line
The result: unresolved symbols:
snd_compat_strlcpy()Which ALSA version? Did you try CVS?
Takashi
Signature · 2 lines
Manuel Jander Electronic Engineer
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click