From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-06-20
Date: Wed, 21 Jun 2017 11:26:42 +0200 [thread overview]
Message-ID: <20170621112642.3e993fde@windsurf.home> (raw)
In-Reply-To: <1498033808.3113.1.camel@embedded.rocks>
Hello,
On Wed, 21 Jun 2017 10:30:08 +0200, J?rg Krause wrote:
> > sh4a | libupnpp-0.15.2 | http://autobuild.buil
> > droot.net/results/df23cd5e77f61caf3f30cf43c91bc161a88def3a
>
> Odd, as libupnpp has BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 defined, but the
> sh4a toolchain is GCC 4.7.
Not odd at all: libupnpp indeed depends on gcc >= 4.9. But libupnpp is
selected by upmpdcli, which only depends on gcc >= 4.7. So the libupnpp
dependencies have not been properly propagated to upmpdcli.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next parent reply other threads:[~2017-06-21 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170621063055.8A34C20A28@mail.free-electrons.com>
[not found] ` <1498033808.3113.1.camel@embedded.rocks>
2017-06-21 9:26 ` Thomas Petazzoni [this message]
2017-06-21 9:31 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-06-20 Jörg Krause
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=20170621112642.3e993fde@windsurf.home \
--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.