From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] package/cmake: re-introduce cmake-3.7
Date: Thu, 2 Mar 2017 09:41:07 +0100 [thread overview]
Message-ID: <20170302094107.0f66f2c0@free-electrons.com> (raw)
In-Reply-To: <20170301221413.6cb8f56d@free-electrons.com>
Hello,
On Wed, 1 Mar 2017 22:14:13 +0100, Thomas Petazzoni wrote:
> > Thomas Petazzoni (1):
> > cmake: adjust dependencies added for libuv
> >
> > Vicente Olivert Riera (3):
> > cmake: bump version to 3.7.0
> > cmake: bump version to 3.7.1
> > cmake: bump version to 3.7.2
> >
> > Yann E. MORIN (1):
> > core/pkg-cmake: provide our own platform description
>
> All applied to master. Thanks!
Well, it seems like this introduced some issues.
Look for example at:
http://autobuild.buildroot.net/?reason=paho-mqtt-c-v1.1.0
paho-mqtt-c builds fine at commit
9951d5c931c419a32d31cc2a67d3a5c388efbed6 (before the CMake changes),
but fails to build at commit 609df3acf644e97d0aa4a66db8998d93f8543f3b
(right after the CMake changes).
Here is a minimal defconfig to reproduce the problem:
BR2_arcle=y
BR2_archs38=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_PAHO_MQTT_C=y
# BR2_TARGET_ROOTFS_TAR is not set
The fastd problems could also be related, but I haven't checked, see
http://autobuild.buildroot.net/?reason=fastd-18.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-02 8:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 18:07 [Buildroot] [PATCH 0/5] package/cmake: re-introduce cmake-3.7 Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 1/5] core/pkg-cmake: provide our own platform description Yann E. MORIN
2017-02-28 18:26 ` Baruch Siach
2017-02-28 20:03 ` Yann E. MORIN
2017-02-28 20:41 ` Jörg Krause
2017-02-28 20:58 ` Yann E. MORIN
2017-02-28 22:15 ` Jörg Krause
2017-03-01 8:01 ` Arnout Vandecappelle
2017-03-01 7:58 ` Arnout Vandecappelle
2017-03-01 8:17 ` Thomas Petazzoni
2017-03-01 8:35 ` Arnout Vandecappelle
2017-03-01 18:43 ` Yann E. MORIN
2017-03-05 23:27 ` Arnout Vandecappelle
2017-03-06 17:00 ` Yann E. MORIN
2017-03-06 22:02 ` Arnout Vandecappelle
2017-03-02 12:29 ` Baruch Siach
2017-03-02 12:41 ` Thomas Petazzoni
2017-02-28 18:07 ` [Buildroot] [PATCH 2/5] cmake: bump version to 3.7.0 Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 3/5] cmake: bump version to 3.7.1 Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 4/5] cmake: adjust dependencies added for libuv Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 5/5] cmake: bump version to 3.7.2 Yann E. MORIN
2017-03-01 7:49 ` [Buildroot] [PATCH 0/5] package/cmake: re-introduce cmake-3.7 Arnout Vandecappelle
2017-03-01 7:59 ` Thomas Petazzoni
2017-03-01 21:14 ` Thomas Petazzoni
2017-03-02 8:41 ` Thomas Petazzoni [this message]
2017-03-02 17:39 ` Yann E. MORIN
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=20170302094107.0f66f2c0@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