From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libfastjson: Was referencing non-existing files
Date: Wed, 21 Sep 2016 11:00:42 +0200 [thread overview]
Message-ID: <20160921110042.538663cc@free-electrons.com> (raw)
In-Reply-To: <CAA=pTTRQKB0S0uz7xqHwUz4pw5__+e5Ws-xV_OjnpFL+Gyfy5g@mail.gmail.com>
Hello,
On Wed, 21 Sep 2016 08:44:23 +0000, Frederik Peter Aalund wrote:
> > <pkgname>-<version>.tar.gz is the default name of the tarball, so it
> > sounds like you have a LIBFASTJSON_SOURCE = .. somewhere - Please double
> > check.
>
> That must have been the culprit. Even though I deleted the external
> libfastjson.mk file,
> the value of LIBFASTJSON_SOURCE must still have been cached somewhere. There
> were no errors after i purged the entire buildroot folder. Thanks for
> investigating.
There is no cache anywhere in Buildroot for such variables. So it must
have been *defined* somewhere explicitly, due to a modification you had
done.
> > Nice, so you are using Buildroot on the sensors?
>
> Yes, and I'm really liking it so far. `make legal-info` in particular is
> very handy when aggregating programs in a distribution.
Glad to hear this is a useful functionality!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-21 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 9:36 [Buildroot] [PATCH 1/1] libfastjson: Was referencing non-existing files Frederik Aalund
2016-09-16 16:55 ` Thomas Petazzoni
2016-09-20 13:36 ` Frederik Peter Aalund
2016-09-20 14:33 ` Peter Korsgaard
2016-09-21 8:44 ` Frederik Peter Aalund
2016-09-21 9:00 ` Thomas Petazzoni [this message]
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=20160921110042.538663cc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.