From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Bug report or teaching moment -- downloading kernel patches
Date: Sat, 30 Dec 2017 18:10:21 +0100 [thread overview]
Message-ID: <20171230171021.GG2921@scaer> (raw)
In-Reply-To: <CAF_dkJCrv_M-bXkXGtoY0esM6GS_MW6+Pjeb9aJWUCRFstST8A@mail.gmail.com>
Patrick, All,
On 2017-12-30 11:32 -0500, Patrick Doyle spake thusly:
> I can't figure this out...am I doing something wrong or have I uncovered a bug?
Bug.
It's a known bug, where extra downloads are not downloaded when the main
download is something that is not a tarball.
And for atmel_sama5d27_som1_ek_mmc_dev_defconfig, the kernel is from a
git tree, so is not downloaded with wget, so the extra dowenloads are
not downloaded.
Regards,
Yann E. MORIN.
> $ export BR2_DL_DIR=
> # (make sure we start with an empty download directory)
> $ git clone git://git.buildroot.net/buildroot buildroot.test
> # (I am working with master=2a604ddcd8d8bf093cdedaefc074a8c61933a4b6
> from a few days ago)
> $ cd buildroot.test
> $ make atmel_sama5d27_som1_ek_mmc_dev_defconfig
> $ make menuconfig
> -- navigate to Kernel ---> Custom kernel patches
> -- enter https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.9/patches-4.9.61-rt61.tar.gz
> -- Exit, Exit, Exit, save changes, etc...
> $ make linux-patch
>
> When I do this, a kernel gets downloaded, but no patches get applied.
> If I follow that up with
>
> $ cd dl
> $ wget https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.9/patches-4.9.61-rt61.tar.gz
> $ cd ..
> $ make linux-dirclean
> $ make linux-patch
>
> The patches I manually downloaded get applied.
>
> Can somebody help me figure out what's going on here? From everything
> I've read (and from Yann's email earlier), I would expect the patch
> file to be downloaded by the machinery.
>
> If it makes any difference, I have attached the .config file from my build.
> Also, for full disclosure, as I just tried this again, I didn't
> actually clone from git://git.buildroot.net, I cloned from my existing
> (unmodified) buildroot directory, just to save some time.
>
> --wpd
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-12-30 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 16:32 [Buildroot] Bug report or teaching moment -- downloading kernel patches Patrick Doyle
2017-12-30 17:10 ` Yann E. MORIN [this message]
2017-12-30 17:55 ` Patrick Doyle
2017-12-30 18:01 ` Yann E. MORIN
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=20171230171021.GG2921@scaer \
--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