Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Stanley <Ben.Stanley@exemail.com.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa-drivers-HEAD does not compile against	recent	RHE5.1 kernels
Date: Thu, 05 Jun 2008 01:38:02 +1000	[thread overview]
Message-ID: <1212593882.28032.123.camel@localhost> (raw)
In-Reply-To: <s5hskvt44eb.wl%tiwai@suse.de>


On Wed, 2008-06-04 at 17:16 +0200, Takashi Iwai wrote:
> At Thu, 05 Jun 2008 01:12:28 +1000,
> Ben Stanley wrote:
> > 
> > So, if config.h is not needed in 'newer' kernels (and causes an error?),
> > and is needed in 'older' kernels, it is then an error to universally
> > include it in a configure test program where it causes an error if used
> > inappropriately...
> 
> Well, apparently it's only RH kernels that cause the problem.
> So I haven't cared about it at all.
> 
> > I think the error is not noticed in newer newer kernels because
> > init_utsname is defined in newer newer kernels. (I should look into this
> > statement some more.)
> 
> The problem is, as usual, RH kernels backported init_utsname in a
> different way than the upstream.  This makes things really hard.
> 
> 
> Takashi

Since its a RH kernel problem, I was hoping to prod a response out of
Jaroslav :-) .

This was a real PITA for us because the sound card manufacturer's
supported build procedure required updating the system ALSA to a
particular version before building their driver. The broken test for the
init_utsname symbol prevented this.

Anyway, in the end I have worked around this issue because I have
successfully compiled the driver in question against the kernel headers
as an external module without the need to use ALSA as a base. This also
makes the configuration more supportable from my point of view, as I
don't have to worry about re-testing everything else that depended on
the original system version of alsa. And getting the driver to compile
against RH kernel 2.6.18-53.1.19 was only really a matter of backporting
it to alsa 1.0.14 , which turned out to be not too hard. This build
procedure also allows me to use dkms to manage the installation of my
driver, which is something of a bonus.

Ben Stanley.

  reply	other threads:[~2008-06-04 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23  1:41 alsa-drivers-HEAD does not compile against recent RHE5.1 kernels Ben Stanley
2008-05-23 11:39 ` Ben Stanley
2008-05-23 12:20   ` Ben Stanley
2008-05-29 23:37     ` Ben Stanley
2008-06-04 12:15       ` Takashi Iwai
2008-06-04 15:12         ` Ben Stanley
2008-06-04 15:16           ` Takashi Iwai
2008-06-04 15:38             ` Ben Stanley [this message]
2008-06-04 16:54             ` Takashi Iwai

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=1212593882.28032.123.camel@localhost \
    --to=ben.stanley@exemail.com.au \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox