From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Douglas Schilling Landgraf <dougsland@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [cron job] v4l-dvb daily build 2.6.26 and up: ERRORS
Date: Thu, 28 Oct 2010 20:01:52 +0200 [thread overview]
Message-ID: <4CC9BA90.2080805@hoogenraad.net> (raw)
In-Reply-To: <4CC94D5A.3090504@redhat.com>
Douglas:
First of all thank you for the support you have done so far.
Hans:
Is it possible to build the tar from
http://git.linuxtv.org/mchehab/new_build.git
automatically each night, just like the way the hg archive was built ?
I don't have sufficient processing power to run that.
Mauro:
I'm willing to give the mercurial conversion a shot.
I do not know a lot about v4l, but tend to be able to resolve this kind
of release-type issues.
The way it seems to me is that first new_build.git should compile for
all releases that the hg archive supported.
Then I'd like some support from you as to transfer all current HG
branches to the git line. In principle, that should be fixed by the
maintainers. If the new_build.git complies well, that should be
relatively straightforward.
For me, it would be great if Mauro could transfer these branches
automatically at that time to git.
Mauro Carvalho Chehab wrote:
> Hi Hans,
>
> Provided that we're without a maintainer for Mercurial tree, I doubt that anyone would
> fix the problems there. So, I think you should disable the mercurial build reports,
> while we don't have any backport tree maintainer.
>
> Cheers,
> Mauro
>
> Em 27-10-2010 17:05, Hans Verkuil escreveu:
>> This message is generated daily by a cron job that builds v4l-dvb for
>> the kernels and architectures in the list below.
>>
>> Results of the daily build of v4l-dvb:
>>
>> date: Wed Oct 27 19:00:19 CEST 2010
>> path: http://www.linuxtv.org/hg/v4l-dvb
>> changeset: 15167:abd3aac6644e
>> git master: 3e6dce76d99b328716b43929b9195adfee1de00c
>> git media-master: a348e9110ddb5d494e060d989b35dd1f35359d58
>> gcc version: i686-linux-gcc (GCC) 4.5.1
>> host hardware: x86_64
>> host os: 2.6.32.5
>>
>> linux-git-armv5: WARNINGS
>> linux-git-armv5-davinci: WARNINGS
>> linux-git-armv5-ixp: WARNINGS
>> linux-git-armv5-omap2: WARNINGS
>> linux-git-i686: WARNINGS
>> linux-git-m32r: WARNINGS
>> linux-git-mips: WARNINGS
>> linux-git-powerpc64: WARNINGS
>> linux-git-x86_64: WARNINGS
>> linux-2.6.32.6-armv5: WARNINGS
>> linux-2.6.33-armv5: WARNINGS
>> linux-2.6.34-armv5: WARNINGS
>> linux-2.6.35.3-armv5: WARNINGS
>> linux-2.6.32.6-armv5-davinci: ERRORS
>> linux-2.6.33-armv5-davinci: ERRORS
>> linux-2.6.34-armv5-davinci: ERRORS
>> linux-2.6.35.3-armv5-davinci: ERRORS
>> linux-2.6.32.6-armv5-ixp: ERRORS
>> linux-2.6.33-armv5-ixp: ERRORS
>> linux-2.6.34-armv5-ixp: ERRORS
>> linux-2.6.35.3-armv5-ixp: ERRORS
>> linux-2.6.32.6-armv5-omap2: ERRORS
>> linux-2.6.33-armv5-omap2: ERRORS
>> linux-2.6.34-armv5-omap2: ERRORS
>> linux-2.6.35.3-armv5-omap2: ERRORS
>> linux-2.6.26.8-i686: WARNINGS
>> linux-2.6.27.44-i686: WARNINGS
>> linux-2.6.28.10-i686: WARNINGS
>> linux-2.6.29.1-i686: WARNINGS
>> linux-2.6.30.10-i686: WARNINGS
>> linux-2.6.31.12-i686: WARNINGS
>> linux-2.6.32.6-i686: WARNINGS
>> linux-2.6.33-i686: WARNINGS
>> linux-2.6.34-i686: WARNINGS
>> linux-2.6.35.3-i686: WARNINGS
>> linux-2.6.32.6-m32r: WARNINGS
>> linux-2.6.33-m32r: WARNINGS
>> linux-2.6.34-m32r: WARNINGS
>> linux-2.6.35.3-m32r: WARNINGS
>> linux-2.6.32.6-mips: WARNINGS
>> linux-2.6.33-mips: WARNINGS
>> linux-2.6.34-mips: WARNINGS
>> linux-2.6.35.3-mips: WARNINGS
>> linux-2.6.32.6-powerpc64: WARNINGS
>> linux-2.6.33-powerpc64: WARNINGS
>> linux-2.6.34-powerpc64: WARNINGS
>> linux-2.6.35.3-powerpc64: WARNINGS
>> linux-2.6.26.8-x86_64: WARNINGS
>> linux-2.6.27.44-x86_64: WARNINGS
>> linux-2.6.28.10-x86_64: WARNINGS
>> linux-2.6.29.1-x86_64: WARNINGS
>> linux-2.6.30.10-x86_64: WARNINGS
>> linux-2.6.31.12-x86_64: WARNINGS
>> linux-2.6.32.6-x86_64: WARNINGS
>> linux-2.6.33-x86_64: WARNINGS
>> linux-2.6.34-x86_64: WARNINGS
>> linux-2.6.35.3-x86_64: WARNINGS
>> spec-git: OK
>> sparse: ERRORS
>>
>> Detailed results are available here:
>>
>> http://www.xs4all.nl/~hverkuil/logs/Wednesday.log
>>
>> Full logs are available here:
>>
>> http://www.xs4all.nl/~hverkuil/logs/Wednesday.tar.bz2
>>
>> The V4L-DVB specification from this daily build is here:
>>
>> http://www.xs4all.nl/~hverkuil/spec/media.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
next prev parent reply other threads:[~2010-10-28 18:02 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 19:05 [cron job] v4l-dvb daily build 2.6.26 and up: ERRORS Hans Verkuil
2010-10-28 10:15 ` Mauro Carvalho Chehab
2010-10-28 18:01 ` Jan Hoogenraad [this message]
2010-10-28 18:52 ` Mauro Carvalho Chehab
2010-10-29 16:05 ` Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2010-10-30 19:05 Hans Verkuil
2010-10-29 19:05 Hans Verkuil
2010-10-28 19:04 Hans Verkuil
2010-10-26 19:05 Hans Verkuil
2010-10-25 19:05 Hans Verkuil
2010-10-24 19:05 Hans Verkuil
2010-10-23 19:05 Hans Verkuil
2010-10-22 19:04 Hans Verkuil
2010-10-21 19:05 Hans Verkuil
2010-10-20 19:05 Hans Verkuil
2010-10-19 19:05 Hans Verkuil
2010-10-18 19:05 Hans Verkuil
2010-10-17 19:04 Hans Verkuil
2010-10-16 19:05 Hans Verkuil
2010-10-15 19:04 Hans Verkuil
2010-10-14 19:05 Hans Verkuil
2010-10-13 19:05 Hans Verkuil
2010-10-12 19:04 Hans Verkuil
2010-10-11 19:04 Hans Verkuil
2010-10-10 19:04 Hans Verkuil
2010-10-09 19:04 Hans Verkuil
2010-10-08 19:05 Hans Verkuil
2010-10-07 19:09 Hans Verkuil
2010-10-06 19:09 Hans Verkuil
2010-10-05 19:09 Hans Verkuil
2010-10-04 19:09 Hans Verkuil
2010-10-03 19:09 Hans Verkuil
2010-10-02 19:15 Hans Verkuil
2010-10-03 18:06 ` Hans Verkuil
2010-10-01 19:25 Hans Verkuil
2010-09-30 19:11 Hans Verkuil
2010-09-29 19:11 Hans Verkuil
2010-09-28 19:11 Hans Verkuil
2010-09-27 19:11 Hans Verkuil
2010-09-26 19:11 Hans Verkuil
2010-09-25 19:11 Hans Verkuil
2010-09-24 19:11 Hans Verkuil
2010-09-23 19:11 Hans Verkuil
2010-09-22 19:07 Hans Verkuil
2010-09-21 19:07 Hans Verkuil
2010-09-20 19:07 Hans Verkuil
2010-09-19 19:08 Hans Verkuil
2010-09-18 19:03 Hans Verkuil
2010-09-17 19:03 Hans Verkuil
2010-09-16 19:03 Hans Verkuil
2010-09-15 17:06 Hans Verkuil
2010-09-14 19:03 Hans Verkuil
2010-09-13 19:03 Hans Verkuil
2010-09-12 19:04 Hans Verkuil
2010-09-11 19:04 Hans Verkuil
2010-09-10 19:07 Hans Verkuil
2010-09-09 19:07 Hans Verkuil
2010-09-08 19:07 Hans Verkuil
2010-09-07 19:07 Hans Verkuil
2010-09-06 19:08 Hans Verkuil
2010-09-05 19:07 Hans Verkuil
2010-09-04 19:07 Hans Verkuil
2010-09-03 19:07 Hans Verkuil
2010-09-02 18:55 Hans Verkuil
2010-09-01 18:55 Hans Verkuil
2010-08-31 18:55 Hans Verkuil
2010-08-30 18:54 Hans Verkuil
2010-08-29 18:55 Hans Verkuil
2010-08-28 18:54 Hans Verkuil
2010-08-27 18:55 Hans Verkuil
2010-08-26 18:56 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=4CC9BA90.2080805@hoogenraad.net \
--to=jan-conceptronic@hoogenraad.net \
--cc=dougsland@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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.