From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mario Loritz Subject: Re: alsa-driver-1.0.6a unresolved symbol Date: Sun, 10 Oct 2004 00:29:48 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <200410100029.48457.loritz@fh-furtwangen.de> References: <200410091113.32047.loritz@fh-furtwangen.de> <20041009145905.1fcf393a@mango.fruits.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20041009145905.1fcf393a@mango.fruits.de> Content-Disposition: inline Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Am Samstag, 9. Oktober 2004 14:59 schrieb Florian Schmidt: > On Sat, 9 Oct 2004 11:13:32 +0200 > > Mario Loritz wrote: > > I think I've seen this error before in an earlier version of alsa. > > There, it could be fixed... > > I don't think this is an alsa error. This is rather a module build error. > Make sure your kernel source tree is in a suitable state for building > modules against it. > > flo Could you, in short words, explain why alsa-1.0.5 compiles just fine and alsa-1.0.6 doesn't? And yes, the last time I observed this error it was gone with a new alsa release. Greetings Mario Loritz ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl