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

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

> I think it comes down to figuring out the point between 'newer' and
> 'older' kernels and modifying the configure test appropriately to use or
> not use config.h as required. I'm not sure how that should be done.
> 
> Ben.
> 
> On Wed, 2008-06-04 at 14:15 +0200, Takashi Iwai wrote:
> > At Fri, 30 May 2008 09:37:43 +1000,
> > Ben Stanley wrote:
> > > 
> > > [PING] 
> > > 
> > > I need some help on this one. I don't know how to determine whether or
> > > not the config.h file should be included in the test program or not.
> > 
> > config.h is needed for older kernels indeed.
> > 
> > 
> > Takashi
> > 
> > > 
> > > Ben Stanley.
> > > 
> > > On Fri, 2008-05-23 at 22:20 +1000, Ben Stanley wrote:
> > > > Further to my previous email,
> > > > 
> > > > The config.log file shows the following output for the test for
> > > > init_utsname in the case of the RHEL 5.1 kernel 2.6.18-53.1.19:
> > > > 
> > > > configure:10792: checking for init_utsname
> > > > configure:10822: gcc -c -Wall -fno-strict-aliasing -g -O2
> > > > -I/lib/modules/2.6.18-53.1.19.el5/build/include
> > > > -I/lib/modules/2.6.18-53.1.19.el5/source/include  -Iinclude -nostdinc
> > > > -iwithprefix include -DKBUILD_STR(s)=#s
> > > > -DKBUILD_BASENAME=KBUILD_STR(dummy) -DKBUILD_MODNAME=KBUILD_BASENAME
> > > > -Werror  conftest.c >&5
> > > > In file included from conftest.c:52:
> > > > /lib/modules/2.6.18-53.1.19.el5/build/include/linux/config.h:6:2: error:
> > > > #warning Including config.h is deprecated.
> > > > configure:10828: $? = 1
> > > > configure: failed program was:
> > > > 
> > > > I think it is failing because of the config.h warning.
> > > > 
> > > > Ben Stanley.
> > > > 
> 

  reply	other threads:[~2008-06-04 15:16 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 [this message]
2008-06-04 15:38             ` Ben Stanley
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=s5hskvt44eb.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=Ben.Stanley@exemail.com.au \
    --cc=alsa-devel@alsa-project.org \
    /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