The autoconf macros detect the presence of -ldbm or -lndbm on the host
system and add the library to link against, for now good reason I can
explain.
This patch makes the build behave determinstically whether they're
present or not. Other than the extra linkage, there doesn't appear to be
any other change in behaviour from these options and they look like
dead code.
The extra linkage can cause problems where sstate is used on a machine
where the extra librbary isn't present causing build failures.
(From OE-Core rev: f609bf5525450bfdb8e0864d44c41cce7f9319c9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With 1.3 coming soon, it's time to bump DISTRO_NAME, DISTRO_VERSION
SDK_VERSION and SANITY_TESTED_DISTROS
Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
This line causes pkgconfig-dev to replace pkgconfig so the package with all the files
in is replaced by one with no files. This makes no sense and hence we should just
remove this broken line.
At this point in the release, this is the safest way to fix this even if an empty -dev
package is left available.
[YOCTO #2878]
(From OE-Core rev: 5bed2bb831b379a8fbf2f725435af4b7c934359e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The eglibc core build still has a number of issues with /bin/dash.
Recently found is both sysdeps/unix/make-syscalls.sh and it's output,
which make calls via SHELL do not play well with /bin/dash. By force
make to use /bin/bash via SHELL setting it works correctly.
Currenly known issues are: make-syscalls.sh line with a bad substitution,
which can be corrected by:
vdso_symver="$(printf '%s\n' ${vdso_symver} | sed 's/\./_/')"
Following that there is an issue with emiting a '\n' through a second
echo and then to the compiler. There maybe more issues beyond that.
[YOCTO #3080]
(From OE-Core rev: 9d002f7cdc5309c4d850a76e4fd73ff04c980a07)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the temporary text in the new "Patching the Kernel" section
that was copied from the old appendix A. Fixed the PRINC variable
in the creating a new layer example.
(From yocto-docs rev: 3eba77a81d3460866638a2f2d6b7c27d9dd1a2be)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed the "kernel-example-repos-generic.png" file as it describes
the bare clone method for kernel modification. We are removing
that from this manual.
(From yocto-docs rev: c25c4f662c2f8a83fd9b09583646be9dbe01424c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Moved the simpler version of the kernel workflow diagram to the
figures folder.
(From yocto-docs rev: c856fe320a0e70701f14312439fec6ccb707f9bd)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel workflow section was re-written to reflect that the
kernel appendix has been removed. Also, changes to the flow in
general no longer make reference to the bare clone and the copy
of the bare clone as a method used to modify the kernel.
Many links were modified in other manuals as well.
(From yocto-docs rev: 38adbcb00d4305029cfa94e5ef047da41823f021)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The figure that shows the bare clone and the copy of the bare
clone are no longer needed. The description for the kernel
workflow has been reduced to discussing only modification of
the temporary source files. We are no longer talking about
creating a bare clone and copying it as a way to modify the
kernel in this manual. That topic will be described elsewhere.
(From yocto-docs rev: f6a25e5e3763ea7a1f8a81ce377e3b520143b852)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#3245]
New glossary terms for SPECIAL_PKGSUFFIX, and MLPREFIX.
Also improved the definition of the BPN variable.
(From yocto-docs rev: d9eb38122967a5729f3a6aff1dae00427a22f579)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Common Tasks" chapter is better suited as the last chapter in
this manual. So I moved the development workflows up a chapter.
(From yocto-docs rev: 19f0a6411c065388b5bd0083338b164b43baff0e)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel example appendix is now gone.
(From yocto-docs rev: d744e76034ff2711a8c40b9bb1982971d28a04b1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel example appendix is being removed. This broke a lot
of links. For now I have moved the information into a new section
called "Patching the Kernel". I have preserved the information
by adding the old appendix file as kerne-appendix-orig.xml.
(From yocto-docs rev: 994235a69362dfb0114ef9001ea7f2f2e2fdc5c3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Eliminated the section A.2, which had an example of how to use
menuconfig in the kerenl example appendix. The information is
now merged into the similar section in Chapter 4 "Common
Tasks." It was decided that the Appendix A examples in the
manual were too detailed for a general development guide.
(From yocto-docs rev: f88ec421b257657f02cc0f132ec2580c17f07cef)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perl.c uses an ARCHLIB_EXP define to generate compile-time code that
adds the archlibexp path to @INC during run-time initialization of a
new perl interpreter.
Because we've changed this value in a temporary way to make it
possible to use ExtUtils::Embed in the target build (the temporary
value in config.sh gets re-stripped out during packaging), the
ARCHLIB_EXP value that gets generated still uses the temporary version
instead of the original expected version (i.e. becauses it's in the
generated config.h, it doesn't get stripped out during packaging like
the others in config.sh).
This creates an unmodified version called archlib_exp that gets used
by a modified config_h.SH to get the correct value into config.h
This patch uses an unmodified version of archlibexp called
archlib_exp, introduced to config.sh, which is used to generate the
correct value of ARCHLIB_EXP into config.h
Fixes [YOCTO #3099].
(From OE-Core rev: cbcfdeb1d55e2e76f199750bda401bad126ae234)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This change also applies to task-core-standalone-sdk-target-dbg and resolves
build failures caused by the missing packages.
(Bitbake rev: 4cd0200e96fb282980a945b80af641a6e022e0b4)
Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The name of the license for bzip2 is wrong causing warnings
to be thrown.
(From OE-Core rev: 566c6101cc7a8d90973eb22478ffc77eac23f81c)
Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a problem in commit ad23395cd1 since
gettext-nativesdk was translated to gettext instead of nativesdk-gettext.
This fixes to use the correct dependency.
(From OE-Core rev: a6e325342cb489e05927d6cb2bb0a24fa6c20ef8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
korg commit 42dcd1f4e [perf tools: Fix parallel build] fixes parallel
build issues that are being seen in the autobuilder.
We also have a fix from Tom:
[
perf annotate: replace 'expand' with equivalent sed expression
We don't have 'expand' in our userspace so we need to accomplish the
same thing using 'sed', which we do have.
]
So we apply it to all BSP branches and kernel types.
(From meta-yocto rev: 54fc1fd107f907a208b41a66c0a7b9b40cb428c7)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
korg commit 42dcd1f4e [perf tools: Fix parallel build] fixes parallel
build issues that are being seen in the autobuilder.
We also have a fix from Tom:
[
perf annotate: replace 'expand' with equivalent sed expression
We don't have 'expand' in our userspace so we need to accomplish the
same thing using 'sed', which we do have.
]
So we apply it to all BSP branches and kernel types.
(From OE-Core rev: f06e7d38db35c56c71a42264361ec45fb3777a14)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.4 linux-yocto-tiny kernel successfully boots to a prompt for
qemux86.
(From meta-yocto rev: e24ea77ca40e096f294649e3f85c8ec47efcbb87)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The hardware reference BSPs are missing the update to 3.4.11
that the qemu* machines received several weeks ago.
Bumping to 3.4.11 specifically addresses the segfaults being
seen with rpm on the beagleboard.
[YOCTO #3186]
(From meta-yocto rev: f2d93f4e79d0c8c0035774cfa7dc4beb197899f4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If qemu-mips was disabled as done in some distros, this wrapper would fail.
Therefore check if the file exists before wrapping it.
(From OE-Core rev: 9ec1c06915b10d142bf5646396c4e91bb61a40a5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This recipe builds the "tiny" kernel type defined by the linux-yocto
meta-data. Support is defined for the qemux86 machine via
common-pc-tiny.scc in the linux-yocto meta branch. The resulting
kernel is 1.8 MB and boots to a serial console with with qemux86 and
core-image-minimal using the following command:
qemu -kernel tmp/deploy/images/bzImage-qemux86.bin -initrd tmp/deploy/images/core-image-minimal-qemux86.cpio.gz -append "root=/dev/ram0 console=ttyS0" -nographic
(From OE-Core rev: cf25f211ec420e1e8dd48c8e62f60deefe2c6d53)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV to pickup the following change:
Ensure the qemux86 machine is defined in common-pc-tiny as it is
for -standard and -rt.
(From OE-Core rev: 1076910ac3cd55a3f87b5ca7a1db1e38c623480a)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kernel configuration fragments to fix the following
issues:
- remove options that are no longer in the 3.4 kernel
- disable unused, but large kernel modules
- fix kconfig audit warnings for x86 BSPs
- make uprobes reusable by multiple fragments
The following meta branch commits are represented by this update:
3da1172 uprobes: split into enable and patch fragments
17ec51a meta: cleanup invalid/obselete 3.4 CONFIG options
b5cee42 meta: disable OCFS2 by default
efe937e meta: drm: tag DRM options as 'hardware'
10b5155 meta: emenlow: clean emenlow configuration warnings
a907b82 meta: add CONFIG_SHMEM to standard kernel config
(From OE-Core rev: a01bb3ec72c375c0f06006769969f63fed3ef566)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
this statement in the linux-yocto-3.4.bbappend file needs to
have the comment removed so the source can be found.
(From yocto-docs rev: 821162221818f5ce53bb903aeef57c85314f5083)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the Kernel example appendix I changed some remaining 3.2
kernel strings to 3.4. Also I added the OE_INIT_FILE variable
from poky.ent for use instead of the "oe-init-build-env" string.
(From yocto-docs rev: 1d9d8d72d197bdd81756eed7fe1529f341de6089)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Each time the kernel revision is bumped (e.g. 3.2 to 3.4)
Some of the figures would be out of date. The reason is they
had pathnames that included the release of the kernel.
For previous YP releases I was adding logic to the Makefile
to be sure to catch the right files dependent on the branch
from which the documents were being built. This scheme is
not scalable so I decided to make the figures generic by
adding a note within the figures explaining the place-holder
"<x.x>" as part of a pathname. Thus, three new figures were
added to the folders directories of the dev-manual and the
mega-manual. Correspondingly, the 'denzil' version of the
figures were deleted.
I modified the Makefile so that if the BRANCH is not edison
or denzil then the generic figure set is used. I have to retain
the logic for both edison and denzil to cover the case where
a user clones or sets up an edison or denzil repo and then
builds out the manuals. Basically, it had to be backwards
compatible for releases prior to danny.
(From yocto-docs rev: 8283eed4b0b9ec164b87db99c35231f8731ac443)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Minor edits to the part of the example that sets up for the
first core-image-minimal build. Put in the variable to use
for the build environment setup script, updated some changed
output from some of the commands, etc.
(From yocto-docs rev: 0b4b2ddf9a78a9d6d218ed9a6f0acd3e876d9581)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Danny, the "kernel-example-repo-<release>.png" file changed to
"kernel-example-repo-danny.png". To correctly make the dev-manual
and the mega-manual some things needed to change:
1. New figure created and added to both the dev-manual and the
mega-manuals figures directory.
2. The "kernel-example-repo-denzil.png" files from the dev-manual
and mega-manual figures directory was removed.
3. The Makefile was adjusted so a new BRANCH=danny area now exists
to set TARFILES for both dev-manual and mega-manual.
(From yocto-docs rev: 8b2ff6b657a1486559799e219baaec9fde2e5c6c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a note at the beginning of this appendix that references
the yocto-kernel script as a way to quickly manage kernel patches
and configuration.
(From yocto-docs rev: 35cd7f6a9722120e47ae8b422dd86593497ebf1c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO_#3180]
Final changes to the packages section. They were re-organized and
the set is complete and thus fixes this bug.
(From yocto-docs rev: 533b45c9d41330497bbd0da58b812a4738ba64a8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows for use of bitbake in offline mode, but override it in
command line.
(From OE-Core rev: bcefd015fb163d9c382ae05a86569dbcfd3d736a)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When DISTRO_FEATURES does not include X11 ensure that both x11
and gtk are diabled correctly. ConsoleKit also has x11, so ensure
that any RDEPENDS is also excluded.
The flags for x11 changed at somepoint to use enable/disable, but
this recipe was not updated.
(From OE-Core rev: 0730d3449aa28600488e73de883240ba2bd60aec)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Also ensure that we always cleanup the temporary install manifest files,
some of them will cause problems if they exist in multiple install
attempts.
Finally verify that the lists remain uniquely sorted otherwise the
complementary install may install the same files numerous times,
triggering a failure.
(From OE-Core rev: 4f2a290cbcc6c21afbb2a6e6148efdef4d135b41)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This avoids errors where gcc/binutils get installed to the native sysroot
in the same location for multiple package architectures. Ultimately making
these native recipes with ${PACKAGE_ARCH} appended to PN will resolve this
but hide the warnings until this gets sorted out.
Also hide the python and docbook catalog warnings since they're known about,
nothing to worry about and we'll aim to clean them up properly in the 1.4 cycle.
(From OE-Core rev: 5bae58a5b59c04d8947f4842f19837a914c29b52)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this, path components like // could break comparisions with the whitelist leading
to warnings being displayed to the user unintentionally.
(From OE-Core rev: d3c46ca56fab2f07bf16b61514f30765543a8747)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't want the cairo dependency. Unfortunately simply checking whether its present
isn't good enough. If its not in DEPENDS, it can disappear half way through building.
We therefore need to explictly disable it.
(From OE-Core rev: 51df11c5747f69b4112121df78fc1e10644d390a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Saul Wold
Richard Purdie
Elizabeth Flanagan
Scott Rifenbark
Tom Zanussi
Martin Jansa
Andrei Dinu
Cristiana Voicu
Constantin Musca
Bruce Ashfield
Darren Hart
Otavio Salvador
Mark Hatle