The X18NCMSstubs.diff was modified to please the -Werror=return-type
compiler option. Otherwise, it will throw an error.
(From OE-Core rev: 708785266d1d671f5d2a8e8af81a77e34c70662f)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed two backported patches that already exist in the current
version and fixed a compilation issue when zlib is used.
(From OE-Core rev: 47800f9bff7a799489851156c341151ee9cf364f)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Enable the remapping for SDK generation, this is required to be able to
create an SDK that targets an alternative multilib. Note, this work does
not finish SDK/multilib support, but it is one more step toward making
it work properly.
(From OE-Core rev: d66d2bdf6214939e8b131f47db2f35d3c64e7dd2)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When constructing a multilib based image, it's possible to end up with
the same package listed in multiple steps of the install. During resolution
we use the --replacepkgs option to avoid errors, as the resulting install
solution will be as expected. (We do not enable the replacepkgs option
for the final install step, only the generation of the install solution.)
(From OE-Core rev: 68ea7d827710ae7c5cf402887d4c12319038e064)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
An anonymous python chunk configures some multilib settings for both
populate_sdk_rpm and rootfs_rpm. The two classes should contain identical
versions to ensure that the generated multilib configuration is the same
for the SDK and the rootfs.
(From OE-Core rev: 0f60722ef460fa826e4f02e7457004e64ca41d76)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
neon requires expat to be built first
lua similarly requires expat if enabled
selinux package name should be "libselinux" (from meta-selinux).
(From OE-Core rev: 6b3c9802b659ca1d3b7638ff80e6492cc0e16d6f)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #2133]
Increase ALTERNATIVE_PRIORITY of file functions to be higher than
the value in package initscript. Then when lsbinitscripts installed,
file functions provided by lsbinitscripts will be used.
(From OE-Core rev: 33f9abed7658bd5eae39e987b210651d202e1f4e)
Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lsb need a more abundant /etc/init.d/functions file to handle lsb test.
Use update-alternative to install file funtions in package initscripts,
when package lsbinitscripts installed the file functions of
lsbinitscripts will be used.
(From OE-Core rev: 478f821462665a9dc6f1755059cdbf642aebbf4d)
Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Manually checked packages for updates.
Changed the necessary fields with updated values.
Added missing recording where necessary.
Beautified some packages info.
Removed small typos in distro_alias.inc and recipe_color.inc.
All changes easy detectable in the diff.
(From meta-yocto rev: 387445c38b5eec0fad9dc8a819cedd5d89171c17)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated gzip and sudo to reflect recent recipe upgrades.
Updated manual check information for e2fsprogs, chrpath, opensp,
expat, nfs-utils, and libpng.
(From meta-yocto rev: eb52c5988e67adb1f6843da83f3ffe8bccda207b)
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I missed a "Yocto Project Files" term because the damn thing split
across two lines in the source file and my grep method did not find
it. Changed it to "source directory."
(From yocto-docs rev: 31a261c141d3e26f4a87b9725097005c96345e2e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Mentioned at the very end of the beagleboard build that the image
can now be run on the target hardware.
Also, specically noted the local.conf file as "conf/local.conf" in
the build directory.
Reported-by: Kevin Strasser <keven.strasser@intel.com>
(From yocto-docs rev: a4b41c7f5e8e8017401961097e0df4b13458ac24)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I did a scrub for the term "Yocto" and substituted appropriately.
This resulted in the term "Yocto Project build system" going away and
being replaced by "OpenEmbedded build system." The "Yocto Project
build directory" was replaced by "build directory." I also found a few
little things that were wrong like including the Debian distro in the
list of supported distros so I removed that. Finally, a spell check
produced a couple of fixes.
(From yocto-docs rev: 6957658982516aa4b0e4726c9344c46854aa11d3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I fixed several "Yocto Project build system" terms and some "Yocto
Project Build Directory" terms.
(From yocto-docs rev: 10c1d50380336ac684243525646ac9aa3c1812d4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found a stray reference to "Yocto Project Build Directory." I changed
to "build directory."
(From yocto-docs rev: e0c593ac162c61f7d42625482b95c253d0f8622a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the build/tmp/log directory description to mention that running
a build does not necessarily mean a log directory is created. Also,
ran a spell check and found a typo.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: c602919a1f188a4dff23f965bcc52b635f9a92ae)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
the section describing meta/recipes.txt had the "/" character at the
end of the filename, which is incorrect. I removed this.
Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: 28295d8c46d3a2cc6b53f0a7ccea35f1db77d1df)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made a few edits to better describe how the scripts and bin/bitbake
directories are placed into the PATH variable.
Reported-by: Paul Eggleton <paul.eggleton@linux.intel.com>
(From yocto-docs rev: 1e45731898935d40db6e6705f60bdea9633255ab)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The description of how BitBake is run and where its executable and
wrapper script reside has been updated to be more accurate.
Reported-by: Robert J. P. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 885b4c42a3ec3d228f1f5659a887627f4fe2d939)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bootimg.bbclass using STAGING_DIR_HOST/kernel instead of
STAGING_KERNEL_DIR, resulting in build failure of live images.
| install: cannot stat `/usr/local/dev/yocto/fishriver-test/build/tmp/sysroots/fishriver/kernel/bzImage': No such file or directory
Replace it with STAGING_KERNEL_DIR.
(From OE-Core rev: 8f16811a8d51982a8b3d70e6087aef4a41926840)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Tested-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on "Dependency Graphs" failed to mention the
package-depends.dot file among the files. Added this file to the
list.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 0ebf8ddf54e146454d6f300f790964decaeec6a9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This shouldn't be unconditional - a later patch made it so, but that's
not yet pulled in. In the meantime, to fix build failures remove the
unconditional install.
(From OE-Core rev: dcc43c34bfa9304233ecfd3f518a84ddfdc2fd90)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When use PACKAGE_CLASSES = "package_deb", and the length of tmpdir is
longer than 177, the error occurs during the image generation:
/very/long/path/totmp/sysroots/x86_64-linux/usr/bin/dpkg-scanpackages:
bad interpreter: No such file or directory
The interpreter is perl, and it does exist, this is because the first
line:
#!/very/long/path/to/perl
in the script can't be very long.
Create a wrapper for it would fix the problem.
[YOCTO #2640]
(From OE-Core rev: 7d3281be18567207de8ce2cabce03957bf2cbca8)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The setting is the same in all recipes, so move it to
the shared settings in u-boot.inc
Since FILESDIR is also being phased out, use the FILESPATH
setting as suggested by Richard Purdie.
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: 1b78904b115b50172cf82948d8a68dc3a98005ce)
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Variables which used multiple overrides and the append/prepend operators were
not functioning correctly. This change fixes that.
This fixes the testcase:
OVERRIDES = "linux:x86"
TESTVAR = "original"
TESTVAR_append_x86 = " x86"
TESTVAR_append_x86_linux = " x86+linux"
TESTVAR_append_linux_x86 = " linux+x86"
[YOCTO #2672]
(Bitbake rev: dc35a2e506e15fb7ddbf74c3b3280e9e83ab33bb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we don't do this, target and cross recipes end up with different sstate
checksums for shared work directory tasks which is bad in the case of gcc.
It leads to multiple fetch/unpack tasks against the shared directory
which ends up with build failures/races.
(From OE-Core rev: 793ce6cd9aa632e0f13789c8293770a86085d28d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We added the autoconf cache line a while back to ensure that configure doesn't
poke into some hardcoded host paths looking for things it shouldn't. Applying
it as part of do_configure wasn't getting it to the do_compile tasks
where much of the configure scripts are run by gcc. This changes it to a simple
export to ensure it reaches the places it needs to and truly gets rid of
the cross compile badness messages from the logs.
(From OE-Core rev: af58d5c3a5c5e632aa20b1d007d47dbbfb4ed6e6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ppp-watch requires it.
x86_64-poky-linux-gcc -m64 --sysroot=/intel/poky2/builds/fetch/tmp/sysroots/qemux86-64 -O2 -pipe -g -feliminate-unused-debug-types -Wall -D_GNU_SOURCE `pkg-config glib-2.0 --cflags` -c ppp-watch.c -o ppp-watch.o
Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
ppp-watch.c:78:18: fatal error: glib.h: No such file or directory
compilation terminated.
make[1]: *** [ppp-watch.o] Error 1
make[1]: Leaving directory `/intel/poky2/builds/fetch/tmp/work/x86_64-poky-linux/lsbinitscripts-9.03-r0/initscripts-9.03/src'
(From OE-Core rev: 488610f4a5b7591a989ff1a6137f276a85fd7a85)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
