[Buildroot] Q. How to use a custom kernel tree?

[Buildroot] Q. How to use a custom kernel tree?

[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?

-- 
-Chris-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130308/61d4cd23/attachment-0001.html>

[Buildroot] Q. How to use a custom kernel tree?

[Jeremy Rosen]

simplest is to set a local.mk containing

LINUX_OVERRIDE_SRCDIR=<path to your uncompressed source>


this will use your directory as the sources.

there is also an option to specify the config file.

with those two you should be good



    Cordialement

    J?r?my Rosen

fight key loggers : write some perl using vim

----- Mail original -----
> 
> 
> 
> 
> 
> 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?
> 
> 
> 
> --
> -Chris-
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] Q. How to use a custom kernel tree?

[Thomas Petazzoni]

Dear Jeremy Rosen,

Please don't top-post, this is annoying.

On Fri, 8 Mar 2013 17:00:51 +0100 (CET), Jeremy Rosen wrote:
> simplest is to set a local.mk containing
> 
> LINUX_OVERRIDE_SRCDIR=<path to your uncompressed source>
> 
> this will use your directory as the sources.
> 
> there is also an option to specify the config file.
> 
> with those two you should be good

This doesn't really answers Chris question. The LINUX_OVERRIDE_SRCDIR
mechanism is usually meant to be useful during development, when you're
actively modifying your kernel tree.

Apparently, Chris is in a situation where he has some kernel sources
that don't change, and therefore he creates a tarball from them, and
expect Buildroot to be able to use this tarball. This can normally be
achieved using the BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION option,
which Chris rightly tried to use.

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

[Buildroot] Q. How to use a custom kernel tree?

[Jeremy Rosen]

ok, I misunderstood...

I thought he was actively developing and that he did the tarbal because
CUSTOM_TARBALL was the only way to override, not the other way round

my bad...

    Cordialement

    J?r?my Rosen

fight key loggers : write some perl using vim

----- Mail original -----
> Dear Jeremy Rosen,
> 
> Please don't top-post, this is annoying.
> 
> On Fri, 8 Mar 2013 17:00:51 +0100 (CET), Jeremy Rosen wrote:
> > simplest is to set a local.mk containing
> > 
> > LINUX_OVERRIDE_SRCDIR=<path to your uncompressed source>
> > 
> > this will use your directory as the sources.
> > 
> > there is also an option to specify the config file.
> > 
> > with those two you should be good
> 
> This doesn't really answers Chris question. The LINUX_OVERRIDE_SRCDIR
> mechanism is usually meant to be useful during development, when
> you're
> actively modifying your kernel tree.
> 
> Apparently, Chris is in a situation where he has some kernel sources
> that don't change, and therefore he creates a tarball from them, and
> expect Buildroot to be able to use this tarball. This can normally be
> achieved using the BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION option,
> which Chris rightly tried to use.
> 
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> 

[Buildroot] Q. How to use a custom kernel tree?

[Thomas Petazzoni]

Dear Jeremy Rosen,

On Fri, 8 Mar 2013 17:09:37 +0100 (CET), Jeremy Rosen wrote:
> ok, I misunderstood...
> 
> I thought he was actively developing and that he did the tarbal because
> CUSTOM_TARBALL was the only way to override, not the other way round
> 
> my bad...

Can you please stop this horrible practice of top-posting?

Thanks!

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

[Buildroot] Q. How to use a custom kernel tree?

[Chris Wilkinson]

Thanks for the tip. Where should this file be located? I read somewhere
else that it is at the root of the BR sources directory but I don't see
that in my BR tree.

My .config in in Pastebin here http://pastebin.com/6XDsAGzv

Chris


On Fri, Mar 8, 2013 at 11:12 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear Jeremy Rosen,
>
> On Fri, 8 Mar 2013 17:09:37 +0100 (CET), Jeremy Rosen wrote:
> > ok, I misunderstood...
> >
> > I thought he was actively developing and that he did the tarbal because
> > CUSTOM_TARBALL was the only way to override, not the other way round
> >
> > my bad...
>
> Can you please stop this horrible practice of top-posting?
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>



-- 
-Chris-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130308/f8ecc880/attachment.html>

[Buildroot] Q. How to use a custom kernel tree?

[Thomas Petazzoni]

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

[Buildroot] Q. How to use a custom kernel tree?

[Chris Wilkinson]

Is this a config error on my part or a BR bug? Stephan suggests it's
currently a BR limitation that custom tarballs can only be got from an http
server not a local directory.


On Fri, Mar 8, 2013 at 11:05 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

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



-- 
-Chris-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130311/1757010f/attachment.html>

[Buildroot] Q. How to use a custom kernel tree?

[Thomas Petazzoni]

Dear Chris Wilkinson,

On Mon, 11 Mar 2013 11:49:29 -0400, Chris Wilkinson wrote:
> Is this a config error on my part or a BR bug? Stephan suggests it's
> currently a BR limitation that custom tarballs can only be got from an http
> server not a local directory.

Yes, I think Stefan is correct. There is a patch pending to fix this
issue.

Best regards,

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

[Buildroot] Q. How to use a custom kernel tree?

[Stephan Hoffmann]

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>

[Buildroot] Q. How to use a custom kernel tree?

[Chris Wilkinson]

Pity this didn't get taken up. Perhaps it got overlooked. You could try
again possibly?

Chris


On Fri, Mar 8, 2013 at 11:07 AM, Stephan Hoffmann <sho@relinux.de> wrote:

>  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 listbuildroot at busybox.nethttp://lists.busybox.net/mailman/listinfo/buildroot
>
>
>
> --
> reLinux     -    Stephan Hoffmann
> Am Schmidtgrund 124    50765 K?ln
> Tel. +49.221.95595-19    Fax: -64www.reLinux.de     sho at reLinux.de
>
>


-- 
-Chris-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130311/1c852f1f/attachment-0001.html>

[Buildroot] Q. How to use a custom kernel tree?

[Rafał Fabich]

Hi,

On Fri, Mar 8, 2013 at 4:47 PM, Chris Wilkinson <winstonian36@gmail.com> wrote:
>
> I have a customized, patched kernel tree which I'd like BR to use.
>
>
> 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?
>

You can try this patch:
http://patchwork.ozlabs.org/patch/222743/


Best regards,
Rafal