linux/meta-openembedded.git/meta-oe/conf, branch sumo

meta-*: add LAYERSERIES_COMPAT to layer.conf files

2018-04-13T19:43:37+00:00

Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster

meta-oe/conf/layer.conf: Remove "id" from HOSTTOOLS

2017-10-15T17:29:40+00:00

The "id" HOSTTOOLS should be add to the HOSTTOOLS definition on OE-Core; especially "id" is used on "rootfs_check_host_user_contaminated" rootfs-postcommand which is available on OE-Core thus belonging to it. Signed-off-by: Otavio Salvador Signed-off-by: Martin Jansa

security_flags.inc: Delete

2017-09-08T20:38:12+00:00

OE-Core has now reworked the PIE flags, where they are implicitly passed by compiler when security flags are enabled None of these pinnings are needed anymore, since these packages compile fine with security flags enabled Signed-off-by: Khem Raj Signed-off-by: Martin Jansa Signed-off-by: Joe MacDonald

layer.conf: remove FREESMARTPHONE_GIT variable

2017-08-31T12:22:12+00:00

* nothing in meta-oe is using it now and meta-fso is also gone now Signed-off-by: Martin Jansa

layer.conf: exclude android-tools->android-tools-conf from siggen

2017-08-31T12:21:43+00:00

* when android-tools were moved from meta-smartphone/meta-android to meta-oe this part was overlooked and my jenkins jobs didn't detect it because I was still including meta-android layer. Signed-off-by: Martin Jansa

meta_oe_security_flags.inc: Disable PIE for libdevmapper

2017-05-04T07:18:58+00:00

Since libdevmapper was split out from lvm2, it now needs its own entry to disable building with -fpie. Signed-off-by: Peter Kjellerstedt Signed-off-by: Martin Jansa

crash: 7.1.5 -> 7.1.8

2017-04-18T12:21:41+00:00

1. Upgrade crash to fix build failure with glibc 2.25. 2. Add the "id" to HOSTTOOLS in meta-oe/layer.conf Signed-off-by: Dengke Du Signed-off-by: Martin Jansa

meta_oe_security_flags.inc: Disable PIE for luajit

2016-12-02T08:26:33+00:00

Signed-off-by: Khem Raj Signed-off-by: Martin Jansa

meta_oe_security_flags: disable PIE for libdbus-c++

2016-12-02T08:23:44+00:00

The short version - it ain't working. The long version: For shared libraries made from C++ sources, configure runs some code to determine how to link shared libraries (from libtool.m4) using g++. In particular, it calls g++ ${CFLAGS} -c conftest.c g++ ${CFLAGS} -nostdinc -shared -v conftest.o to then parse the gcc -v output. If CFLAGS contains -pie -fpie, g++ adds Scrt1.o to the objects being linked together to form the final output. Once Scrt1.o is pulled into a shared library, it becomes impossible to link this DSO against a final binary. I didn't investigate why, by I suspect because of -Wl,relro -Wl,now libtool takes note of Scrt1.o (and all other libraries added by gcc, but those don't matter here) and adds it everywhere a shared library is being created, see predep_objects= and postdep_objects= in the 'LIBTOOL TAG CONFIG: CXX' section. In other words, the the shared library created during the build can't be linked against. This includes some applications that are part of the libdbus-c++ source tree, but also any other external user. While I am not sure if the root of the issue is in - gcc (should it really add Scrt1.o despite -shared), or in - libtool (should it filter out -pie -fpie during the configure step), or even in - OE (should it really be adding -pie -fpie to everything, even shared libraries by default and unconditionally), we can make things work by using SECURITY_NO_PIE_CFLAGS instead. Signed-off-by: André Draszik Signed-off-by: Martin Jansa

libvdpau: Disable PIE

2016-11-26T00:04:53+00:00

Signed-off-by: Khem Raj