Some formatting to fix up Kevin's patch. One thing important was
that the <ulink> line cannot span multiple lines. I fixed this.
When they span multiple lines, the sed script used to convert the
links for the mega-manual breaks.
(From yocto-docs rev: e31012878c709eccae94734f7933559cb1187c47)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patch from Kevin that adds a new class. Note that the
patch removed the existing src_distribute_local.bbclass
class.
(From yocto-docs rev: 4ce602093bc9ddfcbcd9392bcc8fd6187885bdf1)
Signed-off-by: Kevin Strasser <kevin.strasser@linux.intel.com>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The list was somewhat out of date. Robert's patch fixes it.
(From yocto-docs rev: 8c3c07872a7202315a7501dcd56fb7347668feae)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a note in the bsp-guide to point back to the main
new section, which is in the dev-manual.
Made some small edits to the main section in the dev-manual.
(From yocto-docs rev: 4105c8edbdc531b2a941d7f7282325fae763f059)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied some minor fixes to this area as directed by
Paul Eggleton. This represents a clean second draft that
can be reviewed. ]
(From yocto-docs rev: d3380d698d36e83aab16ac74e713ab03baef60b0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These are review comments from both Paul and Bjorn.
(From yocto-docs rev: 773300f78b20bd601cbad750cfe32263fbe9d127)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a cross-reference to the "How to Submit a Change"
section. I added a bit of text to note that the ready can
go there to find out who maintains code.
(From yocto-docs rev: 30a2602c4c0945f1c9bd2a7fa71c1b98e790b2eb)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "Tracking Bugs" section mentions how to enter a bug using
Bugzilla. I added a new step just before the step that says
to submit the bug that tells the user to be sure to copy the
correct people. The link goes to the section that describes
how to figure out who is responsible for code.
(From yocto-docs rev: 64e58402490267a339c9bade969850da50f39cf1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provided three ways to dig out the information on who might
be contaced about a change or patch to an area of code:
1. See the "maintenance.inc" file.
2. Examine BSP README files or the MAINTAINERS file (for BSP)
3. Use the 'git shortlog -- <filename> command to see who
has committed the bulk of the changes for a particular file.
(From yocto-docs rev: 0757a2edddb55bcce2ea1507501220c3097f0a22)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
${datadir} was empty when building ${B} != ${S}, this patch addresses that
problem and means the -lenses package is no longer empty.
(From OE-Core rev: ee3b0d8fbe42a3c813039850886b5bf97544eb15)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backport patches from linux-pam git repo to fix test case
tst-pam_pwhistory1 failure.
[YOCTO #4107]
(From OE-Core rev: 65e4a9f050ae588ec794808315a206d94ca7a861)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When pam is enabled an extra plugin is build and it references an incorrect directory
when separate build directories are used. This patch corrects the issue.
(From OE-Core rev: a6e91db198ae5b77986de25331631d894c7b97d1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* with external toolchain I have different HOST_PREFIX and HOST_SYS
AC_PATH_TOOL is using HOST_SYS as prefix and fails to find objcopy
then it tries objcopy without prefix which is found on host, but
that objcopy does not work for arm libs
* with internal toolchain gperf is not prefixed with HOST_PREFIX, but
fallback to "gperf" only finds the one in native sysroot first
* based on http://lists.linuxtogo.org/pipermail/openembedded-core/2013-April/037985.html
(From OE-Core rev: 6ae99136f1c1c59f4e55331c43cf0c0bac5abcdd)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit a2546fae [ftrace: Add -mfentry to Makefile on function tracer]
adds support for using -mfentry when possible, whenever the ftrace
CONFIG_FUNCTION_TRACER option is enabled.
This unfortunately causes bogus dwarf debuginfo to be generated:
gcc Bug 54793 - the location of a formal_parameter is not started from a
function entry with -mfentry
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54793
This can be fixed by applying the gcc patch above, which will be
present in gcc-4.8, but in the meantime, the problem is currently
being worked around in different ways by various tools. One of those
tools that we support in Yocto, Systemtap, requires the DW_AT_producer
string contain -mfentry, which means that it's assuming
record-gcc-switches is also used:
SystemTap Bug 15123 - workaround for bad debuginfo for -mfentry
http://sourceware.org/bugzilla/show_bug.cgi?id=15123
The lack of -grecord-gcc-switches and therefore a missing -mfentry
string in Yocto leads to the following Yocto bug:
Bug 4099 - Crosstap script check fails
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4099
Which is what this patch intends to fix.
It only affects architectures that HAVE_FENTRY when
CONFIG_FUNCTION_TRACER is turned on and in any case is just adding to
the debuginfo, so there doesn't seem to be much risk to adding it.
(From OE-Core rev: c04f611aa4bf77867fe78a005d09434226feb62c)
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The meta-oe bbappend only increments PRINC, if we bump INC_PR here we
can remove that.
(From OE-Core rev: 9e74a1c9cb753a426b55544cc41860edb98e8d33)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The meta-oe bbappend only increments PRINC, if we bump PR here we can
remove that.
(From OE-Core rev: 7aadfe2f293da665236aede5cb03f801d420d050)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The meta-oe bbappend only increments PRINC, if we bump INC_PR here we
can remove that.
(From OE-Core rev: 976a06f41558d2246173414658d9f7b8eee193d6)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After installing Avahi we need DBus to reload it's configuration. In a
pure-systemd image there isn't a DBus init script to reload, so cut out the
middleman and just sent SIGHUP to all running dbus-daemon processes instead.
(From OE-Core rev: d6fb028de172bb649b905b605f6ddc8402af859a)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recipe in meta-gnome has PR = "r1" so make it the same here and
avoid PR going backwards for existing users of meta-gnome when the
recipe there is removed.
(From OE-Core rev: 200685bde7ea222891e1dde27f086caea9216e48)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After installing Avahi we need DBus to reload it's configuration. In a
pure-systemd image there isn't a DBus init script to reload, so cut out the
middleman and just sent SIGHUP to all running dbus-daemon processes instead.
(From OE-Core rev: b3e468294a0723b3ceafe2022bf9d735eee64678)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The distcc support is clearly unused and broken, might as well drop the
remaining code fragements.
(From OE-Core rev: 1a70a3225947aa45f3e1f377d50a5865aac64d2b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libpng 1.6 emits more warnings than before, and is also stricter with function
ordering. Fix the function ordering when reading PNGs, and stop treating all
warnings as errors.
(From OE-Core rev: 55d00b750f5c45e583abef406c96416cd6a8caa7)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel size has grown to a point where the original load address might not work
due to memory region overlap. This updates the instructions to use larger memory
addresses which avoids the problem.
[YOCTO #2430]
(From meta-yocto rev: 6b7cd4aa50f91c4ebb8a61c9d7fea616be63f470)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The install boot option was giving the following error when one tried to
install the live image on a permanent storage of a BSP.
cat: write error Invalid argument
Installation image failed
sh: can't access tty: job control turned off
Further digging into the issue, found out that the install script was trying
to do this:
cat /proc/mounts > /etc/mtab
And in the base-files recipe the /etc/mtab is made soft link to /proc/mounts.
So the cat command was failing to write on /etc/mtab. As the contents of
the /proc/mounts is already reflected in the /etc/mtab file due to the
symlink-ing, there is no need for this step to recreate /etc/mtab in the
install script. So just removing this unnecessary step, which solves the
install issue of the live images.
Fixes this bug:
[YOCTO #4229]
(From OE-Core rev: f8663eac872882e94d956b1b604304e92b865766)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Patches backported from mesa Git and from mesa-dev mailing list.
(From OE-Core rev: f704bb42062f2ac15edaad36497a8d2815b8b8b2)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SCRCREV to pick up the following fix
updateme: use absolute path for generated BSP descriptions
When a custom BSP is used, a top level BSP is generated by the tools and fed
to the build system just as a user defined BSP would be located and
passed. The location of the generated file is placed in the top_tgt file,
which is used by subsequent stages. A relative path was being placed into
top_tgt, which binds the build to a particular directory structure and
working directory.
The location of parts of the build have changed, and this relative path is
no longer accurate. Changing it to an absolute path solve the build issues
related to custom BSPs.
(From OE-Core rev: 2d7b2478a3d48a5686afde790c378ee2f69b8e59)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* CentOS 6.4 is the latest stable release; users of previous versions
get automatically upgraded as part of normal distro updates.
* Add Poky 1.4 for the build appliance
(From meta-yocto rev: ec56279c5158fa0902d7bdc8839bb490cba98a48)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New coreutils (8.15 onwards) build /usr/bin/realpath, which busybox also builds.
Add it to the alternatives handling to avoid file conflicts.
(From OE-Core rev: 826c18eb1c69f5e3689b5b0ef188f74ae930a050)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Other recipe versions in other layers
may be using connman.inc, so by resetting
INC_PR they go backwards in version.
Set the INC_PR correctly.
(From OE-Core rev: 2d56006cd88233c7f1f15a44f72a04bd0e441b25)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>