- use migrate_localcount.bbclass to generate AUTOINC entries
which are exported to LOCALCOUNT_DUMPFILE
- import the generated AUTOINC entries
- one can migrate LOCALCOUNT to AUTOINC by executing:
bitbake-prserv-tool migrate_localcount
[YOCTO #3071]
(From OE-Core rev: ffab86f13cafb10d8d6273b6af8cd9a3c84eae20)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is needed to to boot efl images on qemuarm,qemumips and qemuppc
these options were already defined for qemux86 and qemux86-64 and
therefore the images were booting fine for these two machines
(From OE-Core rev: 60e73068cf542c2134106fe6cfc5971874bbc766)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Systemd has some uclibc specific patches which
needed to be forwarded ported to 196
(From OE-Core rev: e39f01ba4f6d9d9f1d24fd01745530cde9e92131)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the /etc/rpm-postinsts/ directory was empty, the following error
would occur at system startup.
ERROR: postinst /etc/rpm-postinsts/* failed
This patch fixes this issue.
[YOCTO #3767]
(From OE-Core rev: 202263aeca837dc7b6615a3dc34569c199163733)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recent change to blktrace removed the do_install method,
since this recipe does not use autotools it needs to specifiy
a do_install activity.
(From OE-Core rev: f8832d969746fb879e63d1b28e6beef5ab82a39d)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit c04f5435 "populate_sdk_base.bbclass: use SDK_ARCH instead
of SDKMACHINE" prevents not only the installation of 64 bit SDK
configurations on 32 bit hosts (which indeed cannot work), but also
the legitimate installation of a 32 bit SDK on a 64 bit host.
Fix this.
While there, also make sure we use the same patterns ("i[3-6]86" resp.
"x86[-_]64" to get unified strings for both INST_ARCH and SDK_ARCH.
(From OE-Core rev: 7ddd97b9b09fe7a327916ea88908a63375556ae6)
Signed-off-by: Wolfgang Denk <wd@denx.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
"RDEPENDS_${PN}_class-native" doesn't work for native recipe because no
-native package will be created. Then the dependencies listed here are
not built when bitbake createrepo-native.
Update and use DEPENDS_class-native instead.
(From OE-Core rev: 0b8dc781e4df0edffa10ac989f8745ac3f684de0)
Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The nslookup is not shipped for now, we should disable its man page if
the binary tool is not installed.
[YOCTO#3754]
(From OE-Core rev: 1a31918733a7f8479220c01fc99dd9099fdcaf9b)
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As this package RDEPENDS on systemd it wants to build systemd, but if systemd
isn't a DISTRO_FEATURE then that package is skipped so world builds fail. Solve
this by skipping this package too.
(From OE-Core rev: 192efd033c38205e114f62e9f62696a9a49b0970)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If configure of perl is reattempted it currently fails as it tries to edit
files outside ${S}. Chaging from ${WORKDIR} to ${S} avoids this issue
and allows rebuilds to work.
(From OE-Core rev: 1b66c30eb6085aedce118ce086efbd2e562d0d6c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Discussion has revealed that upstream has formally rejected patches to support
uclibc, so mark this in the headers.
(From OE-Core rev: caf6aa1c996a949ca85f4beaf40d2a19433d18c8)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GUPnP is now in meta-multimedia, so remove it from this SDK packagegroup.
(From OE-Core rev: 356a5ee5a74f9cee112eac2c595c13ef707eca82)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The GUPnP stack was stagnating in oe-core and untested. It's now moved to
meta-multimedia where it's also been upgraded.
(From OE-Core rev: 51e548a4e61709d9d87a424586529638873835b3)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This package isn't yet in oe-core, but GTK+ 3.6 depends on it so will be here at
some point.
(From OE-Core rev: 8c46ec2edc0197b32d32e0f27d5b60271338b600)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The reverts were by Koen and are literal revert commits, the uclibc patches were
mostly introduced by Khem.
(From OE-Core rev: 8925501890cbe630258d9c6fe348f1e3c821fc71)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that gtk-doc.bbclass supports overriding the documentation directory,
systemd can just inherit gtk-doc and all of the manual operations can be
removed.
(From OE-Core rev: 8b7816804dcfdc380fbebe6dc8c81f431a7fc450)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Not every package puts the gtk-doc infrastructure into ${S}, so allow this to be
overridden.
(From OE-Core rev: 40353c9ef83f986a0d49cc6eb654b3ace6ef4dc4)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop hash_enums.patch which is already applied upstream
(From OE-Core rev: c4d3f5596662d6aced46f270f566b510a36e4952)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
cross.patch was accepted upstream, so update this patch with the commit that was
merged.
(From OE-Core rev: 8e5ffa370c4259f925a0454fe7fd81c80ef2174b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes:
| operf_utils.cpp: In function 'bool _op_get_event_codes(std::vector*)':
| operf_utils.cpp:151:21: error: 'pfm_initialize' was not declared in this scope
| operf_utils.cpp:151:26: error: 'PFM_SUCCESS' was not declared in this scope
| operf_utils.cpp:166:45: error: 'PFM_PLM3' was not declared in this scope
| operf_utils.cpp:166:55: error: 'PFM_OS_NONE' was not declared in this scope
| operf_utils.cpp:166:72: error: 'pfm_get_os_event_encoding' was not declared in this scope
| operf_utils.cpp:167:14: error: 'PFM_SUCCESS' was not declared in this scope
[YOCTO #3717]
(From OE-Core rev: 121cb96964fe2f374d814bf39036119bd63b9589)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oprofile's "configure" was always looking at the configuration of the host
kernel, not the target kernel. This patch instructs oprofile to use the
target kernel to configure itself.
(From OE-Core rev: 5892db9a34c188b8a9bdaa86e19ba62a7f4793b5)
Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need to add a build time dependency on virtual/update-alternatives,
however we can't just do DEPENDS +=, or we end up with various problems. To
work around this, in the anonymous python space we ensure we only do the
addition when the package does not provide virtual/update-alternatives and
it is a target package.
Also the system wide PREFERRED_PROVIDER was incorrect. It references a
runtime package, and not the recipe it should have. This has been corrected.
[YOCTO #3691]
(From OE-Core rev: 56a59ef12936dcc6464cf1d43dda6957a5aa8c65)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Tested-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building the target SDK portion, we can safely ignore various
package rdepends. These dependencies are not required on a build
only environment like an SDK.
[YOCTO #3691]
(From OE-Core rev: 1edd44bed9e9829f7c2466928bc3f45be102b84b)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Tested-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
xattr system calls are old enough that we can switch
to just pulling the system call numbers from kernel
headers.
Upstream-Status: Submitted acl-devel@nongnu.org
(From OE-Core rev: 4dab91a4109a452f43483ef11ea9037ca8df1b33)
Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix a build failure caused by a bashism and improve quoting whilst in
the area.
(From OE-Core rev: 9eb78340c61acddb0c2012e25c76c18735febb4d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this some software fails to build complaining it can't find these
utilities.
(From OE-Core rev: db84eaf851b22b262d9dc48eb55bd5224a00fdd2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I found that if I had two packages architectures built (say core2 and i586),
that the shlibs data from i586 was being used in the core2 build. This
lead to odd dependency issues if the i586 build was out of date and core2
was being targetted.
When loading shlibs files, the last loaded wins so we need to iterate the
lists from least to strongest weighting, not the other way around. With this
patch applied, the contamination issue is resolved.
(From OE-Core rev: acd7b1c2ee9f3ff84c45a723dba5e0bc5f6a100c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Dropbear does not start when the host key is empty and it is possible
that a device is switched off before the host key is generated. This
is possible because the dropbearkey code doesn't create a temporary
file first. Detect truncated keys and then remove them which will lead
to the re-generation. This way the dropbear process will always start.
(From OE-Core rev: 16b57e352f5844f301cc6c7ea4f87bf750c11d67)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The gnu tar versions less than 1.24 pose a problem with the SDK
extraction. A typical SDK will have hard links. The SDK is created
with a newer version of tar but extracted with the host version of tar
which may be much older. The specific defect is that older version of
gnu tar do not properly handle the "--strip-components=" argument when
processing hard links and the paths do not get properly truncated and
hooked up with the corresponding real file payloads. This leads to
errors like the following during the SDK install:
tar: sysroots/qemux86-yocto-linux/usr/bin/getconf: Cannot hard link to `./opt/yocto/SDK-qemux86/sysroots/qemux86-yocto-linux/usr/bin/POSIX_V6_ILP32_OFFBIG': No such file or directory
The simple way to work around the problem is to just not save the path
information that is going to get chopped off anyway. This has the
added benefit that it saves a small amount of space in the tar archive
as well.
(From OE-Core rev: 0f4112016bac07f0294f2a4d0fde4659c0fed2d2)
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
b27b438221e16ac3df6ac66d761b77e3bd43db67 introduced a regression when
PKGV is modified by the recipe. E.g. when having something like
| PV = "1.7.33+gitr${SRCPV}"
| PKGV = "1.7.33+gitr${GITPKGV}"
| RDEPENDS_${PN}-subpkg += "${PN} (= ${EXTENDPKGV})"
| inherit gitpkgv
The resulting core package has
| Version: 1.7.33+git234+cd01e8c-r11
and because the subpackage has
| Depends: vdr (= 1.7.33+git0+cd01e8c18d494150730214f033f84e5282ce7639-r11)
image build fails with
| * satisfy_dependencies_for: Cannot satisfy the following dependencies ...
| * vdr (= 1.7.33+git0+cd01e8c18d494150730214f033f84e5282ce7639-r11)
Patch avoids the 'PKGV = "cleanup(${PV})"' operation and replaces
AUTOINC directly within PKGV. This might introduce a regression too
when 'AUTOINC' is added to PKGV intentionally but impact is small and
can be fixed trivially by using another string.
(From OE-Core rev: 6e46664085fa49bc204fc944ca23ed6383e2ec51)
Signed-off-by: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
Cc: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch to import the following commits that cleanup and
reorganize the features that make up the graphics features of the Intel
BSPs
c0b3904 meta: add config fragment for gma600 graphics driver
f41638f meta: add config fragment for gma500 graphics driver
ff8ad3e meta: sys940x: drop vesa fragment from bsp config
fcb82ac meta: sys940x: remove emgd config from bsp config
c1677bb meta: fri2: drop vesa fragment from bsp config
7324440 meta: fri2: remove emgd config from bsp config
dd435c6 meta: emenlow: drop vesa fragment from bsp config
243b515 meta: emenlow: remove emgd config from bsp config
3e1be82 meta: crownbay: drop vesa fragment from bsp config
fc5ed4e meta: crownbay: remove emgd config from bsp config
d46236b meta: drm-emgd.cfg: add configs for dependent routines
db4bc5e meta: relocate git-merge of emgd branch
(From OE-Core rev: 8d0074ef2b61bf022ed1bb3b5f1afe526d8c921b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the yocto 3.4 kernel tree to the 3.4.25 and 3.4.26 -stable updates
as well as refreshing the preempt-rt branches to 3.4.25-rt37.
(From OE-Core rev: da536703bdcf31c8c2ef17f5a49d06280fe77600)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kernel compiler is not special and we currently have it so
we want to pass -march and -mtune options as CFLAGS to kernel
build so that compiler picks the right subarch flags when
compiling assembly files in particular. Otherwise defaults
are chosen which may not be right in many case e.g. when
compiling kernel for collie machine we should use arch=armv4
but it uses toolchain/as defaults which is armv5te
in some case e.g. thumb1 we know that kernel can not be compiled
in thumb1 mode so we can provide that information e.g. -marm
option through KERNEL_HOST_CC_ARCH variable as we do now
(From OE-Core rev: c49f967384ccbfe131bbb33ee518014f3fc4b38f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The default fstab has entries which are not necessary
in systemd based systems so add a simpler default in
this case.
(From OE-Core rev: 77bbb839ba25b974a538b90d346b454ccd5deefd)
Signed-off-by: Martin Donnelly <martin.donnelly@ge.com>
Signed-off-by: Radu Moisan <radu.moisan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
update-rc.d is not necessary when systemd is enabled,
systemctl is the replacement
(From OE-Core rev: eaa82c842d3197e0251a887ba16028c22f9d8d94)
Signed-off-by: Radu Moisan <radu.moisan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd-compat-units is needed to run postinsts for example.
(From OE-Core rev: cf783377767c70db544da57593616cfc952dbfb9)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Constantin Musca
Khem Raj
Chen Qi
Saul Wold
Wolfgang Denk
Kang Kai
wenzong.fan@windriver.com
Ross Burton
Richard Purdie
Cristian Iorga
Matthew McClintock
Christopher Larson
Bogdan Marinescu
Mark Hatle
Riku Voipio
Holger Hans Peter Freyther
Jason Wessel
Enrico Scholz
Bruce Ashfield
Koen Kooi
Martin Donnelly
Radu Moisan