All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus-Peter Schrage <kpschrage@gmx.de>
To: Kristof vansant <de_lupus@pandora.be>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa-drivers can't make on kernel 2.6 because of broken vx driver
Date: Tue, 06 Jan 2004 19:03:02 +0100	[thread overview]
Message-ID: <3FFAF856.2020901@gmx.de> (raw)
In-Reply-To: <1073392202.2633.4.camel@d51528079.kabel.telenet.be>

Kristof vansant wrote:
> I don't know how alsa patches drivers when it has to compile on kernel
> 2.6, so I don't know how to fix it. 
> 
> I think lot of kernel 2.6 users would be gratefull if you fixed this
> issue. 
> 
>   CC [M]  /home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.o
> /home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:6:31:
> linux/modversions.h: Onbekend bestand of map

My Dutch is a bit rusty, but I guess the last line expresses that 
modversions.h is missing. As far as I remember, this is created during 
the kernel build process. So, is this a virgin kernel source which 
hasn't been configured and compiled yet?
Klaus



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

  parent reply	other threads:[~2004-01-06 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 12:30 alsa-drivers can't make on kernel 2.6 because of broken vx driver Kristof vansant
2004-01-06 13:56 ` Ed Wildgoose
2004-01-06 14:27   ` Kristof vansant
2004-01-06 18:03 ` Klaus-Peter Schrage [this message]
2004-01-06 18:29   ` Kristof vansant
2004-01-06 19:01     ` Klaus-Peter Schrage

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=3FFAF856.2020901@gmx.de \
    --to=kpschrage@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=de_lupus@pandora.be \
    /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.