As binutils is required by perf to build and is GPLv3 licensed adding
GPLv3 to INCOMPATIBLE_LICENSE will cause linux-yocto to be skipped.
Long term we should look at moving perf to a separate recipe but as a
short term solution this patch will ensure that when GPLv3 is in
INCOMPATIBLE_LICENSE perf is not built and it's dependencies are not
added to build.
Fixes [YOCTO #1879]
(From OE-Core rev: ce61f9031b54067bffa304dab90c31278631dcdf)
(From OE-Core rev: 8c1a2fa)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed this line
ac_cv_sizeof_unsigned_char=${ac_cv_sizeof_unsigned_int=1}
as this line
ac_cv_sizeof_unsigned_char=${ac_cv_sizeof_unsigned_char=1}
This issue was causing guile recipe to compile-fail for x86 target.
(From OE-Core rev: d71df3cc2ff2504d61078c578c0e73bbf53b6651)
(From OE-Core rev: 69ac1ad415634e125d9c366efc91353624225ad2)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this fix, when packages are being built using distutils and
the python packages were deployed from sstate-cache is it possible
that the LD command will contain an invalid sysroot override.
We can fix this by always exported LDSHARED, which is the env var
that distutil looks for to override creating shared libraries.
(From OE-Core rev: 3f6b859a29ba7f570b9dae3b5bb7ab4bd7b8cee4)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #1909]
Install autoconf-nativesdk and automake-nativesdk to host.
(From OE-Core rev: 0b3842f5c3c1587d25e70bc8223e2b144b9043cb)
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To quote my report of this to the git mailing list:
"""
I have a problem with git clone commands using alternates failing by
mixing up different repositories. I have a situation where I could end
up with both:
/srv/mirrors/repo
/srv/mirrors/repo.git
as bare clones.
I then try cloning "repo" with alternates with the command:
$ git clone -s -n /srv/mirrors/repo /tmp/foo
Cloning into /tmp/foo...
done.
$ cat /tmp/foo/.git/objects/info/alternates
/srv/mirrors/repo.git/objects
Note how I'm now referencing repo.git, not repo. This doesn't work as
expected giving some very bizarre results when actually using the
repository.
I appreciate this is a rather bizarre corner case but its one that is
breaking the build system I work with. Ideally people would use a
consistent URL for the same repository but we have an example where they
haven't and this really shouldn't break like this.
Looking at the code, the cause seems to be
clone.c:get_repo_path():
static char *suffix[] = { "/.git", ".git", "" };
since its looking in order for:
repo/.git (fails)
repo.git (suceeds, incorrect)
repo (never looked at)
I'm not sure what would break if that order were to change, swapping the
last two options.
I can "force" the issue by running:
git clone -s -n /srv/mirrors/repo/ /tmp/foo
but this results in the slightly odd looking:
$ cat /tmp/foo/.git/objects/info/alternates
/srv/mirrors/repo//objects
which does at least work.
"""
This patch adds the trailing slash to ensure the correct repository is
referenced at the expense of some ugliness in the alternates file.
(Bitbake rev: d978e7b35550e3785c7c567ffe4c40a3c3947450)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kernel SRCREVs to pickup the stable 3.0.18 release.
(From OE-Core rev: b1a4d1a912af39dc3be7433a1e2ed4c48d5ffb93)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In OpenVZ containers (and probably lx containers as well),
the diskstats entry is not even present. Use the "NoLogicalDrive"
introduced by Elizabeth Flanagan in such case.
This allows the bitbaking to occure within such containers.
(From OE-Core rev: 16e09b850dcb44cb1afe411439e40a4bae7e8002)
(From OE-Core rev: 84bd443d82d8022027180b6ef1f7b7cfc7d06420)
Signed-off-by: Jean-François Dagenais <jeff.dagenais@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GCC will define __ARM_ARCH_4T__ when building with "-march=armv4t" so
we can check this to turn off the use of 'clz' instructions, which
otherwise would cause compile errors like "selected processor does
not support ARM mode `clz r3,r0'".
(From OE-Core rev: 6859e3fc34269620146d26eeecc9b93c3a9d7055)
Signed-off-by: Wolfgang Denk <wd@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We have witnessed non-deterministic failures of perf for some platforms
whilst looking for bfd.h, a header provided by binutils.
(From OE-Core rev: ab56f27d96cbd2c79ca16d12333687ca9720934c)
(From OE-Core rev: eb014a992e0f3e6ddb4eee8e1287d28ac2f09e00)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add Patch to disable the XML::Parser check in the target
intltool.m4, this check will find the host (not native)
XML::Parser if it's installed possibly causing Host
contamination, but will also fail configuration if XML::Parser
is not installed on the host.
Since we know that XML::Parser is installed on the image, we don't
really need this check, so comment it out.
From RP in mail thread:
> If the recipe needs perl for
> some other reason than intltool, it needs perlnative but it if only
> needs perl for intltool, we shouldn't need the dependency. The .m4 macro
> checks are well intended but don't fit the way we use perl. I really
> don't want to end up in a position where intltool automatically means we
> have to add perlnative as a dependency and we've previously seen many
> problems related to that.
(From OE-Core rev: 264fb6c5a4875cd8969a24a9f0301ed916ab827b)
(From OE-Core rev: 085c76298891dc0b0e2207ef929569672c9cb254)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
configure of cvs packages was failing on the meta-toolchain for a x86_64 target.
Configure error reported:
checking whether printf supports %p... configure: error: cannot run test program while cross compiling
This fixes [YOCTO #1781]
(From OE-Core rev: 061818adbea1af9e98fe0fdf81b21f1e7f210c00)
(From OE-Core rev: 5e0e0cf5b9d380120187d368683e9f95c1b8f6d1)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
USER is the correct variable to use, also this can affect sstate
cache as well.
(From OE-Core rev: 898bf0294d01172b0990d218ecc5fecdba962711)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this simply changing the number of threads via
PARALLEL_MAKE can invalidate sstate-cache
(From OE-Core rev: b2411e12f9ea32012af20ecee1e09d95db129b75)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backport fix for PR 47551 fixes the ICE seen on armv7-a/qt4-x11-free
Bump up SRCREV past gcc 4.6.2 release
(From OE-Core rev: dd2fdf9f5a3923c37e4ea2e46e347bb0657c2f5b)
(From OE-Core rev: 320f6b71e502d65421a01a2f280c9e2c8f046619)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If two packages were available of differing priority, this would confuse
opkg and it was ignoring the dependency in the new dependency ordering
code. This changes it not to ignore these cases by setting the badly
named 'quiet' parameter accordingly.
(From OE-Core rev: c38693f78c968ab5f4bb557c20d1c8c55393ed6b)
(From OE-Core rev: 4c75318b75c4776cc469cc2c6511596bc7befbb4)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this the command will add a route for the subnet 192.168.7.0 which
means multiple qemu instances can't operate correctly since all but the last
one will be masked out.
(From OE-Core rev: 9e00d6b343120496ec0dd72240c7b04e0a8b7eaa)
(From OE-Core rev: f5bcd56dcca7daad6aa6b4371d4e331d8ffd11eb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This break things for on target opkg usage since $D must remain
unset there.
(From OE-Core rev: 746ae269a475857ae57095b1fd164fe195b3d051)
(From OE-Core rev: aa632292cc55b997a5b808b6c4a70ce33a3b9e7e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This addresses some of the concerns about the previous opkg changes
allowing it to break out of circular dependency loops with just a notice
in the logs rather than effectively going OOM.
(From OE-Core rev: 5a2b67b8faad3dd5417ba89d8e82ca564753ccc9)
(From OE-Core rev: 29f77f865434cc956e6bbccaee81ff458492ec46)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a major issue with opkg images at the moment as preinst
functions are not being executed before their dependencies are installed
and this is leading to corruption of images containing avahi/dbus in
particular.
There are various changes in upstream opkg in the last 8 revisions which
make changes in this area but sadly these aren't enough to get things
working for us. I've updated to the latest svn revision with this patch
since it makes sense to pull in those changes first and then supplement
them with the attached patches.
There is a full description of the patches in the patch headers but in
summary they:
a) Ensure preinst functions execute with their dependencies installed.
This is a pretty invasive change as it changes the package install
ordering in general.
b) Ensure opkg sets $D, not $PKG_ROOT which we don't use
c) Change opkg to allow execution of postinstall functions which fail
resulting in execution on the target device as rootfs_ipk.bbclass
currently does manually.
The remaining changes interface this with the rest of the OE build
infrastructure, adding in the option to tell opkg to run the preinst and
postinst functions, ensure the correct environment is present for the
postinst scripts and removing the now unneeded rootfs_ipk class code
which opkg now does itself.
[YOCTO #1711]
(From OE-Core rev: 2feba313c991170747381c7cf821a45c2cd04632)
(From OE-Core rev: b7e2eff8c18bc59605fb711ac4540985c71f155a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
dpkg-native's update-alternatives is broken for offline work so
don't install it.
Also list update-alternatives in the multiprovider whitelist to
avoid unwanted multiple provider warnings when multiple package
backends are enabled.
(From OE-Core rev: 300336fc4a310ed16a14ad041744708d54aae189)
(From OE-Core rev: c90b1faa34e908c7f63e1a64027873858e6d7e8a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Occasionally we keep seeing "unable to open temp file" messages during
do_package_write_rpm tasks. This appears to happen when multiple
processes are writing rpm files and is likely due to using the
shared system temp directory. This patch changes the tmp path
to the package work directory meaning conflicts should become
a non-issue.
(From OE-Core rev: b2ef543284c8c8d0d3badb2e1bcadad1106982d2)
(From OE-Core rev: 018442ed2cd251f85212dfa1d03c0b24a0750bfa)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If PACKAGE_CLASSES does not set package_rpm as the first item, the root filesystem
will not be generated based on rpm. We need remove rpm/zypper tests against
non-rpm filesystem.
[YOCTO #1757]
(From OE-Core rev: 43adb8dcf4461b68a7ce0ba9d8acdb2012a70416)
(From OE-Core rev: f541517be97e27951157e1dd10256e132c31ab1f)
Signed-off-by: Jiajun Xu <jiajun.xu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If rpm-native was built in an alternative location, it may not relocate correctly
unless the rpmpopt and macros paths are explicitly specified.
This fixes errors seen on the Yocto autobuilder where pkgconfig
"provides" entries could disappear leading to image dependency failures.
(From OE-Core rev: fb01bd81197057e62106aac966f9ebc4c5054f97)
(From OE-Core rev: 15f50ab3ee454dc3510801d61bb09bf37d78d1af)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need to build texinfo-native to get and install the makedoc tool
[YOCTO #1664]
(From OE-Core rev: 8899f4840787ef043d952f8ea2ce5d78e5cc41ab)
(From OE-Core rev: 8e802c0ed491967cd254dce1555a960382a79247)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Need to have the texinfo-native build and install a host sysroot makedoc
binary and then patch the target build to use this binary. This requires
that we don't ASSUME_PROVIDED texinfo-native any longer since we need to
install this makedoc tool which is not part of the normal distrubtion.
[YOCTO #1664]
(From OE-Core rev: 9fa98de54a73465f06484ba863eccf1e07cc1e2a)
(From OE-Core rev: 007bbb23808cc5b036829915e3dfa04f590a05d8)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building qemu-native, if the linux kvm header is unavailable (as
it is on CentOS 5.x 32-bit) then do not pass the --enable-kvm switch to
the configure script, thus avoiding failed do_configure.
(From OE-Core rev: 8c21c71f005b601f58925e9912f2cf44127e291d)
(From OE-Core rev: 44d9e208c97ec1e3c5ba0a8dc6c10cef12dc270d)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Unfortunately we now have code in BitBake which is parsed before the
current version check and is incompatible with Python < 2.6. Rather than
fixing this and being eternally vigilant for >= 2.6 feature usage, just
add a version check to the wrapper script.
(From OE-Core rev: 9b8a48efa3b80fea34efa51de44d10ff2b1e3193)
(From OE-Core rev: c3ba7e8f7aca8b49739b3b92aec723c5f3375bc0)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If /dev/net/tun is either not present or is not writable by the
user, then show an appropriate error message. (QEMU needs access to this
device in order to enable networking; it may be missing if it is not
enabled or loaded into the kernel, and some distributions such as CentOS
5.x set restrictive permissions upon it.)
(From OE-Core rev: a00b94900d437828f25debce1c30ffcc0bbf29e9)
(From OE-Core rev: b66fa6238a8f9c0972a60932941997517826ff03)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #1174]
Rpm logs will grow indefinitely, so change the config to flush those old logs.
(From OE-Core rev: e2c4dff079722f256ddcab9630b5b3f8f6421cc9)
(From OE-Core rev: f235c7a320c401fea70a578186c5cf80dd597fcd)
Signed-off-by: Mei Lei <lei.mei@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this, if rpmddeps came from a sstate package which was relocated
it might not find its magic file and if that happens, requires/provides
in packages could get corrupted. This leads to failures at rootfs time
during builds with messages like:
libdbus-1.so.3 is needed by libdbus-glib-1-2-0.92-r1.armv5te
since the provides would be missing in the dbus package.
(From OE-Core rev: abe2a948905a997314c61a8fcd35e2b42a3f4408)
(From OE-Core rev: 5ee145ebbb32824e3870b6dd689ce2b3f9bf3f17)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
According to XChangeProperty doc, array of "long" should be used when format is
32. Wrong _NET_WORKAREA parameter caused blank screen in matchbox-desktop on 64
bit platform.
[YOCTO #1689] got fixed.
(From OE-Core rev: 381c7857a5b303bf9eadd7fffc39d17a2b8e31f2)
(From OE-Core rev: 869601da9aa43d77564c37d291d9072b9896d3e6)
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable was being expanded immediately and pulling in
paths to the variable dependecies which causes it's sstate-cache
to never be reused
(From OE-Core rev: ddb8d3de34f809b9c72eb3a2223a74f75eff7911)
(From OE-Core rev: 8f616810b868a30fc01550c017f9fc14220ae7d8)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The path to the native perl was incorrect leading to rootfs failures. This
patch corrects that problem.
(From OE-Core rev: 044324465bd54d53ae768f3c1e7468ae0e0c6200)
(From OE-Core rev: 8fa40eb1c2a32782b8a74bee70fa81b2c3e5cbaf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The value of baselib can be constructed in several different ways
and from a sstate perspective we don't care how it was made up,
we only care what the final value is. This uses the new functionality
in bitbake to ensure we only include the value of baselib and not
any intermediate dependencies.
[YOCTO #1583]
(From OE-Core rev: c38567894ebc31ac977f2bc89a076d0380bddcf8)
(From OE-Core rev: 8b70cfe7a1768b8bf1e5b7e390276518e16f14af)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the sstate files are installed into a sysroot from the sstate cache,
the directory to the main sysroot can change and the symlinks aren't
adjusted to account for this. This is a problem specific to the toolchain
bootstrap process. This patch adds up a function to recreate the
symlinks, hence ensuring they always point at the correct location.
(From OE-Core rev: ad0baa7d2f33a865011e0c6afe29f22aa1beea32)
(From OE-Core rev: bc8a384c49c60feab9d01f8277e92ac0603c8f93)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The method of resolving the patch should not effect the sstate-cache
signature.
(From OE-Core rev: b64cbe0b511de8d8943ce34cbb4901239d9f0cb0)
(From OE-Core rev: 896bd7d1442dcd3f080dc741a72f50ab95d7c38f)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Joshua Lock
Saul Wold
Nitin A Kamble
Matthew McClintock
Jessica Zhang
Lianhao Lu
Richard Purdie
Bruce Ashfield
Jean-François Dagenais
Wolfgang Denk
Khem Raj
Jiajun Xu
Paul Eggleton
Mei Lei
Zhai Edwin
Martin Jansa