All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org, Michael Krufky <mkrufky@linuxtv.org>
Subject: Re: [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: OK
Date: Wed, 30 Dec 2009 00:17:36 +0100	[thread overview]
Message-ID: <4B3A8E10.9000609@freemail.hu> (raw)
In-Reply-To: <4B3A86ED.1090303@redhat.com>

Mauro Carvalho Chehab írta:
> Németh Márton wrote:
>> Hans Verkuil wrote:
>>> Detailed results are available here:
>>>
>>> http://www.xs4all.nl/~hverkuil/logs/Tuesday.log
>> linux-2.6.33-rc2-armv5: ERRORS
>>
>> In file included from <command-line>:0:
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28: error: linux/autoconf.h: No such file or directory
>> In file included from <command-line>:0:
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28: In file included from <command-line>:0error: :
>> linux/autoconf.h: No such file or directory
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28:In file included from <command-line>:0 error: :
>> linux/autoconf.h: No such file or directory
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28: error: linux/autoconf.h: No such file or directory
>> In file included from <command-line>:0:
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28: error: linux/autoconf.h: No such file or directory
>> In file included from <command-line>:0:
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28: error: linux/autoconf.h: No such file or directory
>> In file included from <command-line>:0:
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28: error: linux/autoconf.h: No such file or directory
>> In file included from <command-line>:0:
>> /marune/build/v4l-dvb-master/v4l/config-compat.h:4:28: error: linux/autoconf.h: No such file or directory
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dvb_filter.o] Error 1
>> make[3]: *** Waiting for unfinished jobs....
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dvbdev.o] Error 1
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dvb_ringbuffer.o] Error 1
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dvb_ca_en50221.o] Error 1
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dmxdev.o] Error 1
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dvb_demux.o] Error 1
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dvb_frontend.o] Error 1
>> make[3]: *** [/marune/build/v4l-dvb-master/v4l/dvb_net.o] Error 1
>> make[2]: *** [_module_/marune/build/v4l-dvb-master/v4l] Error 2
>> make[2]: Leaving directory `/marune/build/trees/armv5/linux-2.6.33-rc2'
>> make[1]: *** [default] Error 2
>> make[1]: Leaving directory `/marune/build/v4l-dvb-master/v4l'
>> make: *** [all] Error 2
>> Tue Dec 29 19:01:02 CET 2009
>>
>> This problem happens because the v4l/config-compat.h includes the
>> linux/autoconf.h . This file is generated by v4l/scripts/make_config_compat.pl .
>>
>> I found different commits where the inclusion of this file was
>> completely removed, like in
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=911f21501f50b16ce77f37b01e90b5b73c8c80bf .
>> I doubt whether the line should be completely deleted or a construct
>> like this should be used:
>>
>> #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 33)
>> #include <linux/autoconf.h>
>> #endif
>>
>> What do you think?
> 
> If I'm not mistaken, Michael included this file at the building system,
> since some drivers need to do some checks against some CONFIG_foo symbols that
> are needed to compile certain drivers.
> 
> By removing it, it may break some compilations. So, while I'm not quite sure
> what should be done to fix the issue, just removing it seems to me that it will
> cause some regression.

Maybe the following construct would be the right one:

#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 33)
#include <linux/autoconf.h>
#else
#include <generated/autoconf.h>
#endif

Regards,

	Márton Németh

  reply	other threads:[~2009-12-29 23:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 19:59 [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: OK Hans Verkuil
2009-12-29 21:21 ` Németh Márton
2009-12-29 22:47   ` Mauro Carvalho Chehab
2009-12-29 23:17     ` Németh Márton [this message]
2009-12-31 11:19       ` [PATCH] move autoconf.h for 2.6.33 Németh Márton
  -- strict thread matches above, loose matches on Subject: below --
2009-12-30 19:55 [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: OK Hans Verkuil
2009-12-31 19:50 Hans Verkuil
2010-01-01 19:50 Hans Verkuil
2010-01-02 19:50 Hans Verkuil
2010-01-03 19:50 Hans Verkuil
2010-01-04 19:50 Hans Verkuil
2010-01-05 19:50 Hans Verkuil
2010-01-06 19:50 Hans Verkuil
2010-01-07 19:50 Hans Verkuil
2010-01-08 19:50 Hans Verkuil
2010-01-09 19:50 Hans Verkuil
2010-01-10 19:58 Hans Verkuil
2010-01-11 19:58 Hans Verkuil
2010-01-12 19:58 Hans Verkuil
2010-01-13 19:58 Hans Verkuil
2010-03-01 19:53 Hans Verkuil
2010-03-02 19:52 Hans Verkuil
2010-03-06 19:52 Hans Verkuil
2010-03-07  5:49 ` Németh Márton
2010-03-07  9:52   ` Hans Verkuil
2010-03-07 12:20 ` Németh Márton
2010-03-07 12:29   ` Hans Verkuil
2010-03-07 13:00     ` Németh Márton
2010-03-07 20:05 Hans Verkuil
2010-03-08 20:05 Hans Verkuil
2010-03-10 20:30 Hans Verkuil

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=4B3A8E10.9000609@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=mkrufky@linuxtv.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 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.