From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Q. How to use a custom kernel tree?
Date: Fri, 08 Mar 2013 17:07:44 +0100 [thread overview]
Message-ID: <513A0CD0.2060205@relinux.de> (raw)
In-Reply-To: <CAHUKsLJM76BFzZunyc=6Jc=UUo4NKq=07_BHNRpVZwYc5VkkRg@mail.gmail.com>
Am 08.03.2013 16:47, schrieb Chris Wilkinson:
>
> I have a customized, patched kernel tree which I'd like BR to use.
>
> I tar'd the custom kernel tree, selected custom tarball for the kernel
> version and put the full URL/path to the archive in
> BR2_LINUX_KERNEL_CUSTOM_TARBALL.
>
> The custom tree also contains a defconfig for my arch. I set
> BR2_LINUX_KERNEL_USE_DEFCONFIG=y and gave it's name in
> BR2_LINUX_KERNEL_DEFCONFIG.
>
> Using make, BR error'ed out thus.
>
> >>> linux custom Extracting
> cat /home/chrisw/embedded/buildroot/dl/linux-3.4-ss4000e.tar | tar
> --strip-components=1 -C
> /home/chrisw/embedded/buildroot/output/build/linux-custom -xf -
> cat: /home/chrisw/embedded/buildroot/dl/linux-3.4-ss4000e.tar: No such
> file or directory
> tar: This does not look like a tar archive
> tar: Exiting with failure status due to previous errors
>
> It appears that BR expects to find the custom tarball in <BR>/dl, not
> the path I specified.
>
> What should I do to have BR use my custom kernel tree and config?
Hello Chris,
unfortunatelly, buildroot always assumes that the "custom tarball" is on
a server where it can be fetched using wget. I submitted a patch
(http://patchwork.ozlabs.org/patch/217204/) some time ago to improve
this, but noone responded.
You can use Source Override (see docu) to use your local kernel tree
(not gzipped).
Regards
Stephan
>
> --
> -Chris-
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130308/7959605e/attachment.html>
next prev parent reply other threads:[~2013-03-08 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 15:47 [Buildroot] Q. How to use a custom kernel tree? Chris Wilkinson
2013-03-08 16:00 ` Jeremy Rosen
2013-03-08 16:07 ` Thomas Petazzoni
2013-03-08 16:09 ` Jeremy Rosen
2013-03-08 16:12 ` Thomas Petazzoni
2013-03-08 19:21 ` Chris Wilkinson
2013-03-08 16:05 ` Thomas Petazzoni
2013-03-11 15:49 ` Chris Wilkinson
2013-03-11 17:30 ` Thomas Petazzoni
2013-03-08 16:07 ` Stephan Hoffmann [this message]
2013-03-11 14:34 ` Chris Wilkinson
2013-03-12 11:17 ` Rafał Fabich
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=513A0CD0.2060205@relinux.de \
--to=sho@relinux.de \
--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