Since gobject-introspection convert to python3 in oe-core,
incorrectly assigning PYTHON_PN with python caused host python3
loaded.
On centos7, built with qemuarm failed:
...
arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option
'-mtune=generic'
..
arm-poky-linux-gnueabi-gcc: error: unrecognized command line option
'-m64'
Traceback (most recent call last):
File "/usr/lib64/python3.4/distutils/unixccompiler.py", line 126, in
_compile
...
The native python3 should be loaded.
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Use github for SRC_URI
Reorder the linker flags so that we can remove disabling --as-needed
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Use git fetcher to use tip of tree, the tree does not
get frequent fixes. Its not disruptive to use git fetcher
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
The commit 187798c3bd (gvfs: update
1.28.3 -> 1.32.1) caused a regression where images that use rpm4 can
no longer assemble correctly because it includes polkit rules.
At image creation time rpm4 will detect a mismatch of the ownership
with the polkit rules.d directory as follows:
file /usr/share/polkit-1/rules.d conflicts between attempted installs of gvfs-1.32.1-r0.1.core2_64 and polkit-0.113-r0.8.core2_64
file /usr/share/polkit-1/rules.d conflicts between attempted installs of libvirt-1.3.5-r0.9.core2_64 and gvfs-1.32.1-r0.1.core2_64
The libvirt which also appears in the error message has already been
fixed in the meta-virtualization layer in a similar maner. (http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=67c86c4962170354ad8a2ec4cdbb9bc0056cfd66)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
1) Upgrade openldap from 2.4.44 to 2.4.45
2) Delete openldap-CVE-2017-9287.patch, since it is integrated upstream.
3) License checksum changed, since the copyright years were updated.
Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
If "--with-pidfile-dir" configure option is not specified, then the syslog-ng
configure script assigns PID directory to /var/lib/syslog-ng; which is
where the PID file of syslog-ng process is created. But the syslog-ng
initscript (/etc/init.d/syslog-ng) uses /var/lib/syslog-ng/
as PID directory, this results in not stopping/restarting syslog-ng daemons
when it was requested to do so.
For example:
-- snip --
root@qemux86:~# /etc/init.d/syslog status
/usr/sbin/syslog-ng (pid 345 344) is running...
root@qemux86:~# /etc/init.d/syslog stop
Stopping syslog-ng:.
root@qemux86:~# /etc/init.d/syslog status
/usr/sbin/syslog-ng (pid 345 344) is running...
root@qemux86:~#
-- snip --
Hence set --with-pidfile-dir to "/var/run/syslog-ng", so that syslog-ng daemon
can be stopped/restarted via initscript.
Signed-off-by: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
- Fix compile failure against musl C library
- Fixed when compile with "-Wformat -Wformat-security -Werror=format-security"
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
- Fix compile failure against musl C library
- Fixed when compile with "-Wformat -Wformat-security -Werror=format-security"
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Tell Meson that even if it looks like the architectures are compatible, not to
bother executing binaries: differences in tunes, C libraries and so on mean
binaries may not work.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Hongxu Jia
Khem Raj
Jason Wessel
Huang Qiyu
Derek Straka
Jagadeesh Krishnanjanappa
Jackie Huang
Ross Burton
Martin Jansa
Mikko Rapeli
Romain Bazile