From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] pulseview: new package
Date: Wed, 8 Apr 2015 16:29:05 +0200 [thread overview]
Message-ID: <20150408162905.4cfbc0a3@free-electrons.com> (raw)
In-Reply-To: <CAMpxmJXWnzUwgM7EQ3De4OCAprJ1oFVecYMD8j+xa7dU8co1qA@mail.gmail.com>
Dear Bartosz Golaszewski,
On Wed, 8 Apr 2015 16:07:07 +0200, Bartosz Golaszewski wrote:
> is it somehow possible to see the full build log? Pulseview can't be
> built due to:
>
> -- checking for module 'libsigrokcxx>=0.3.0'
> -- package 'libsigrokcxx>=0.3.0' not found
>
> I can't reproduce it with attached configs locally though and need to
> see what happens when building the C++ bindings.
No, we don't save the full build logs as they are way too large. Did
you try rebuilding exactly one of the failing configurations?
For example, building
http://autobuild.buildroot.org/results/a4e/a4ebb507798b94272bbad02456dace90472785a7/config ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-08 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 10:08 [Buildroot] [PATCH v2] pulseview: new package Bartosz Golaszewski
2015-03-20 22:07 ` Thomas Petazzoni
2015-03-23 22:09 ` Bartosz Golaszewski
2015-04-06 21:43 ` Thomas Petazzoni
2015-04-08 10:45 ` Bartosz Golaszewski
2015-04-08 14:07 ` Bartosz Golaszewski
2015-04-08 14:29 ` Thomas Petazzoni [this message]
2015-04-08 14:38 ` Bartosz Golaszewski
2015-04-08 16:05 ` Bartosz Golaszewski
2015-04-08 19:12 ` Thomas Petazzoni
2015-04-08 20:29 ` Bartosz Golaszewski
2015-04-08 20:38 ` Thomas Petazzoni
2015-04-09 10:19 ` Bartosz Golaszewski
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=20150408162905.4cfbc0a3@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