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] wget download: 'scheme missing' results in empty output file
Date: Thu, 25 Feb 2016 18:01:58 +0100	[thread overview]
Message-ID: <20160225180158.673b34f5@free-electrons.com> (raw)
In-Reply-To: <874mcwwxyx.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Thu, 25 Feb 2016 17:34:14 +0100, Peter Korsgaard wrote:

>  > Also, for packages where the source is included with buildroot, like
>  > makedevs, FOO_SITE is empty too.
> 
> .. but those also don't define _SOURCE / _VERSION, so wget isn't called
> ;)

Yeah, but I was proposing to check for an empty FOO_SITE in the package
infrastructure itself, so we're not at the point where wget gets called.

But to answer Thomas: for cases like makedevs, we can special case such
packages (their _SOURCE is empty, or something like this).

Best regards,

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

  reply	other threads:[~2016-02-25 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 13:19 [Buildroot] wget download: 'scheme missing' results in empty output file Thomas De Schampheleire
2016-02-25 15:40 ` Peter Korsgaard
2016-02-25 16:05   ` Thomas De Schampheleire
2016-02-25 16:21     ` Peter Korsgaard
2016-02-25 16:07 ` Thomas Petazzoni
2016-02-25 16:13   ` Thomas De Schampheleire
2016-02-25 16:34     ` Peter Korsgaard
2016-02-25 17:01       ` Thomas Petazzoni [this message]
2016-02-25 20:32         ` Yann E. MORIN
2016-03-18  9:43           ` Thomas De Schampheleire
2016-07-03  9:54 ` Thomas Petazzoni

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=20160225180158.673b34f5@free-electrons.com \
    --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