From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manuel Jander Subject: Unresolved symbol Date: Tue, 5 Jul 2005 14:04:55 +0200 Message-ID: <21ed1c3705070505042d503a58@mail.gmail.com> Reply-To: Manuel Jander Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by alsa.jcu.cz (ALSA's E-mail Delivery System) with ESMTP id 7DC731A7 for ; Tue, 5 Jul 2005 14:04:56 +0200 (MEST) Received: by rproxy.gmail.com with SMTP id z35so837584rne for ; Tue, 05 Jul 2005 05:04:55 -0700 (PDT) Content-Disposition: inline Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org 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, --=20 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_id=7477&alloc_id=16492&op=click