* [Buildroot] Cross-compiling out-of-tree kernel modules and user-space apps
From: Thomas Petazzoni @ 2017-05-03 9:35 UTC (permalink / raw)
To: buildroot
In-Reply-To: <4e87c694-21a2-7f06-9d88-f736e832e061@free.fr>
Hello,
On Wed, 3 May 2017 11:15:15 +0200, Mason wrote:
> I use buildroot to generate kernel + rootfs image for an ARM
> platform, typically cross-compiled with the Linaro toolchain.
>
> I also have a large body of software in a separate repo
> (outside of the BR tree) with its own build system.
What do you call "its own build system" ?
> This repo includes kernel modules, user-space libraries
> and apps, which need to be cross-compiled and built on
> top of the rootfs generated by BR.
>
> Therefore, I would need to pass some information from BR
> to the separate build system, such as
>
> - ARCH
> - CROSS_COMPILE
> - location of the cross-toolchain, to add to the PATH
> - location of the sysroot
>
> What is the best way to do this?
Create Buildroot packages for the different software components you
need to build.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply
* [Buildroot] Cross-compiling out-of-tree kernel modules and user-space apps
From: Mason @ 2017-05-03 9:48 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20170503113509.0d5cd238@free-electrons.com>
On 03/05/2017 11:35, Thomas Petazzoni wrote:
> On Wed, 3 May 2017 11:15:15 +0200, Mason wrote:
>
>> I use buildroot to generate kernel + rootfs image for an ARM
>> platform, typically cross-compiled with the Linaro toolchain.
>>
>> I also have a large body of software in a separate repo
>> (outside of the BR tree) with its own build system.
>
> What do you call "its own build system" ?
A scary jungle of intertwined / recursive Makefiles. Basically,
one types 'make all' to build modules, libs, apps, and firmwares.
Sorting this mess out would be a multi-man-months effort.
>> This repo includes kernel modules, user-space libraries
>> and apps, which need to be cross-compiled and built on
>> top of the rootfs generated by BR.
>>
>> Therefore, I would need to pass some information from BR
>> to the separate build system, such as
>>
>> - ARCH
>> - CROSS_COMPILE
>> - location of the cross-toolchain, to add to the PATH
>> - location of the sysroot
>>
>> What is the best way to do this?
>
> Create Buildroot packages for the different software components you
> need to build.
OK, what's the second best way to do this, then?
The way it was done in the past is to get BR to produce a script
that exports the above information, and source said script before
invoking the proprietary build system.
Regards.
^ permalink raw reply
* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
From: Thomas De Schampheleire @ 2017-05-03 10:29 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20170430062822.F06D82097E@mail.free-electrons.com>
Hi Thomas,
On Sun, Apr 30, 2017 at 08:28:22AM +0200, Thomas Petazzoni wrote:
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2017-04-29, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
>
> Build failures related to your packages:
>
> arm | toolchain-external-custom | http://autobuild.buildroot.net/results/39888c188c0d13219a8419897a833275fcc81597
>
It seems that this is an invalid configuration:
BR2_arm=y
BR2_cortex_a8=y
BR2_ARM_EABI=y
BR2_ARM_INSTRUCTIONS_THUMB2=y
BR2_STATIC_LIBS=y
BR2_TOOLCHAIN_EXTERNAL=y
With STATIC_LIBS set, there is no downloadable external toolchain.
As such, Buildroot falls back to a preinstalled one and sets the toolchain
location to /path/to/toolchain, which does not exist.
However, I don't find this toolchain config in the list at:
http://autobuild.buildroot.net/toolchains/configs/
The build was submitted by Richard Braun, could it be that he is using toolchain
configs that are not in this list?
Thanks,
Thomas
^ permalink raw reply
* [Buildroot] [PATCH] empty: bump to version 0.6.20b
From: Baruch Siach @ 2017-05-03 12:01 UTC (permalink / raw)
To: buildroot
Drop upstream patch.
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
package/empty/0002-fix-non-thread-build.patch | 49 ---------------------------
package/empty/empty.hash | 2 +-
package/empty/empty.mk | 2 +-
3 files changed, 2 insertions(+), 51 deletions(-)
delete mode 100644 package/empty/0002-fix-non-thread-build.patch
diff --git a/package/empty/0002-fix-non-thread-build.patch b/package/empty/0002-fix-non-thread-build.patch
deleted file mode 100644
index a7e8d90a212f..000000000000
--- a/package/empty/0002-fix-non-thread-build.patch
+++ /dev/null
@@ -1,49 +0,0 @@
-empty uses SysV semaphores, so the ifdef is wrong here.
-
-Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
-
---- empty-0.6.19b.orig/empty.c 2012-09-19 13:24:05.000000000 +0200
-+++ empty-0.6.19b/empty.c 2015-07-09 02:00:09.000000000 +0200
-@@ -179,25 +179,23 @@ int main (int argc, char *argv[]) {
- 2 - unknown */
-
- /* semaphores */
--#ifdef _POSIX_SEMAPHORES
-- #if defined(__linux__) && defined(__GNU_LIBRARY__) && !defined(_SEM_SEMUN_UNDEFINED)
-- /* union semun is defined by including <sys/sem.h> */
-- #else
-- union semun {
-- int val;
-- struct semid_ds *buf;
-- #ifdef __SVR4
-- ushort_t *array;
-- #endif
-- #ifdef __hpux__
-- ushort *array;
-- #endif
-- #ifdef __linux__
-- unsigned short *array;
-- struct seminfo *__buf; /* buffer for IPC_INFO */
-- #endif
-- };
-- #endif
-+#if defined(__linux__) && defined(__GNU_LIBRARY__) && !defined(_SEM_SEMUN_UNDEFINED)
-+ /* union semun is defined by including <sys/sem.h> */
-+#else
-+ union semun {
-+ int val;
-+ struct semid_ds *buf;
-+ #ifdef __SVR4
-+ ushort_t *array;
-+ #endif
-+ #ifdef __hpux__
-+ ushort *array;
-+ #endif
-+ #ifdef __linux__
-+ unsigned short *array;
-+ struct seminfo *__buf; /* buffer for IPC_INFO */
-+ #endif
-+ };
- #endif
- union semun semu;
-
diff --git a/package/empty/empty.hash b/package/empty/empty.hash
index 91402889fa5e..e62939687db7 100644
--- a/package/empty/empty.hash
+++ b/package/empty/empty.hash
@@ -1,2 +1,2 @@
# Locally computed:
-sha256 05b7cb361ef815774abda325c09c573f8c9039ccbb71eedc743439e4637c314a empty-0.6.19b.tgz
+sha256 7e6636e400856984c4405ce7bd0843aaa3329fa3efd20c58df8400a9eaa35f09 empty-0.6.20b.tgz
diff --git a/package/empty/empty.mk b/package/empty/empty.mk
index a1cc3c0526a3..5e3ed42befd4 100644
--- a/package/empty/empty.mk
+++ b/package/empty/empty.mk
@@ -4,7 +4,7 @@
#
################################################################################
-EMPTY_VERSION = 0.6.19b
+EMPTY_VERSION = 0.6.20b
EMPTY_SOURCE = empty-$(EMPTY_VERSION).tgz
EMPTY_SITE = http://downloads.sourceforge.net/project/empty/empty/empty-$(EMPTY_VERSION)
EMPTY_LICENSE = BSD-3-Clause
--
2.11.0
^ permalink raw reply related
* [Buildroot] Cross-compiling out-of-tree kernel modules and user-space apps
From: Thomas Petazzoni @ 2017-05-03 12:23 UTC (permalink / raw)
To: buildroot
In-Reply-To: <60824eaa-5a38-a9b7-1394-ae9c5d2a64bf@free.fr>
Hello,
On Wed, 3 May 2017 11:48:28 +0200, Mason wrote:
> > What do you call "its own build system" ?
>
> A scary jungle of intertwined / recursive Makefiles. Basically,
> one types 'make all' to build modules, libs, apps, and firmwares.
> Sorting this mess out would be a multi-man-months effort.
You don't need to "sort this mess out". Just create a Buildroot package
that does "make all".
> > Create Buildroot packages for the different software components you
> > need to build.
>
> OK, what's the second best way to do this, then?
Again: create a package for it. Whatever you think should be done in a
shell script can be done in a Buildroot package, so there is no reason
to not create a Buildroot package for your stuff.
You don't necessarily need to split it into multiple Buildroot
packages. It can be just one big Buildroot package that calls your
"make all" stuff to build your home-grown apps/libs/modules in one go.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply
* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
From: Thomas Petazzoni @ 2017-05-03 12:29 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20170503102922.GB26389@argentina>
Hello,
Adding Arnout in Cc here because I believe it is a bug he introduced :-)
On Wed, 3 May 2017 12:29:22 +0200, Thomas De Schampheleire wrote:
> It seems that this is an invalid configuration:
>
> BR2_arm=y
> BR2_cortex_a8=y
> BR2_ARM_EABI=y
> BR2_ARM_INSTRUCTIONS_THUMB2=y
> BR2_STATIC_LIBS=y
> BR2_TOOLCHAIN_EXTERNAL=y
>
> With STATIC_LIBS set, there is no downloadable external toolchain.
> As such, Buildroot falls back to a preinstalled one and sets the toolchain
> location to /path/to/toolchain, which does not exist.
>
> However, I don't find this toolchain config in the list at:
> http://autobuild.buildroot.net/toolchains/configs/
BR2_STATIC_LIBS is randomly added, to all possible configurations:
https://git.buildroot.org/buildroot-test/tree/scripts/autobuild-run#n553
So even if you don't see this configuration in the list of toolchains,
it is normal to see BR2_STATIC_LIBS=y.
However, BR2_STATIC_LIBS should not be added for glibc toolchains.
Arnout recently reworked the way we detect if it's a glibc toolchain or
not... and it seems like it doesn't work as expected. Or perhaps
Richard hasn't updated his autobuild-run script and we have another
issue ?
Richard have you updated your autobuild-run script recently?
Thomas DS, see:
https://git.buildroot.org/buildroot-test/commit/scripts/autobuild-run?id=7c49373a4f494fea64e98c44ca504680e89a0e86
https://git.buildroot.org/buildroot-test/commit/scripts/autobuild-run?id=3972df164e23828a0e9eb8aa85f4e82b760a859e
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply
* [Buildroot] [PATCH] dtc: bump version to 1.4.4
From: Peter Korsgaard @ 2017-05-03 12:32 UTC (permalink / raw)
To: buildroot
Adds overlay support.
Drop the non-upstreamed 0002-extra-cflags.patch and instead simply pass the
needed CFLAGS as make arguments. Passing the full upstream warning flags
are not important in the Buildroot context, so this is simpler than
maintaining a patch.
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
| 32 --------------------------------
package/dtc/dtc.hash | 2 +-
package/dtc/dtc.mk | 6 +++---
3 files changed, 4 insertions(+), 36 deletions(-)
delete mode 100644 package/dtc/0002-extra-cflags.patch
diff --git a/package/dtc/0002-extra-cflags.patch b/package/dtc/0002-extra-cflags.patch
deleted file mode 100644
index f070692c0..000000000
--- a/package/dtc/0002-extra-cflags.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-Makefile: append the CFLAGS to existing ones
-
-Allow the user to pass custom CFLAGS (eg. optimisation flags).
-
-Do not use EXTRA_CFLAGS, append to existing CFLAGS with += (Arnout)
-
-Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
-Cc: Arnout Vandecappelle <arnout@mind.be>
-
----
-Patch not sent upstream.
-
-Although not specific to buildroot, I am not sure this is the best
-way to handle user-supplied CFLAGS.
-
-diff --git a/Makefile b/Makefile
-index 962f94eba661..bf6b317158cf 100644
---- a/Makefile
-+++ b/Makefile
-@@ -16,9 +16,10 @@ LOCAL_VERSION =
- CONFIG_LOCALVERSION =
-
- CPPFLAGS = -I libfdt -I .
--WARNINGS = -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
-+WARNINGS = -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
- -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls -Wshadow
--CFLAGS = -g -Os -fPIC -Werror $(WARNINGS)
-+CFLAGS ?= -g -Os
-+CFLAGS += -fPIC $(WARNINGS)
-
- BISON = bison
- LEX = flex
diff --git a/package/dtc/dtc.hash b/package/dtc/dtc.hash
index 8b3af331f..75c2e40ee 100644
--- a/package/dtc/dtc.hash
+++ b/package/dtc/dtc.hash
@@ -1,2 +1,2 @@
# from https://www.kernel.org/pub/software/utils/dtc/sha256sums.asc
-sha256 77992ad8eac7b68f553d0ba58e5b51604ac803d126196c99e3ae38aaae28bb94 dtc-1.4.1.tar.xz
+sha256 470731d5c015b160d26a96645dbb1c7337d6e7b8c98244612002b66bedf6cffb dtc-1.4.4.tar.xz
diff --git a/package/dtc/dtc.mk b/package/dtc/dtc.mk
index 5bb2ca26a..9d50e3596 100644
--- a/package/dtc/dtc.mk
+++ b/package/dtc/dtc.mk
@@ -4,7 +4,7 @@
#
################################################################################
-DTC_VERSION = 1.4.1
+DTC_VERSION = 1.4.4
DTC_SOURCE = dtc-$(DTC_VERSION).tar.xz
DTC_SITE = https://www.kernel.org/pub/software/utils/dtc
DTC_LICENSE = GPL-2.0+ or BSD-2-Clause (library)
@@ -32,7 +32,7 @@ DTC_INSTALL_GOAL = install-lib
endif # $(BR2_PACKAGE_DTC_PROGRAMS) != y
define DTC_BUILD_CMDS
- $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) PREFIX=/usr
+ $(TARGET_CONFIGURE_OPTS) $(MAKE) CFLAGS="$(TARGET_CFLAGS) -fPIC" -C $(@D) PREFIX=/usr
endef
# For staging, only the library is needed
@@ -47,7 +47,7 @@ endef
# host build
define HOST_DTC_BUILD_CMDS
- $(HOST_CONFIGURE_OPTS) $(MAKE) -C $(@D) PREFIX=$(HOST_DIR)/usr
+ $(HOST_CONFIGURE_OPTS) $(MAKE) CFLAGS="$(HOST_CFLAGS) -fPIC" -C $(@D) PREFIX=$(HOST_DIR)/usr
endef
define HOST_DTC_INSTALL_CMDS
--
2.11.0
^ permalink raw reply related
* [Buildroot] [PATCH] dtc: bump version to 1.4.4
From: Matthew Weber @ 2017-05-03 12:39 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20170503123215.20544-1-peter@korsgaard.com>
All,
On Wed, May 3, 2017 at 7:32 AM, Peter Korsgaard <peter@korsgaard.com> wrote:
> Adds overlay support.
>
> Drop the non-upstreamed 0002-extra-cflags.patch and instead simply pass the
> needed CFLAGS as make arguments. Passing the full upstream warning flags
> are not important in the Buildroot context, so this is simpler than
> maintaining a patch.
>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
A dtc bump came up earlier this week on one of our projects starting
to use overlays. :-) Thanks for the patch.
Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com>
> ---
> package/dtc/0002-extra-cflags.patch | 32 --------------------------------
> package/dtc/dtc.hash | 2 +-
> package/dtc/dtc.mk | 6 +++---
> 3 files changed, 4 insertions(+), 36 deletions(-)
> delete mode 100644 package/dtc/0002-extra-cflags.patch
>
> diff --git a/package/dtc/0002-extra-cflags.patch b/package/dtc/0002-extra-cflags.patch
> deleted file mode 100644
> index f070692c0..000000000
> --- a/package/dtc/0002-extra-cflags.patch
> +++ /dev/null
> @@ -1,32 +0,0 @@
> -Makefile: append the CFLAGS to existing ones
> -
> -Allow the user to pass custom CFLAGS (eg. optimisation flags).
> -
> -Do not use EXTRA_CFLAGS, append to existing CFLAGS with += (Arnout)
> -
> -Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> -Cc: Arnout Vandecappelle <arnout@mind.be>
> -
> ----
> -Patch not sent upstream.
> -
> -Although not specific to buildroot, I am not sure this is the best
> -way to handle user-supplied CFLAGS.
> -
> -diff --git a/Makefile b/Makefile
> -index 962f94eba661..bf6b317158cf 100644
> ---- a/Makefile
> -+++ b/Makefile
> -@@ -16,9 +16,10 @@ LOCAL_VERSION =
> - CONFIG_LOCALVERSION =
> -
> - CPPFLAGS = -I libfdt -I .
> --WARNINGS = -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
> -+WARNINGS = -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
> - -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls -Wshadow
> --CFLAGS = -g -Os -fPIC -Werror $(WARNINGS)
> -+CFLAGS ?= -g -Os
> -+CFLAGS += -fPIC $(WARNINGS)
> -
> - BISON = bison
> - LEX = flex
> diff --git a/package/dtc/dtc.hash b/package/dtc/dtc.hash
> index 8b3af331f..75c2e40ee 100644
> --- a/package/dtc/dtc.hash
> +++ b/package/dtc/dtc.hash
> @@ -1,2 +1,2 @@
> # from https://www.kernel.org/pub/software/utils/dtc/sha256sums.asc
> -sha256 77992ad8eac7b68f553d0ba58e5b51604ac803d126196c99e3ae38aaae28bb94 dtc-1.4.1.tar.xz
> +sha256 470731d5c015b160d26a96645dbb1c7337d6e7b8c98244612002b66bedf6cffb dtc-1.4.4.tar.xz
> diff --git a/package/dtc/dtc.mk b/package/dtc/dtc.mk
> index 5bb2ca26a..9d50e3596 100644
> --- a/package/dtc/dtc.mk
> +++ b/package/dtc/dtc.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -DTC_VERSION = 1.4.1
> +DTC_VERSION = 1.4.4
> DTC_SOURCE = dtc-$(DTC_VERSION).tar.xz
> DTC_SITE = https://www.kernel.org/pub/software/utils/dtc
> DTC_LICENSE = GPL-2.0+ or BSD-2-Clause (library)
> @@ -32,7 +32,7 @@ DTC_INSTALL_GOAL = install-lib
> endif # $(BR2_PACKAGE_DTC_PROGRAMS) != y
>
> define DTC_BUILD_CMDS
> - $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) PREFIX=/usr
> + $(TARGET_CONFIGURE_OPTS) $(MAKE) CFLAGS="$(TARGET_CFLAGS) -fPIC" -C $(@D) PREFIX=/usr
> endef
>
> # For staging, only the library is needed
> @@ -47,7 +47,7 @@ endef
>
> # host build
> define HOST_DTC_BUILD_CMDS
> - $(HOST_CONFIGURE_OPTS) $(MAKE) -C $(@D) PREFIX=$(HOST_DIR)/usr
> + $(HOST_CONFIGURE_OPTS) $(MAKE) CFLAGS="$(HOST_CFLAGS) -fPIC" -C $(@D) PREFIX=$(HOST_DIR)/usr
> endef
>
> define HOST_DTC_INSTALL_CMDS
> --
> 2.11.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
^ permalink raw reply
* [Buildroot] [PATCH 1/2] picocom: bump to version 2.2
From: Baruch Siach @ 2017-05-03 12:46 UTC (permalink / raw)
To: buildroot
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
package/picocom/picocom.hash | 2 +-
package/picocom/picocom.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/picocom/picocom.hash b/package/picocom/picocom.hash
index 674b6209d3bd..16db03e10485 100644
--- a/package/picocom/picocom.hash
+++ b/package/picocom/picocom.hash
@@ -1,2 +1,2 @@
# Locally calculated
-sha256 6b152fc5f816eaef6b86336a4cec7cf1496b7c712061e5aea5a36f143a0b09ed picocom-2.1.tar.gz
+sha256 3e3904158d675541f0fcfdcd1f671b38445338f536080f5de8d6674b5f33d4ce picocom-2.2.tar.gz
diff --git a/package/picocom/picocom.mk b/package/picocom/picocom.mk
index 8e77f1d425c4..07bda0e745cd 100644
--- a/package/picocom/picocom.mk
+++ b/package/picocom/picocom.mk
@@ -4,7 +4,7 @@
#
################################################################################
-PICOCOM_VERSION = 2.1
+PICOCOM_VERSION = 2.2
PICOCOM_SITE = $(call github,npat-efault,picocom,$(PICOCOM_VERSION))
PICOCOM_LICENSE = GPL-2.0+
PICOCOM_LICENSE_FILES = LICENSE.txt
--
2.11.0
^ permalink raw reply related
* [Buildroot] [PATCH 2/2] picocom: force target LDFLAGS
From: Baruch Siach @ 2017-05-03 12:46 UTC (permalink / raw)
To: buildroot
In-Reply-To: <04e1e4d95a425dfc0e0650088cb0120a9f3e46a8.1493815595.git.baruch@tkos.co.il>
This allows a static build of picocom when BR2_STATIC_LIBS=y but the toolchain
provides static and shared libraries.
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
package/picocom/picocom.mk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/picocom/picocom.mk b/package/picocom/picocom.mk
index 07bda0e745cd..4e25556f4c55 100644
--- a/package/picocom/picocom.mk
+++ b/package/picocom/picocom.mk
@@ -10,7 +10,8 @@ PICOCOM_LICENSE = GPL-2.0+
PICOCOM_LICENSE_FILES = LICENSE.txt
define PICOCOM_BUILD_CMDS
- $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D)
+ $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) \
+ LDFLAGS="$(TARGET_LDFLAGS)" -C $(@D)
endef
define PICOCOM_INSTALL_TARGET_CMDS
--
2.11.0
^ permalink raw reply related
* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
From: Thomas Petazzoni @ 2017-05-03 13:02 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20170503124713.GA17301@shattrath>
Hello,
On Wed, 3 May 2017 14:47:13 +0200, Richard Braun wrote:
> > Richard have you updated your autobuild-run script recently?
>
> My builder should be running with version 6986aa15ed966e16312ebaef1a47f498ca76a197.
>
> It is automatically updated and restarted once a week.
Then you are running with the latest changes from Arnout, and most of
the other autobuilder slaves are not, which is why we only see this
issue coming from your autobuilder.
So, this confirms my hypothesis that the bug is in the changes from
Arnout :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply
* [Buildroot] [PATCH 2/2] picocom: force target LDFLAGS
From: Thomas Petazzoni @ 2017-05-03 14:22 UTC (permalink / raw)
To: buildroot
In-Reply-To: <f7abac9c0ca017bffd3109f7df0d6bfa7f099281.1493815595.git.baruch@tkos.co.il>
Hello,
On Wed, 3 May 2017 15:46:35 +0300, Baruch Siach wrote:
> This allows a static build of picocom when BR2_STATIC_LIBS=y but the toolchain
> provides static and shared libraries.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/picocom/picocom.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/package/picocom/picocom.mk b/package/picocom/picocom.mk
> index 07bda0e745cd..4e25556f4c55 100644
> --- a/package/picocom/picocom.mk
> +++ b/package/picocom/picocom.mk
> @@ -10,7 +10,8 @@ PICOCOM_LICENSE = GPL-2.0+
> PICOCOM_LICENSE_FILES = LICENSE.txt
>
> define PICOCOM_BUILD_CMDS
> - $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D)
> + $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) \
> + LDFLAGS="$(TARGET_LDFLAGS)" -C $(@D)
We already pass LDFLAGS in $(TARGET_CONFIGURE_OPTS). Should we pass
$(TARGET_CONFIGURE_OPTS) on the right hand side of $(MAKE) ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply
* [Buildroot] [PATCH 2/2] picocom: force target LDFLAGS
From: Baruch Siach @ 2017-05-03 14:28 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20170503162244.5b67294e@free-electrons.com>
Hi Thomas,
On Wed, May 03, 2017 at 04:22:44PM +0200, Thomas Petazzoni wrote:
> On Wed, 3 May 2017 15:46:35 +0300, Baruch Siach wrote:
> > This allows a static build of picocom when BR2_STATIC_LIBS=y but the toolchain
> > provides static and shared libraries.
> >
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> > package/picocom/picocom.mk | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/package/picocom/picocom.mk b/package/picocom/picocom.mk
> > index 07bda0e745cd..4e25556f4c55 100644
> > --- a/package/picocom/picocom.mk
> > +++ b/package/picocom/picocom.mk
> > @@ -10,7 +10,8 @@ PICOCOM_LICENSE = GPL-2.0+
> > PICOCOM_LICENSE_FILES = LICENSE.txt
> >
> > define PICOCOM_BUILD_CMDS
> > - $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D)
> > + $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) \
> > + LDFLAGS="$(TARGET_LDFLAGS)" -C $(@D)
>
> We already pass LDFLAGS in $(TARGET_CONFIGURE_OPTS). Should we pass
> $(TARGET_CONFIGURE_OPTS) on the right hand side of $(MAKE) ?
That would overwrite CPPFLAGS that picocom Makefile uses for some seemingly
useful macros.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
^ permalink raw reply
* [Buildroot] [git commit] empty: bump to version 0.6.20b
From: Peter Korsgaard @ 2017-05-03 15:18 UTC (permalink / raw)
To: buildroot
commit: https://git.buildroot.net/buildroot/commit/?id=920c7f470678dcc550dd0c8de20e92d9da7bb0d1
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Drop upstream patch.
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/empty/0002-fix-non-thread-build.patch | 49 ---------------------------
package/empty/empty.hash | 2 +-
package/empty/empty.mk | 2 +-
3 files changed, 2 insertions(+), 51 deletions(-)
diff --git a/package/empty/0002-fix-non-thread-build.patch b/package/empty/0002-fix-non-thread-build.patch
deleted file mode 100644
index a7e8d90..0000000
--- a/package/empty/0002-fix-non-thread-build.patch
+++ /dev/null
@@ -1,49 +0,0 @@
-empty uses SysV semaphores, so the ifdef is wrong here.
-
-Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
-
---- empty-0.6.19b.orig/empty.c 2012-09-19 13:24:05.000000000 +0200
-+++ empty-0.6.19b/empty.c 2015-07-09 02:00:09.000000000 +0200
-@@ -179,25 +179,23 @@ int main (int argc, char *argv[]) {
- 2 - unknown */
-
- /* semaphores */
--#ifdef _POSIX_SEMAPHORES
-- #if defined(__linux__) && defined(__GNU_LIBRARY__) && !defined(_SEM_SEMUN_UNDEFINED)
-- /* union semun is defined by including <sys/sem.h> */
-- #else
-- union semun {
-- int val;
-- struct semid_ds *buf;
-- #ifdef __SVR4
-- ushort_t *array;
-- #endif
-- #ifdef __hpux__
-- ushort *array;
-- #endif
-- #ifdef __linux__
-- unsigned short *array;
-- struct seminfo *__buf; /* buffer for IPC_INFO */
-- #endif
-- };
-- #endif
-+#if defined(__linux__) && defined(__GNU_LIBRARY__) && !defined(_SEM_SEMUN_UNDEFINED)
-+ /* union semun is defined by including <sys/sem.h> */
-+#else
-+ union semun {
-+ int val;
-+ struct semid_ds *buf;
-+ #ifdef __SVR4
-+ ushort_t *array;
-+ #endif
-+ #ifdef __hpux__
-+ ushort *array;
-+ #endif
-+ #ifdef __linux__
-+ unsigned short *array;
-+ struct seminfo *__buf; /* buffer for IPC_INFO */
-+ #endif
-+ };
- #endif
- union semun semu;
-
diff --git a/package/empty/empty.hash b/package/empty/empty.hash
index 9140288..e629396 100644
--- a/package/empty/empty.hash
+++ b/package/empty/empty.hash
@@ -1,2 +1,2 @@
# Locally computed:
-sha256 05b7cb361ef815774abda325c09c573f8c9039ccbb71eedc743439e4637c314a empty-0.6.19b.tgz
+sha256 7e6636e400856984c4405ce7bd0843aaa3329fa3efd20c58df8400a9eaa35f09 empty-0.6.20b.tgz
diff --git a/package/empty/empty.mk b/package/empty/empty.mk
index a1cc3c0..5e3ed42 100644
--- a/package/empty/empty.mk
+++ b/package/empty/empty.mk
@@ -4,7 +4,7 @@
#
################################################################################
-EMPTY_VERSION = 0.6.19b
+EMPTY_VERSION = 0.6.20b
EMPTY_SOURCE = empty-$(EMPTY_VERSION).tgz
EMPTY_SITE = http://downloads.sourceforge.net/project/empty/empty/empty-$(EMPTY_VERSION)
EMPTY_LICENSE = BSD-3-Clause
^ permalink raw reply related
* [Buildroot] [git commit] dtc: bump version to 1.4.4
From: Peter Korsgaard @ 2017-05-03 15:18 UTC (permalink / raw)
To: buildroot
commit: https://git.buildroot.net/buildroot/commit/?id=40a5d253787039774992334050577363c09a7d94
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Adds overlay support.
Drop the non-upstreamed 0002-extra-cflags.patch and instead simply pass the
needed CFLAGS as make arguments. Passing the full upstream warning flags
are not important in the Buildroot context, so this is simpler than
maintaining a patch.
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
| 32 --------------------------------
package/dtc/dtc.hash | 2 +-
package/dtc/dtc.mk | 6 +++---
3 files changed, 4 insertions(+), 36 deletions(-)
diff --git a/package/dtc/0002-extra-cflags.patch b/package/dtc/0002-extra-cflags.patch
deleted file mode 100644
index f070692..0000000
--- a/package/dtc/0002-extra-cflags.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-Makefile: append the CFLAGS to existing ones
-
-Allow the user to pass custom CFLAGS (eg. optimisation flags).
-
-Do not use EXTRA_CFLAGS, append to existing CFLAGS with += (Arnout)
-
-Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
-Cc: Arnout Vandecappelle <arnout@mind.be>
-
----
-Patch not sent upstream.
-
-Although not specific to buildroot, I am not sure this is the best
-way to handle user-supplied CFLAGS.
-
-diff --git a/Makefile b/Makefile
-index 962f94eba661..bf6b317158cf 100644
---- a/Makefile
-+++ b/Makefile
-@@ -16,9 +16,10 @@ LOCAL_VERSION =
- CONFIG_LOCALVERSION =
-
- CPPFLAGS = -I libfdt -I .
--WARNINGS = -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
-+WARNINGS = -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
- -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls -Wshadow
--CFLAGS = -g -Os -fPIC -Werror $(WARNINGS)
-+CFLAGS ?= -g -Os
-+CFLAGS += -fPIC $(WARNINGS)
-
- BISON = bison
- LEX = flex
diff --git a/package/dtc/dtc.hash b/package/dtc/dtc.hash
index 8b3af33..75c2e40 100644
--- a/package/dtc/dtc.hash
+++ b/package/dtc/dtc.hash
@@ -1,2 +1,2 @@
# from https://www.kernel.org/pub/software/utils/dtc/sha256sums.asc
-sha256 77992ad8eac7b68f553d0ba58e5b51604ac803d126196c99e3ae38aaae28bb94 dtc-1.4.1.tar.xz
+sha256 470731d5c015b160d26a96645dbb1c7337d6e7b8c98244612002b66bedf6cffb dtc-1.4.4.tar.xz
diff --git a/package/dtc/dtc.mk b/package/dtc/dtc.mk
index 5bb2ca2..9d50e35 100644
--- a/package/dtc/dtc.mk
+++ b/package/dtc/dtc.mk
@@ -4,7 +4,7 @@
#
################################################################################
-DTC_VERSION = 1.4.1
+DTC_VERSION = 1.4.4
DTC_SOURCE = dtc-$(DTC_VERSION).tar.xz
DTC_SITE = https://www.kernel.org/pub/software/utils/dtc
DTC_LICENSE = GPL-2.0+ or BSD-2-Clause (library)
@@ -32,7 +32,7 @@ DTC_INSTALL_GOAL = install-lib
endif # $(BR2_PACKAGE_DTC_PROGRAMS) != y
define DTC_BUILD_CMDS
- $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) PREFIX=/usr
+ $(TARGET_CONFIGURE_OPTS) $(MAKE) CFLAGS="$(TARGET_CFLAGS) -fPIC" -C $(@D) PREFIX=/usr
endef
# For staging, only the library is needed
@@ -47,7 +47,7 @@ endef
# host build
define HOST_DTC_BUILD_CMDS
- $(HOST_CONFIGURE_OPTS) $(MAKE) -C $(@D) PREFIX=$(HOST_DIR)/usr
+ $(HOST_CONFIGURE_OPTS) $(MAKE) CFLAGS="$(HOST_CFLAGS) -fPIC" -C $(@D) PREFIX=$(HOST_DIR)/usr
endef
define HOST_DTC_INSTALL_CMDS
^ permalink raw reply related
* [Buildroot] [PATCH] empty: bump to version 0.6.20b
From: Peter Korsgaard @ 2017-05-03 15:24 UTC (permalink / raw)
To: buildroot
In-Reply-To: <551bc33d600ea93bb2e336a6bd972a6861601daf.1493812863.git.baruch@tkos.co.il>
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Drop upstream patch.
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [PATCH] dtc: bump version to 1.4.4
From: Peter Korsgaard @ 2017-05-03 15:24 UTC (permalink / raw)
To: buildroot
In-Reply-To: <20170503123215.20544-1-peter@korsgaard.com>
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Adds overlay support.
> Drop the non-upstreamed 0002-extra-cflags.patch and instead simply pass the
> needed CFLAGS as make arguments. Passing the full upstream warning flags
> are not important in the Buildroot context, so this is simpler than
> maintaining a patch.
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [git commit] picocom: bump to version 2.2
From: Peter Korsgaard @ 2017-05-03 15:24 UTC (permalink / raw)
To: buildroot
commit: https://git.buildroot.net/buildroot/commit/?id=738544208aa98005b8296bb4364ef63b423715bd
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/picocom/picocom.hash | 2 +-
package/picocom/picocom.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/picocom/picocom.hash b/package/picocom/picocom.hash
index 674b620..16db03e 100644
--- a/package/picocom/picocom.hash
+++ b/package/picocom/picocom.hash
@@ -1,2 +1,2 @@
# Locally calculated
-sha256 6b152fc5f816eaef6b86336a4cec7cf1496b7c712061e5aea5a36f143a0b09ed picocom-2.1.tar.gz
+sha256 3e3904158d675541f0fcfdcd1f671b38445338f536080f5de8d6674b5f33d4ce picocom-2.2.tar.gz
diff --git a/package/picocom/picocom.mk b/package/picocom/picocom.mk
index 8e77f1d..07bda0e 100644
--- a/package/picocom/picocom.mk
+++ b/package/picocom/picocom.mk
@@ -4,7 +4,7 @@
#
################################################################################
-PICOCOM_VERSION = 2.1
+PICOCOM_VERSION = 2.2
PICOCOM_SITE = $(call github,npat-efault,picocom,$(PICOCOM_VERSION))
PICOCOM_LICENSE = GPL-2.0+
PICOCOM_LICENSE_FILES = LICENSE.txt
^ permalink raw reply related
* [Buildroot] [git commit] picocom: force target LDFLAGS
From: Peter Korsgaard @ 2017-05-03 15:24 UTC (permalink / raw)
To: buildroot
commit: https://git.buildroot.net/buildroot/commit/?id=add51b89bfb5ebe7b533e14714088a4d3912c9a0
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
This allows a static build of picocom when BR2_STATIC_LIBS=y but the toolchain
provides static and shared libraries.
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/picocom/picocom.mk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/picocom/picocom.mk b/package/picocom/picocom.mk
index 07bda0e..4e25556 100644
--- a/package/picocom/picocom.mk
+++ b/package/picocom/picocom.mk
@@ -10,7 +10,8 @@ PICOCOM_LICENSE = GPL-2.0+
PICOCOM_LICENSE_FILES = LICENSE.txt
define PICOCOM_BUILD_CMDS
- $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D)
+ $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) \
+ LDFLAGS="$(TARGET_LDFLAGS)" -C $(@D)
endef
define PICOCOM_INSTALL_TARGET_CMDS
^ permalink raw reply related
* [Buildroot] [PATCH 1/2] picocom: bump to version 2.2
From: Peter Korsgaard @ 2017-05-03 15:24 UTC (permalink / raw)
To: buildroot
In-Reply-To: <04e1e4d95a425dfc0e0650088cb0120a9f3e46a8.1493815595.git.baruch@tkos.co.il>
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [PATCH 2/2] picocom: force target LDFLAGS
From: Peter Korsgaard @ 2017-05-03 15:25 UTC (permalink / raw)
To: buildroot
In-Reply-To: <f7abac9c0ca017bffd3109f7df0d6bfa7f099281.1493815595.git.baruch@tkos.co.il>
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> This allows a static build of picocom when BR2_STATIC_LIBS=y but the toolchain
> provides static and shared libraries.
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
Is this only an issue for picocom 2.2, or also something we should
backport for the 2017.02.x branch?
--
Bye, Peter Korsgaard
^ permalink raw reply
* [Buildroot] [PATCH 2/2] picocom: force target LDFLAGS
From: Baruch Siach @ 2017-05-03 17:00 UTC (permalink / raw)
To: buildroot
In-Reply-To: <87h912c67z.fsf@dell.be.48ers.dk>
Hi Peter,
On Wed, May 03, 2017 at 05:25:52PM +0200, Peter Korsgaard wrote:
> >>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
>
> > This allows a static build of picocom when BR2_STATIC_LIBS=y but the toolchain
> > provides static and shared libraries.
>
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>
> Committed, thanks.
>
> Is this only an issue for picocom 2.2, or also something we should
> backport for the 2017.02.x branch?
Version 2.1 is also affected. But I'm not sure the issue is bad enough for a
backport.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
^ permalink raw reply
* [Buildroot] [PATCH] let-me-create: new package
From: Rahul Bedarkar @ 2017-05-03 18:01 UTC (permalink / raw)
To: buildroot
Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com>
---
DEVELOPERS | 1 +
package/Config.in | 1 +
package/let-me-create/Config.in | 27 +++++++++++++++++++++++++++
package/let-me-create/let-me-create.hash | 2 ++
package/let-me-create/let-me-create.mk | 20 ++++++++++++++++++++
5 files changed, 51 insertions(+)
create mode 100644 package/let-me-create/Config.in
create mode 100644 package/let-me-create/let-me-create.hash
create mode 100644 package/let-me-create/let-me-create.mk
diff --git a/DEVELOPERS b/DEVELOPERS
index 82eb819..3116dae 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -1309,6 +1309,7 @@ F: package/glog/
F: package/gssdp/
F: package/gupnp/
F: package/gupnp-av/
+F: package/let-me-create/
F: package/nanomsg/
N: Rahul Jain <rahul.jain@imgtec.com>
diff --git a/package/Config.in b/package/Config.in
index aaecd61..96ca201 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -1082,6 +1082,7 @@ menu "Hardware handling"
source "package/gnu-efi/Config.in"
source "package/hidapi/Config.in"
source "package/lcdapi/Config.in"
+ source "package/let-me-create/Config.in"
source "package/libaio/Config.in"
source "package/libatasmart/Config.in"
source "package/libcec/Config.in"
diff --git a/package/let-me-create/Config.in b/package/let-me-create/Config.in
new file mode 100644
index 0000000..14d9674
--- /dev/null
+++ b/package/let-me-create/Config.in
@@ -0,0 +1,27 @@
+config BR2_PACKAGE_LET_ME_CREATE
+ bool "LetMeCreate"
+ # build issues in static libs configuration
+ # see https://github.com/CreatorDev/LetMeCreate/issues/28
+ depends on !BR2_STATIC_LIBS
+ depends on BR2_INSTALL_LIBSTDCPP
+ depends on BR2_TOOLCHAIN_HAS_THREADS
+ help
+ This library is collection of small wrappers for some
+ interfaces on Ci40. It aims at making easier to develop
+ on this platform. It also provides wrappers for a few
+ clicks.
+
+ https://github.com/CreatorDev/LetMeCreate
+
+comment "LetMeCreate needs a toolchain w/ C++, threads, dynamic library"
+ depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS \
+ || BR2_STATIC_LIBS
+
+if BR2_PACKAGE_LET_ME_CREATE
+
+config BR2_PACKAGE_LET_ME_CREATE_EXAMPLES
+ bool "Build and install examples"
+ help
+ Build and install examples
+
+endif
diff --git a/package/let-me-create/let-me-create.hash b/package/let-me-create/let-me-create.hash
new file mode 100644
index 0000000..45b5e55
--- /dev/null
+++ b/package/let-me-create/let-me-create.hash
@@ -0,0 +1,2 @@
+# Locally computed
+sha256 5f42858a2062f34d2578e9cb1aed3ccb8d2409d908aa4c41a924418666d5f2bd let-me-create-v1.5.2.tar.gz
diff --git a/package/let-me-create/let-me-create.mk b/package/let-me-create/let-me-create.mk
new file mode 100644
index 0000000..3292de3
--- /dev/null
+++ b/package/let-me-create/let-me-create.mk
@@ -0,0 +1,20 @@
+################################################################################
+#
+# LetMeCreate
+#
+################################################################################
+
+LET_ME_CREATE_VERSION = v1.5.2
+LET_ME_CREATE_SITE = $(call github,CreatorDev,LetMeCreate,$(LET_ME_CREATE_VERSION))
+LET_ME_CREATE_INSTALL_STAGING = YES
+LET_ME_CREATE_LICENSE = BSD-3-Clause
+LET_ME_CREATE_LICENSE_FILES = LICENSE
+LET_ME_CREATE_CONF_OPTS = -DBUILD_STATIC=OFF -DBUILD_SHARED=ON
+
+ifeq ($(BR2_PACKAGE_LET_ME_CREATE_EXAMPLES),y)
+LET_ME_CREATE_CONF_OPTS += -DBUILD_EXAMPLES=ON
+else
+LET_ME_CREATE_CONF_OPTS += -DBUILD_EXAMPLES=OFF
+endif
+
+$(eval $(cmake-package))
--
2.7.4
^ permalink raw reply related
* [Buildroot] [PATCH] tinyxml2: fix build in static libs configuration
From: Rahul Bedarkar @ 2017-05-03 19:04 UTC (permalink / raw)
To: buildroot
tinyxml2 can build both static and shared libraries. By default, only
shared library is built. Shared/static builds are controlled using
separate cmake flags BUILD_SHARED_LIBS and BUILD_STATIC_LIBS.
In static libs configuration, we internally pass -DBUILD_SHARED_LIBS=OFF
cmake flag to build system which disables both shared and static builds
of library, resulting in failures while linking executable with library.
So pass -DBUILD_STATIC_LIBS=ON cmake flag in case of static libs
configuration.
fixes:
http://autobuild.buildroot.net/results/d30/d301bcbe5db26068b35eaa94bd816ae8cf8ef2e1
Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com>
---
package/tinyxml2/tinyxml2.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/tinyxml2/tinyxml2.mk b/package/tinyxml2/tinyxml2.mk
index bb1e167..e289ca9 100644
--- a/package/tinyxml2/tinyxml2.mk
+++ b/package/tinyxml2/tinyxml2.mk
@@ -10,4 +10,8 @@ TINYXML2_LICENSE = Zlib
TINYXML2_LICENSE_FILES = readme.md
TINYXML2_INSTALL_STAGING = YES
+ifeq ($(BR2_STATIC_LIBS),y)
+TINYXML2_CONF_OPTS += -DBUILD_STATIC_LIBS=ON
+endif
+
$(eval $(cmake-package))
--
2.7.4
^ permalink raw reply related
* [Buildroot] [PATCH] package: protobuf: fix build on gcc < 4.5.0
From: Mario J. Rugiero @ 2017-05-03 19:16 UTC (permalink / raw)
To: buildroot
Add upstream patch working around a gcc bug which got fixed in version 4.5.0.
Fixes:
http://autobuild.buildroot.org/results/77d/77dbb6bbbc0ea9e9bcdd22b10011ef9728c20d54/
http://autobuild.buildroot.org/results/21f/21f5e1ea4f37e1d174604d6da78c0e916c89f1e3/
http://autobuild.buildroot.org/results/24e/24e880086c87d40b5d79a90d805acc75b33d484c/
Tested with:
qemu_aarch64_virt_defconfig
Signed-off-by: Mario J. Rugiero <mrugiero@gmail.com>
---
package/protobuf/protobuf.hash | 1 +
package/protobuf/protobuf.mk | 1 +
2 files changed, 2 insertions(+)
diff --git a/package/protobuf/protobuf.hash b/package/protobuf/protobuf.hash
index 8c2ade37e..9b8e1e86d 100644
--- a/package/protobuf/protobuf.hash
+++ b/package/protobuf/protobuf.hash
@@ -1,3 +1,4 @@
# Locally calculated
sha256 51d773e4297238b282eaa4c1dd317099675b12eef2b414732b851c00459225c6 protobuf-cpp-3.2.0.tar.gz
sha256 da80c39838515913633f4cbd875fdd4ad711be95c83a50ff5096b9f1254033b3 416f90939d4de58fe1a4e2489120010313183291.patch
+sha256 309c8fd476863ddf9726a9700023d6349f7305e05bec071a06f4ccf7e90a7053 a83ac8663fb8042a881bc60b12a8bd3a0c03a3ff.patch
diff --git a/package/protobuf/protobuf.mk b/package/protobuf/protobuf.mk
index 610da8c04..92b6fe344 100644
--- a/package/protobuf/protobuf.mk
+++ b/package/protobuf/protobuf.mk
@@ -20,6 +20,7 @@ PROTOBUF_CONF_OPTS = --with-protoc=$(HOST_DIR)/usr/bin/protoc
PROTOBUF_INSTALL_STAGING = YES
PROTOBUF_PATCH = https://github.com/google/protobuf/commit/416f90939d4de58fe1a4e2489120010313183291.patch
+PROTOBUF_PATCH += https://github.com/google/protobuf/commit/a83ac8663fb8042a881bc60b12a8bd3a0c03a3ff.patch
ifeq ($(BR2_PACKAGE_ZLIB),y)
PROTOBUF_DEPENDENCIES += zlib
--
2.12.2
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox