From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Fw: Build failed in Jenkins: buildroot » raspberrypi_defconfig #320
Date: Mon, 4 Aug 2014 23:08:50 +0200 [thread overview]
Message-ID: <20140804210850.GH3875@free.fr> (raw)
In-Reply-To: <XnsA37FDED614C14berndkuhlsPkbjNfxxIA@bernd-kuhls.de>
Bernd, All,
On 2014-08-04 21:54 +0200, Bernd Kuhls spake thusly:
> Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote
> in news:20140804084458.60f38d5d at free-electrons.com:
>
> > cannot stat
> > '<http://jenkins.free-electrons.com/job/buildroot/./config=raspberrypi_de
> > fconfig/ws/output/build/linux-0b8e8118dd2c9440bb7a2da1a19e15e324d3c09b/ar
> > ch/arm/configs/bcmrpi_quick_defconfig'>: No such file or directory make:
>
> sent a patch to bump kernel again:
> http://patchwork.ozlabs.org/patch/376429/
>
> There is a, imho, weird thing about the git repo for raspberry linux:
>
> Looking at the two last commits in
> https://github.com/raspberrypi/linux/commits/rpi-3.12.y
>
> - Linux 3.12.26
> d83a3234d2e1e2a55e7f2430fc9ca29a9bd315e7
>
> and
>
> - Merge remote-tracking branch 'stable/linux-3.12.y' into rpi-3.12.y
> 353043394c99ed37a4075da228af64468fdf6c06
>
> The former does not contain bcmrpi_quick_defconfig
> https://github.com/raspberrypi/linux/tree/d83a3234d2e1e2a55e7f2430fc9ca29a9
> bd315e7/arch/arm/configs
>
> The later one contains bcmrpi_quick_defconfig however
> https://github.com/raspberrypi/linux/tree/353043394c99ed37a4075da228af64468
> fdf6c06/arch/arm/configs
>
> although the commit
> https://github.com/raspberrypi/linux/commit/7b45dd4ca24cd47b5cfa887934ed7d2
> fa420e6d4 introducing the file contains the tag rpi-3.12.y, according to
> the github web interface.
>
> Maybe I have yet to learn something about github, but now the kernel
> compiles again, still does Kodi 14.0a2-Helix.
That's becasue you mixed the tags from the stable branch with the cset
from the "rpi-stable" branch.
Your previous sha1, 0b8e8118dd2c9440bb7a2da1a19e15e324d3c09b, is the
v3.12.25 tag, that is, not on the rpi branch, but in the stable kernel
tree.
That tag was merged into the rpi tree as of cset
09f2fa2f3fb1f9df126c03c160f9457e2fb14489
For you new patch, you correctly use the sha1 from the merge tag.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-08-04 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 6:44 [Buildroot] Fw: Build failed in Jenkins: buildroot » raspberrypi_defconfig #320 Thomas Petazzoni
2014-08-04 19:54 ` Bernd Kuhls
2014-08-04 21:08 ` Yann E. MORIN [this message]
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=20140804210850.GH3875@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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