* ppc-hack patch is dropped.
* Other patches which were direct backports
or has been merged upstream in 0.14.0 are
also dropped
(From OE-Core rev: 97fbdfdbfb15de325fd148bcecc9187d0f778db5)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is needed for the native recipes in meta-efl
(From OE-Core rev: 073f162529e5b84f12d348ae49edccc377ec5f7e)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 2.6.37.5 -stable update is available, so it now becomes
the new base for linux-yocto.
All qemu targets have been built and booted.
Changelog is available via:
git log --pretty=oneline --abbrev-commit v2.6.37.3..v2.6.37.5
(From OE-Core rev: bbbc60f24969f9ec596ab344fbb557d5e21c2abf)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Image generation code in .conf files is hard to read as it needs to be
single line. By moving this to a separate class, multiline functions
can be used instead improving readability. It also declutters
bitbake.conf.
There is no real functional change with this patch but it highlights
the need for improvements in places such as the IMAGE_EXTRA_OPTION
ext* specific variable which makes no sense.
(From OE-Core rev: a5c403f0fc71f38c0669691da7f637303ea09a27)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The base-files version is horribly outdated too.
[YOCTO #924]
(From OE-Core rev: f61df1f1e4a191ed3dd3d71aa78a479c615b14d1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Image type specific size overrides for IMAGE_ROOTFS were being ignored.
Moving the size calculation to after the overide expansion point addresses
this problem.
[YOCTO #928]
(From OE-Core rev: 2f676dadebebc461c1e01e0b6da3cb2258829048)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The quoting in get_imagecmds() is hard to read. We can simplify the constuction
a little to make this easier to parse and reduce complexity slightly.
(From OE-Core rev: da5d038f955bf47155a0f217dba2f96e263bcad8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* otherwise strange error like this:
ERROR: Logfile of failure stored in: /OE/shr-core/tmp/work/armv7a-oe-linux-gnueabi/libtool-cross-2.4-r1/temp/log.do_package_write_ipk.25551
Log data follows:
| ERROR: Package already staged (/OE/shr-core/tmp/sstate-control/manifest-nokia900-libtool-cross.deploy-ipk)?!
| ERROR: Function 'sstate_task_postfunc' failed
NOTE: package libtool-cross-2.4-r1: task do_package_write_ipk: Failed
ERROR: Task 11 (/OE/shr-core/openembedded-core/meta/recipes-devtools/libtool/libtool-cross_2.4.bb, do_package_write_ipk) failed with exit code '1'
is shown in this case with package_ipk twice in INHERIT
* Thanks to Richard for fix
(From OE-Core rev: f2fe5e840b8aa0558b5462ef2c7517b2f14ec2ea)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When 'kernel-misc' is empty do_rootfs will fail when including 'kernel-modules'
The proper fix would be to have a whitelist for the 'kernel-modules' meta-pkg
(From OE-Core rev: bb72bd56101698b7fe166dd02fdca07d06a6eb8b)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Tested-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GCC 4.5 ends up in an ICE when compiling libstdc++ pre compiled header
so we eliminate -feliminate-dwarf2-dups for gcc-runtime
(From OE-Core rev: e0eeb10144db74c0671acd684059e8a6f82a572f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Since bitbake.conf has got rid of -fomit-frame-pointer this
is no longer required
(From OE-Core rev: ba89ba8e02185c7adb92240f119a57e7b21adfa7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-fexpensive-optimizations is enabled by default at -O2
-fomit-frame-pointer is enabled at -O2 selectively by gcc depending upon
architecture if debug info is not hurt
-frename-registers - This might have some performance advantage on top
of O2 on architectures which have more registers and registers are left
after scheduling but it affects debuggability quite a bit so as a i
tradeoff we do not use it.
-feliminate-dwarf2-dups - We use this option to reduce the size of debug
information by removing duplicates this is only valid for dwarf2+ and we
use dwarf2 by default
-pipe uses buffers instead of temporary files internally it can speed
up compilation it has has issues with other assemblers but not
with GNU assembler and we use gas.
Separate out debug information related flags into a separate variable
DEBUG_FLAGS so distros can use/notuse them as they like
(From OE-Core rev: 9cb7113790d716a4c5cf7d511535ba87fdecd1ac)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Coreutils can optionally build with libgmp support and for our uses
it's fine to just not build it rather than add the dependency.
(From OE-Core rev: e58ca6504ccfd4fd7efbf288eaadae6720c84c79)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In mirrors.bbclass we point into /pub but we don't in bitbake.conf.
All uses of KERNELORG_MIRROR look into /pub anyhow, so lets make
use of that.
(From OE-Core rev: 67a0c8f48b5ef2ae5fc712c9204e4e99818c8134)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ubuntu has moved eglibc to /usr/lib/${arch}-linux-gnu and
/lib/${arch}-linux-gnu so we need that to be added to glibpth in
Configure.
Currently we set LD=ld in environment for recipes inheriting native
class. This overrides the LD settings in the Makefiles of perl and
it tries to link by calling ld which does not work since its using
-l<x> on commandline and ubuntu linker seems not to look into
the new location for these libraries. Its better to use gcc for linking
here anyway
[With tweak from Tom Rini to use CCLD, not LD]
(From OE-Core rev: 8ba700a4c593fd52bd01b6272b4c8285a71964f7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without using rw the ext3 images boot the kernel but do not spawn the
console at the end
(From OE-Core rev: 44359c953a6205a5028483e22b81e9d1691bfd44)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a nasty bug in qemu 0.14.0 where it over writes device memory
if the default sizes was not specified on commandline. It can be
worked around by this patch.
I also simplified the memory size calculation logic a bit so we append
'M' to QEMU_MEMORY at the very end instead of sed'ing it afterwards
(From OE-Core rev: 03ef61ed189264a75adbaf32644a80568b410b9b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While the metadata can and should rely on bb always being available, this
needn't necessarily be the case for imported python modules.
(From OE-Core rev: a521835701c07f5786acd663fb4fb394e93eba91)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This attempts to separate the bits we *require* to run bitbake with oe-core
via the wrapper script, and which are independent of the build environment
(PSEUDO_DISABLED, PSEUDO_BUILD, BBFETCH2) from those which are more particular
to poky-init-build-env's way of setting things up (e.g. adding MACHINE to
BB_ENV_EXTRAWHITE, relying on OEROOT, etc). This should make it easier to use
scripts/bitbake with non-standard workflows.
(From OE-Core rev: 7f9d6efcaf019eb046c8aa00735f823e3dbc8712)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this, as a specific example, one has both gtk+-native and gtk+ runtime
providing gdk-pixbuf-loader-*, and you can get bitbake preference conflicts as
a result if you have preferences specified for both gtk+ and gtk+-native for
other things.
(From OE-Core rev: 41d77ac37f606e54293826ba1e94a4254bddbfa6)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a problem with the current PACKAGE_EXTRA_ARCHS implementation
since its impossible to control which extra architectures sort higher
than TARGET_ARCH and which sort lower. In the x86 case for example,
TARGET_ARCH might be "i586", i486 should be lower than this and i686 should
be higher. There are also complications where its easy to inject duplicate
entries into the variable.
I tried various versions of this patch and concluded that it was simplest
just to force the tune files to include TARGET_ARCH in the list in the
right place if they're planning to customise it themselves. Other approaches
with appends and prepends just complicated the code for no good reason.
The TARGET_ARCH definitions should also move to the tune files but I'll
leave this for a separate patch.
(From OE-Core rev: d492ebf8b1801da99c679f465be98ce54fd3061a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The existing infrastructure uses an external build tree which references the
kernel source in the work dir. If run with rm work, building external modules
will fail.
This patch places a configured source tree in sysroots. Striking a balance
between minimal size and minimal maintenance is difficult. A fully configured
tree is about 500MB after a clean. This version leans on the side of caution and
removes only the obviously unecessary parts of the source tree to conserve
space, resulting in about 170MB. The arch directories would be some additional
pruning we could do. Given examples from the devel package from distributions, I
suspect this size could be reduced to 75MB or so, but at the cost of a much more
complex recipe which is likely to require a great deal more maintenance to keep
current with kernel releases.
Care is also taken to clean the hostprogs in scripts, and the modules are
responsible for building them as needed. Although it is unclear to me if this is
really necessary, especially considering that modules put these bits back as
soon as they compile. If we are not generating an sstate package, I suspect we
can ignore these.
Please try this with your modules and let me know how it does. I tried to take
non linux-yocto kernel recipes into account, but I have only tested with
linux-yocto and the hello-mod recipe so far.
(From OE-Core rev: a9d41062e24a6b99661b3a5256f369b557433607)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
Acked-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
LSB command check will test the exist of sendmail, so make sendmail
link to msmtp using update-alternatives class in order to pass the test.
Related to [YOCTO #520]
(From OE-Core rev: 97b71119d716eab86b8afcbac204f38a00b88cf3)
Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Qemu-needed is needed for the qemu* machines to build, but needs alsa-lib
(From OE-Core rev: 31177e0d187c06c30dfb9abe3f2344da3afd643d)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[BUGID# 873] - Added a note in the Images Appendix indicating that
building an image without GPLv3 components is only supported for
base and minimal images. Also put the two changes you have to do
to the local.conf file for the build.
Added a note in the second chapter in the section on building images.
The note indicates the same as in the appendix but does not go into the
local.conf file detail.
(From OE-Core rev: c7960a2e820d7ddb8649ab0b27b3f04843f7af0d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Try to make the output of the qemu script a bit more consistent by using the
same format for the various warning messages:
WARNING: description of warning.
Detailed description of warning, actions taken, and/or instructions to user.
(From OE-Core rev: 7895377378c197289b82e3bbc059454770911abd)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
nVidia's OpenGL libraries are known to have compatibility issues with qemu,
resulting in a segfault. As different workarounds are required for the different
distributions, just warn the user to explain the qemu segfault to follow, and
suggest a workaround using LD_PRELOAD.
[YOCTO #649]
[YOCTO #698]
(Original patch from Edwin, Darren modified warning and git commit wording)
(From OE-Core rev: 2247ffe954b5a71f82944d23141c836b38716654)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Mark Hatle <mark.hatle@windriver.com>
CC: Zhai Edwin <edwin.zhai@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Newer versions of patch, such as in Fedora 14, don't like ".." within
the middle of the file to be patched path.
In order to fix the issue we have to hand apply the patch instead of using
the normal mechanisms. Only flaw with the os.system(...) approach is if it
fails we don't get any notification or a resolver failure.
(From OE-Core rev: 4e592efe8c5ff918a77f7b7b2c17a6b698b1dd68)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adds a test to avoid the "sh: bad number" error message during service
start or stop of nfsserver when there is no NFS_SERVERS value set in
/etc/default/nfsd.
(From OE-Core rev: 0f2debd9360abac54d3e44551af309f0bdde96e7)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows "umount -f -a -r" in our initscripts to actually do something.
(From OE-Core rev: 578c938968857976f888f708f1f57cf862c7b3c4)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a note to reference the FAQ entry in the Poky manual that describes
how to get around proxy and firewall stuff hanging up getting the source
code during a build.
(From OE-Core rev: f9abba290157c122f36aed5e52f1a0f792e3add2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the beginning of the manual I added references to the FAQs we
support.
(From OE-Core rev: 615a015189f3b09ea928f288516be1f90447cbf2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj
Koen Kooi
Bruce Ashfield
Richard Purdie
Martin Jansa
Tom Rini
Chris Larson
Darren Hart
Kang Kai
Scott Rifenbark
Mark Hatle
Paul Eggleton