Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Q. How to use a custom kernel tree?
Date: Fri, 8 Mar 2013 17:05:21 +0100	[thread overview]
Message-ID: <20130308170521.3e8926ff@skate> (raw)
In-Reply-To: <CAHUKsLJM76BFzZunyc=6Jc=UUo4NKq=07_BHNRpVZwYc5VkkRg@mail.gmail.com>

Dear Chris Wilkinson,

On Fri, 8 Mar 2013 10:47:42 -0500, Chris Wilkinson wrote:
> 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.

Can you pastebin your .config file somewhere?

> 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.

Hum, let's see your .config first. Once we check that, we'll be able to
tell you if it's a configuration problem  or indeed a Buildroot bug.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-03-08 16:05 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 [this message]
2013-03-11 15:49   ` Chris Wilkinson
2013-03-11 17:30     ` Thomas Petazzoni
2013-03-08 16:07 ` Stephan Hoffmann
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=20130308170521.3e8926ff@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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