When guile is installed from sstate, if the compiled files get a modified time
older than the source files then guile will produce warnings like this:
;;; note: source file /data/poky-master/tmp/sysroots/x86_64-linux/usr/share/guile/2.0/ice-9/boot-9.scm
;;; newer than compiled /data/poky-master/tmp/sysroots/x86_64-linux/usr/lib/guile/2.0/ccache/ice-9/boot-9.go
Not staging the files and letting guile re-compile them on demand won't work:
;;; compiling /data/poky-master/tmp/sysroots/x86_64-linux/usr/share/guile/2.0/system/base/compile.scm
;;; it seems /data/poky-master/tmp/sysroots/x86_64-linux/usr/share/guile/2.0/system/base/compile.scm
;;; is part of the compiler; skipping auto-compilation
So, use a sstate postinst function to explicitly touch the compiled files after
the extraction to ensure that they are fresher.
[ YOCTO #3370 ]
(From OE-Core rev: cb8fbc332f730cbb4d9c9866ee7b95d62245d121)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For a completely quiet boot using recent versions of utilities, the
/etc/fstab and /var/lock need to be available.
(From OE-Core rev: d7a8154d575f918a0a20cb0e3a8f65d02ed32f30)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
list_installed_packages should output uniform formatted archs for all
packaging system(deb, rpm and ipk), for they are used by common code to
grab the package infos. Otherwise, it will lead some -dbg packages to be
missed processing in come cases.
It's introduced by commit: fc985f51, package_rpm.bbclass: fix the arch
(replace "-" with "_").
Fixed by replacing "_" back to "-" in list_installed_packages, make it
output real arch values which can be safely used.
(From OE-Core rev: 554f2436435bf96c6735827f491c1b78b198c016)
Signed-off-by: Ming Liu <ming.liu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch contains two fixes:
* if the user wants to install the SDK in a directory that already
contains a SDK for the same architecture, a warning will be shown;
* when the symbolic links are relocated use -n option. Otherwise,
symbolic links to existing directories will be created in the
directory itself;
[YOCTO #3401]
(From OE-Core rev: cd035f170a2448b9ebcf0cfac5d4c0fa472b7049)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- fix WARNING: Failed to fetch URL http://www.apache.org/dist/subversion/subversion-1.7.6.tar.bz2
- subversion-1.7.6_mod_dontdothat_svnserve_only.patch doesn't seems to be useful,
cc Marcin to get confirmation
(From OE-Core rev: 60ac9eccd6101967a89ab74344920b4b3ca8cd5f)
Signed-off-by: Eric Bénard <eric@eukrea.com>
Cc: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't implement module onig in our recipes,
so we should explicity disable its invoke in slang
to avoid that slang's configure incorrectly tests
the existence of onig.
[YOCTO #2820]
(From OE-Core rev: 38c1b92f188b7e9b27d7ce3f6a8ffbdd7e19f90d)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The optimisation handling code is not version specific, so move the
fix code to the .inc.
(From OE-Core rev: 22dfc7d5738a20f015d9de693f0c2accfa685560)
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License md5sum changed only because libpng version numbers and
release dates mentioned in it.
(From OE-Core rev: b3f99e01c249c34d6083eec3159d5ba6b54df97f)
Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* all gst* packages were producing LC_MESSAGES/.mo instead of
LC_MESSAGES/gst*.mo and it was leading to file conflicts between gst*
packages too
* for more details see
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-November/032233.html
* buildhistory diff, confirms issue fixed
f2c0888c0e
* Thanks to Enrico for simplier solution
(From OE-Core rev: f50e2984d9411a059b86d6c158e9416fceb84c3d)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The force_postinstall option was missing and some packages were
configured on target rather than on host at rootfs time.
(From OE-Core rev: dfadfaa0b38678029ffebe14f15e2dbc148cb1fb)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A security flaw was found in the way ssh-keysign,
a ssh helper program for host based authentication,
attempted to retrieve enough entropy information on configurations that
lacked a built-in entropy pool in OpenSSL (a ssh-rand-helper program would
be executed to retrieve the entropy from the system environment).
A local attacker could use this flaw to obtain unauthorized access to host keys
via ptrace(2) process trace attached to the 'ssh-rand-helper' program.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-4327http://www.openssh.com/txt/portable-keysign-rand-helper.adv
[YOCTO #3493]
(From OE-Core rev: bdce08215396e5ab99ada5fa0f62c3b002a44582)
Signed-off-by: Li Wang <li.wang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The autoconf macros in autogen use dpkg (!) and guile-config to determine
what/where Guile is.
If the build host has an installed guile, these can produce conflicting results.
More interestingly, if the Guile library source and compiled form have bad
timestamps (source newer than compiled) the configure scripts knows that Guile
is present but doesn't know what version it is, resulting in compile errors.
[ YOCTO #3370 (partially) ]
(From OE-Core rev: 8a4f07d5111feaa3114e039431785d6ad37529b2)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The build summary is meant to reflect key configuration variables. Information
about the build system we're running on is important but currently missing
from the information displayed.
Printing TARGET_SYS removes the need to print TARGET_OS and TARGET_ARCH
and we add BUILD_SYS and NATIVELSBSTRING to show information about the
build system.
[YOCTO #3456]
(From OE-Core rev: 764cc1eb3043c84121f597d2271108b91052095e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Recipe already contains a patch for mips arch but not for mips64.
For mips64 arch 'mips' was not available in OVERRIDES, rather mips64
was there. So added the same patch for mips64 arch using mips64.
(From OE-Core rev: 5fa9f9b626daed83c8d31755040574c13ad25459)
Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently there is some odd behaviour of the packagegroup class in relation
to sstate since it sets PACKAGE_ARCH = "all" but does not use the allarch class
leading to it being undetected by sstate.
Previously it was not possible to use allarch as the recipe couldn't "undo"
settings made by the allarch class. Since this no longer happens when
PACKAGE_ARCH != all, we can use the allarch class.
This patch also fixes up one case we need to preserve TRANSLATED_TARGET_ARCH
and ensures sstate only assumes allarch when PACKAGE_ARCH is "all".
(From OE-Core rev: 591fa7c1ab9e9ff75fdce602c77ecdeda3a255d9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We have cases where we'd like to inherit this class by default but allow
special cases to override it. This change makes the code of the class
conditional on PACKAGE_ARCH remaining set to "all", allowing it to be
overridden. packagegroup usage is one case this is desirable.
(From OE-Core rev: 7dd91402b719ac62b51088f234354f82bfa9c4b6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the interests of simplifying things, remove P and PN from FILESPATH,
instead relying on the BP and BPN versions which work in 99% of cases.
In any problematic case such as a -native only recipe, either the patch
directory can be renamed or the recipe can set FILESPATH specifically.
(From OE-Core rev: fb359583b659cda643973fa285002aaffb729a51)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Files are very rarely, if ever placed in ${PF}. If a recipe needs to do this,
it can easily append to FILESPATH so it makes sense to drop this from the
default search path.
Equally, using FILE_DIR as part of the search path leads to 'bad' SRC_URI
entries and/or file layouts which are not preferred. I'm therefore of the
opinion we should also remove this from FILESPATH and encourage people to
cleanup any places this breaks my correcting the layouts to match the standard
or worst case adding to FILESPATH in recipes that need it.
These changes work towards making the system more friendly as users won't be
greeted with huge search paths we rearely use making the "correct" layout
more obvious.
(From OE-Core rev: 3efa13cd76bbd5611805021945fc9def88d9fd93)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
FILESPATH is the preferred way of finding files now. Having a value
for FILESDIR which defaults to paths which will have already been
searched is pointless at best. This is the final step in letting
us drop FILESDIR support entirely from bitbake at some future date.
(From OE-Core rev: d6e5ceafcaef06b8a3f9acc2aa826a40a016f913)
(From OE-Core rev: 3bb5c6bd51c91ada7fc17451627b8954dbe9c09c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* this is mostly for backwards compatibility and to share binary feed
like it was before, but now without missing different -mtune in it
* if you want to build some package with -mtune add something like this
to your distro config
DEFAULTTUNE_qemuarm_pn-openssl = "arm926ejs"
DEFAULTTUNE_qemuarmx_pn-openssl = "xscale"
be aware that if you do this you should do it also for all packages
which depends on openssl because if you dont and you build e.g. dhcp,
then dhcp build for arm926ejs (even with DEFAULTTUNE armv5te) will
depend on openssl with arm926ejs, so dhcp in armv5te feed will be
rebuild after each MACHINE switch.
* cortexm3, cortexr4, iwmmx and ep9312 are using own DEFAULTTUNE because
they define also different -march
* shared feeds are
armv4t: arm920t, arm9tdmi
armv5te: arm926ejs, xscale
armv7a-neon: cortexa8, cortexa9
(From OE-Core rev: a11bdc36a1be18cc5aa14682b2a2c9ee83141f51)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* without this tune-xscale and tune-arm926ejs were both creating
packages in armv5te feed, but each with different -mtune, with
OEBasicHash enabled it was causing each package to rebuild with new
-mtune after MACHINE switch, but that doesn't make sense with output
stored in the same armv5te feed
* this makes different feed for each -mtune, but more generic one to be
selected with DEFAULTTUNE
* tune-iwmmxt and tune-ep9312 were already using this, just move it
bellow AVAILTUNES and use ARMPKGARCH_tune-foo syntax
* tune-cortexr4 and tune-cortexm3 are using armv7r/armv7m as ARMPKGARCH
because there isn't another tune to use the same -march
(From OE-Core rev: cffda9a821a3b83a8529d643c567859e091c6846)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-foo is not valid override, for it to work I had to add
ARMPKGARCH = "${ARMPKGARCH_tune-${DEFAULTTUNE}}"
but that doesn't work without value defined for every supported
DEFAULTTUNE value, otherwise it's expanded like this
TUNE_PKGARCH (${ARMPKGARCH_tune-armv5te}te).
(From OE-Core rev: 31e4f2dee990ee7f5d7491b65565e71d7d580209)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* we don't care about expression but value
* e.g. tune-xscale and tune-arm926ejs have different expression
in TUNE_CCARGS but with the same DEFAULTTUNE the result is the same
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-September/030032.html
(From OE-Core rev: 03f1e34ea3ce80931e9c3cd2ab22824f28a7233b)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* probably copy&paste error from tune-cortexm3.conf
commit 789dcb8e68a2ab9784ac10ab36815010c61af2fc
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Mon Jul 25 19:03:24 2011 +0100
Add ARM tune file overhaul based largely on work from Mark Hatle
(From OE-Core rev: 4827232077e4a059d6aa818f89c83c42bb91949a)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* without this you'll get different sstate checksum for webkit-gtk and
cairo even when you build them with DEFAULTTUNE == armv5te
* maybe this isn't needed at all anymore or if it is then it should be
applied in arm-armv5.inc for all armv5te devices, not only xscale?
(From OE-Core rev: c51643a510da6d1c3426b3de8f18ae864cb073a4)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If libICE exists when this package configures, libICE and libSM are
added to the list of included libraries. Adding libsm and libice to the
list of dependencies ensures they'll be present and makes the contents
of this package more deterministic.
(From OE-Core rev: 0d8adb1b57bf435f888c9357d40d1e2dae10d07f)
Signed-off-by: Gilbert Coville <gilbert_coville@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some bad logic in license.bbclass misses certain package level
LICENSEs.
(From OE-Core rev: c5a171d5817233c0371e6f5b19f57f3c4b84f5ac)
Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
eglibc fails to compile if someone tries to compile an entire image as -O0:
error "glibc cannot be compiled without optimization"
so in this case, force to use -O2 and give a note about it.
[YOCTO #3405]
(From OE-Core rev: 9ca1c6120fad5dcae1694e8e37331c1b903f1fd0)
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gdk.c depends on gtk-types.defs but
gdk/Makefile.am miss this. This will cause
build error sometimes when built
with multi-jobbing, so add gtk-types.defs into
gdk.c dependence.
[YOCTO #3460]
(From OE-Core rev: 0e97ef30c3819e22f43d88e817e8a8b39ca30e5d)
Signed-off-by: Song.Li <Song.Li@windriver.com>
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This changeset updates existing OE patches to commits from upstream git
tree and adds everything needed to get AArch64 support working.
(From OE-Core rev: f67ad1c2634b3c7a46c43ebdbdffbe7a083e99ed)
Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Do not invoke CURL_SET_COMPILER_DEBUG_OPTS in configure.ac.
This will allow debug options set in our CFLAGS to be
used.
(From OE-Core rev: ba151faad47e6874b295ebd9699ce154bc4ff741)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Makefile makes use of CFLAGS_NOOPT. If we set that
when calling make we can enable options like -g. The
Makefile will override any optimization to -O3.
(From OE-Core rev: 7f26794dc9f2e78ee8aed1e23752acb709345c6f)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Makefile makes use of CFLAGS_NOOPT. If we set that
when calling make we can options like -g. The Makefile
will override any optimization to -O3.
Upstream-Status: Pending
(From OE-Core rev: df2c260f9cda2e291c72f7debe1e6d53846ce058)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add CFLAGS to EXTRA_OEMAKE to allow us control over
debugging and optimization.
(From OE-Core rev: 2e123bb1b3ee023a020798972821f32b1e0054e6)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Makefile computes CFLAGS, but we can see that our
defaults get included by using CCOPTS to pass them
to make.
Upstream-Status: Pending
(From OE-Core rev: 8d71f7d33c18bb0a975eb86d602bda42db4baa2c)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add some configurations, make rndc command be able to controls
the named daemon.
(From OE-Core rev: 9ad8f7c2bae021269e9a8e35f9fc44a16d23bb6f)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
EXTRA_OEMAKE in the recipe currently discards the
environment CFLAGS when setting CFLAGS passed to make.
We change that to include these options.
(From OE-Core rev: 67924616963fee9cb9f2405d93c74a8cc10b6eab)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building a QT application using OE_QMAKE_CC/OE_QMAKE_CXX, the
--sysroot was not included and the compilation would fail. The user had
to add the option manually which was not very user friendly. This
happened only when installing the SDK in another location than the
default one. Since CC/CXX/LD had this option already included, reuse them.
[YOCTO #3409]
(From OE-Core rev: 758f56523daa7d8c8b459757c70b50421d28b8dd)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* without _${PN} suffix they are invalid:
opkg install bash-4.2# opkg install xf86-video-omapfb
Package xf86-video-omap-doc is already installed on root.
* it's not upgrade to omapfb driver but different driver,
so let BSP maintainers decide which one works for their MACHINE
* without this xf86-video-omap (or -doc, -dbg, ...) can be pulled
to image even when XSERVER clearly says xf86-video-omapfb
(From OE-Core rev: ef0f8611001c435abab60c464d31134ef027d7c2)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton
Marko Lindqvist
Otavio Salvador
Ming Liu
Laurentiu Palcu
Eric Bénard
Hongxu Jia
Jackie Huang
Andreas Müller
Martin Jansa
Li Wang
Richard Purdie
Cristian Iorga
Noor Ahsan
Gilbert Coville
Flanagan, Elizabeth
Marcin Juszkiewicz
Joe Slater
Roy Li