Fixes [YOCTO #5772]
These five style sheets support creation of permalinks in the
HTML formatted output.
(From yocto-docs rev: 7467ad6518c0fc0eb829b9432dc113bd0cdb6807)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I have put the disk space requirements up in the general area
describing host system requirements. This specific note for
sato images is redundant and no longer needed.
(From yocto-docs rev: 3cb054c34c62771ae01be6f46817f3b489395867)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added the general requirement of 50 Gbytes of free disk space
to the host requirements. The information was somewhat buried
later on in the manual.
(From yocto-docs rev: aeb8a9988626404fcee60758fe7ae808b31af145)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I extended the section to mention where to find YP supported
BSP layers and a bit on how to get them via the link from the
Source Repositories web interface. Changes driven by community
input.
(From yocto-docs rev: 4c944bf33b7d642126c52efd313666270145ab50)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I was mixing the "50GB" and "50 Gbytes" strings. Throughout the
set I have tried to use "xx Gbytes" form. Fixed a "xxGb" form
that I found.
(From yocto-docs rev: 40dfc6ab1c5c928bedc301ce323af08aa0b7be59)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a bit more to the ending of the sentence to qualify
its meaning.
(From yocto-docs rev: 40b309a43d948d5800cfe908e72f6202c095a166)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #3729]
I have made an attempt at understanding this and creating
a section that describes the steps the user needs to take in
order to build out-of-tree modules on the target device when
running an SDK image. I created a new section called
"Building Out-of-Tree Modules on the Target". Basically,
the user needs to be on the target and change to a directory
and then create some scripts before attempting to build these
types of modules on the target.
(From yocto-docs rev: e0754ae6dbc5dc07fb6707fe4b71ecd95c8180dc)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Received and implemented some feedback from Paul Eggleton
on this section. These were unsolicited observations.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: 48ecc543d9f614b5258ab2573f0406aa3c778647)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5895]
I applied some review comments from Paul to tighten up this section.
(From yocto-docs rev: 9f17ad00e9e707fcd6f2419762b4281d64f4ed0f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new "Overrides" bullet item and fixed some minor issues
pointed out by Paul Eggleton.
(From yocto-docs rev: 44ff3d82985fa304c5641570fe72cf6a8ddabaa3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5521]
I created a brief note in the do_fetch subsection of the
"Taking a Closer Look" section to deal with how the build
system uses checksums during do_fetch to re-execute stuff
if a file:// listed in the SRC_URI has had its contents
modified.
(From yocto-docs rev: 7b857635f2663af7c1d5e8aa87239472a5b47919)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton sent me some feedback on this section. I implemented
his suggestions. Changes were minor. One included a cross-link
to the BitBake User Manual.
(From yocto-docs rev: e9b5f252a1368b8c231dd659428a18eacf9757af)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5895]
I created a new section in the dev-manual titles
"Creating a Custom Template Configuration Directory" that describes
how the build system uses the template local.conf and bblayers.conf
and conf-notes.txt files as a basis when creating the real
deals in the build directory's conf folder. The context of this
is so that the user can create their own directory with their own
template files for repeated configurations and to create a custom
conf-notes.txt file should they want the setup scripts to display
some custom list of targets.
I also modified the two script references in the ref-manual for
oe-init-build-env and oe-init-build-env-memres. I needed to
link to the "how-to" section and added a bit in there about how
the scripts go about forming the conf files in the build directory.
(From yocto-docs rev: c07fb7082fe08387bbc546b2a23620dedc7127b8)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Writing a New Recipe" section has a subsection named
"Packaging." We needed a cross-reference here to the QA checks
performed for packaging.
(From yocto-docs rev: 34952ee1b56a84e0ee0edd142c7c8c68b122a3e3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added "meta" as part of a path.
(From yocto-docs rev: 14cda136d1f8690f5ea15b218f2ab4fb49c0afa9)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #5482]
I applied some review edits as directed by Paul Eggleton. The
main feature was to merge the information on setting root
and extra user's passwords. Also, permanently removed the
reference to the wiki that showed the less optimal way of
setting a root password.
(From yocto-docs rev: fef0e17cd3835580abed175ef4a7baf22b9b7673)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added detailed requirements for the three LSB type images
in order for the build to create an LSB-compliant image.
Massaged the weston image a bit.
(From yocto-docs rev: 01fee2bebe76512ab5707212fc8d78df20d83126)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I implemented some review feedback from Paul Eggleton on these
variables:
TARGET_CFLAGS
BUILD_OPTIMIZATION
SDKMACHINE
IMAGE_ROOTFS_ALIGNMENT
IMAGE_DEVICE_TABLES
EXTRA_IMAGECMD
SSTATE_MIRROR_ALLOW_NETWORK
PACKAGE_ARCHS
SDK_PACKAGE_ARCHS
(From yocto-docs rev: 6fd804376367449494d5a5cfeb7e9bb2f4c04de1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing the v3.10.42 and 43 korg -stable updates.
(From OE-Core rev: f506d0660c9949485268a92724ac770b5457b0ca)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch with configuration changes to enable NAND
booting on the mpc8315e reference board.
We also update the BSP SRCREVs to fix a compilation issue with
date/time on Yaffs2 and gcc 4.9.
(From OE-Core rev: d7f3b457de1a541a4ba986c7e6dcdf136a3b831c)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to the latest korg -stable release.
(From OE-Core rev: 4121ab3a6ebfa9f8c33157a70533069ef1067fae)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the h/w reference BSPs to the latest 3.14 content.
(From meta-yocto rev: 3b0e8596eb3154a1d2dc1653afc9ea9c72db2fc6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a 32M NAND flash on this board, so it would be convenient
that a jffs2 image is created by default. Also change the default image
type from "tar.gz" to "tar.bz2" in order to be compatible with
the beaglebone black and edgerouter BSP.
(From meta-yocto rev: e2e0d9eee91a773c0e9a151f20d859525821a767)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The commit: http://ghostscript.com/pipermail/gs-cvs/2014-February/017271.html
newly added a 'compile time assert' on 9.14 that causes the build to fail if
the sizeof(GX_COLOR_INDEX_TYPE) is not equal to ARCH_SIZEOF_GX_COLOR_INDEX.
Disscuss on IRC:
http://ghostscript.com/irclogs/2014/02/06.html
The commit from OE-Core rev: 78a13ba170c1de6d7ef077854e3e34e18d17099f
...
ghostscript: add pregenerated objarch for mipsel/mips64/mips64el
...
has defined ARCH_SIZEOF_GX_COLOR_INDEX according to the type of archs,
and assigned 4 for mips/mipsel (8 for others).
The GX_COLOR_INDEX_TYPE was defined at do_configure time, which used
large color index (with 8) by default. We should manually choose the
opposite one (with 4) for mips/mipsel.
(From OE-Core rev: 0710ed28e868d4fc4ca027afb3c7acfc899f9409)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- The company address has changed in COPYING.
- Rebase fix_SHAREDDIR.patch to 0.52.17
- Rebase cross_ar.patch to 0.52.17
- Obsolete fix_python_fpic.patch, since the patch has been
merged by upstream;
- The upstream rename snackmodule to snack in 0.52.17, so tweak
libnewt-python_0.52.17.bb;
(From OE-Core rev: 46ec6e5601b88d4270d58586f25626349474d769)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #6254]
Adding support for the get_extra_files() method to the BeagleBoneTarget class.
(From meta-yocto rev: b719ff579fe2a5f5a0d19a9091eaa37e0f145384)
Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As an extra safety measure set PV in the same place as SRCREV.
(From OE-Core rev: cdbd772492812d2bd16ce9f3d5641910f9df240f)
Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
v2 changes:
* update format for commit log
* add Upstream-Status for patch
commit a12eb58959d0a10584a428f4a3103a49204c410f upstream
Dpkg::Source::Patch: Outright reject C-style filenames in patches
Because patch only started recognizing C-style filenames in diffs
in version 2.7, it's not safe to assume one behaviour or the other,
as the system might or might not have a recent enough version, or
a GNU patch program at all. There's also no reason we should be
supporting this kind of strange encoded filenames in patches, when
we have not done so up to now.
Let's just ban these types of diffs and be done with it.
Fixes: CVE-2014-0471, CVE-2014-3127
Closes: #746306
[drop the text for debian/changelog,because it's not suitable
for the veriosn]
(From OE-Core rev: 2c3838443eacd3a86ea8917ea53a20248e7bdf03)
Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com>
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
v2 changes:
* update format for commit log
* add Upstream-Status for patch
commit a82651188476841d190c58693f95827d61959b51 upstream
Dkpkg::Source::Patch: Correctly parse C-style diff filenames
We need to strip the surrounding quotes, and unescape any escape
sequence, so that we check the same files that the patch program will
be using, otherwise a malicious package could overpass those checks,
and perform directory traversal attacks on source package unpacking.
Fixes: CVE-2014-0471
Reported-by: Jakub Wilk <jwilk@debian.org>
[drop the text for debian/changelog,because it's not suitable
for the veriosn]
(From OE-Core rev: 81880b34a8261e824c5acafaa4cb321908e554a0)
Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com>
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
v2 changes:
* update format for commit log
* add Upstream-Status for patch
ppm2tiff does not check the return value of the TIFFScanlineSize
function, which allows remote attackers to cause a denial of service
(crash) and possibly execute arbitrary code via a crafted PPM image that
triggers an integer overflow, a zero-memory allocation, and a heap-based
buffer overflow.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-4564
(From OE-Core rev: 9f02922d44de483ef4d02ce95b55efe79a8b09a2)
Signed-off-by: Yue Tao <Yue.Tao@windriver.com>
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
v2 changes:
* update format for commit log
* add Upstream-Status for patch
Multiple directory traversal vulnerabilities in pam_timestamp.c in the
pam_timestamp module for Linux-PAM (aka pam) 1.1.8 allow local users to
create aribitrary files or possibly bypass authentication via a .. (dot
dot) in the (1) PAM_RUSER value to the get_ruser function or (2) PAM_TTY
value to the check_tty funtion, which is used by the
format_timestamp_name function.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-2583
(From OE-Core rev: 69255c84ebd99629da8174e1e73fd8c715e49b52)
Signed-off-by: Yue Tao <Yue.Tao@windriver.com>
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch allows for an optional new layout for ipk feed directories which I've
called a 'hierarchical feed' and is based on how Debian pools package files. It
is disabled by default and is enabled by setting IPK_HIERARCHICAL_FEED to "1".
In the traditional feed layout, package files are placed in <outdir>/<arch>/.
This can lead to several thousand files existing in a single directory which is
often a problem if developers want to upload a package feed to a shared web
hosting provider. For example, in my case, listing files via FTP only shows the
first 2000 files, breaking my scripts which attempt to upload only new and
changed files via FTP.
In the hierarchical feed, package files are written to
<outdir>/<arch>/<pkg_prefix>/<pkg_subdir>, where pkg_prefix is the first letter
of the package file name for non-lib packages or "lib" plus the 4th letter of
the package file name for lib packages (eg, 'l' for less, 'libc' for libc6).
pkg_subdir is the root of the package file name, discarding the version and
architecture parts and the common suffixes '-dbg', '-dev', '-doc', '-staticdev',
'-locale' and '-locale-*' which are listed in meta/conf/bitbake.conf.
This change relies on recent patches to opkg-utils which support hierarchical
package feeds.
(From meta-yocto rev: a0ab1527f975343f325fb2a5b0ecd14acdd65bc0)
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* TUI/GUI support was added in 2.6.35 based on libnewt
* since 3.10 slang replaced libnewt completly
* changing TUI_DEFINES is not necessary, because NO_NEWT is
still respected with newer kernels
* add comment about the gui history to the recipe
The patch was sponsored by sysmocom
(From OE-Core rev: bbeb133234fb90b01c9448afdecf03ebff7f7c47)
Signed-off-by: Henning Heinold <henning@itconsulting-heinold.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is introduced a bug, since The return of "file ld-linux-x86-64.so.*"
does not include "dynamically linked" in redhat 5.9/6.0(32 bit), and lead
to that ld-linux-x86-64.so.* is not in executable file list.
(From OE-Core rev: fc9603d7d7042efe8941172091cca8578bdde15b)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When toolchain directory is changed to execute mode, some non-executable
files or empty files are sorted. This will lead to the below error:
Extracting SDK...done
Setting it up...Traceback (most recent call last):
File "..._SDK/relocate_sdk.py", line 208, in <module>
arch = get_arch()
File "..._SDK/relocate_sdk.py", line 39, in get_arch
ei_mag0,ei_mag1_3,ei_class = struct.unpack("<B3sB11x", e_ident)
struct.error: unpack requires a string argument of length 16
To call get_arch and parse_elf_header, we should ensure the sorted file
is bigger than 64 byte.
(From OE-Core rev: 3b973f1c9c9ee3fbe64903036ad93eb9e928b185)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch is used for fixing build errors without dnssd/avahi, we
already have this patch, but isn't added to SRC_URI:
meta/recipes-extended/cups/cups/cups-str4402.patch
(From OE-Core rev: 7c0fc920d41cdd74cb7bba72faef08afba09ed12)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found this error on CentOS 5.10, other distros may also has this
problem, I think that we can disable the selinux for dbus-native:
bus/selinux.c:327: error: array type has incomplete element type
[YOCTO #6374]
(From OE-Core rev: 7a2d2d81d8694806060f7bccfbdba42dc356d477)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kexec-tools-klibc required kexec-tools.inc file. Put the patch of
kexec-tools into bb file in order to fixing QA warning about files path.
The patch only needed by kexec-tools.
(From OE-Core rev: d465fb6f8f1fff989a9e497f650328de6044b2f2)
Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>