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] longterm kernel releases: version-URI different for v2.x kernels
Date: Sat, 16 Nov 2013 11:38:42 +0100	[thread overview]
Message-ID: <20131116113842.1c01a56d@skate> (raw)
In-Reply-To: <76128FA7-9969-4BC7-B8F8-07F5BEDDD177@ipfabrics.com>

Dear Rick Robino,

On Fri, 15 Nov 2013 23:53:40 -0800, Rick Robino wrote:

> I encountered problems automatically downloading kernel version
> 2.6.32.61, one of the current longterm releases.  It looks like the
> URL might have changed, so I thought that I would mention it here in
> case this fact might be news to anyone.
> 
> The longterm kernels are in a subdirectory called
> ?v2/.6/longterm/vA.B.C?.  Buildroot only looks in ?v2.6?, which works
> fine for standard kernels but not the longterm ones for 2.6.

Yes. Buildroot cannot guess if the kernel version you're using is a
"normal" version or a "longterm" version. Therefore, when you choose to
only give the kernel version in the configuration, it only looks in
2.6/ or 3.x/. If you need a kernel version that is available in some
other location, then you should use the "Custom tarball" configuration
choice, which allows you to pass an arbitrary URL to a tarball,
either located on kernel.org or on some other place.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-11-16 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16  7:53 [Buildroot] longterm kernel releases: version-URI different for v2.x kernels Rick Robino
2013-11-16 10:38 ` Thomas Petazzoni [this message]
2013-11-16 10:59   ` Rick Robino
2013-11-16 15:07   ` Thomas De Schampheleire

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=20131116113842.1c01a56d@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