sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity
OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
29,896 Commits 8 Branches 0 Tags 142 MiB
Python 37.9%
BitBake 15.7%
C 15.5%
PHP 10%
Shell 7.2%
Other 13.4%
Go to file
Richard Purdie 6467fb38f4 elfutils: Fix debugedit failure in grub 
We've seeing occasional debugedit failures in grub during do_package
which in turn are coming from section alignment failures from libelf.
The failures occur when gold is used to link grub instead of ld.bfd.

"readelf -e uhci.module" shows:

Section Headers:
  [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
  [12] .note.GNU-stack   PROGBITS        00000000 0010ce 000000 00      0   0  1

in a good build and:

Section Headers:
  [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
  [24] .note.GNU-stack   PROGBITS        00000000 009180 000000 00      0   0  0

in a bad build. The problem is the "Al" (alignment) change from 1 to 0.
If its 0, debugedit complains.

As far as I can tell, the alignment of a zero length section is not
an issue and the check in libelf should check the section size and only
give alignment errors if there is some data to align.

(From OE-Core rev: b34447fa5223b4e0be49594aaf0254defd69bbd1)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
 		2014-06-13 12:53:05 +01:00
bitbake bitbake: toaster: build control functionality 2014-06-13 11:55:34 +01:00
documentation dev-manual: Updates to the "Making Images More Secure" section. 2014-05-30 16:32:19 +01:00
meta elfutils: Fix debugedit failure in grub 2014-06-13 12:53:05 +01:00
meta-selftest Basic recipe formatting fixes 2014-01-02 12:50:21 +00:00
meta-skeleton linux-yocto-custom: provide defconfig guidance 2014-05-06 17:59:17 +01:00
meta-yocto busybox: fix meta-yocto's bbappend's FILESEXTRAPATH 2014-06-03 17:53:13 +01:00
meta-yocto-bsp oeqa/controllers/beaglebonetarget.py: fix conditions for files copied to /boot 2014-06-03 10:38:24 +01:00
scripts scripts/test-remote-image: Add script for running runtime tests on remotely built images 2014-06-13 12:52:21 +01:00
.gitignore bitbake: gitignore: Update for recent docs changes 2014-01-27 21:03:13 +00:00
.templateconf .templateconf: New file for customized template defaults 2014-03-11 08:14:27 -07:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
README README: fix DISTRO = "" reference 2014-01-02 12:58:54 +00:00
README.hardware README: add maintainers section for hardware reference boards 2014-05-19 16:13:13 +01:00
oe-init-build-env oe-init-build-env: Improve script sourcing detection. 2014-03-11 08:11:41 -07:00
oe-init-build-env-memres oe-init-build-env-memres: Add auto port functionality 2013-12-02 11:28:27 +00:00

README 

Poky
====

Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with IDE integration.

Additional information on the specifics of hardware that Poky supports
is available in README.hardware. Further hardware support can easily be added
in the form of layers which extend the systems capabilities in a modular way.

As an integration layer Poky consists of several upstream projects such as 
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information 
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.

The Yocto Project has extensive documentation about the system including a 
reference manual which can be found at:
    http://yoctoproject.org/documentation

OpenEmbedded-Core is a layer containing the core metadata for current versions
of OpenEmbedded. It is distro-less (can build a functional image with
DISTRO = "nodistro") and contains only emulated machine support.

For information about OpenEmbedded, see the OpenEmbedded website:
    http://www.openembedded.org/

Where to Send Patches
=====================

As Poky is an integration repository, patches against the various components
should be sent to their respective upstreams.

bitbake:
    bitbake-devel@lists.openembedded.org

meta-yocto:
    poky@yoctoproject.org

Most everything else should be sent to the OpenEmbedded Core mailing list.  If
in doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git
repository.
    openembedded-core@lists.openembedded.org

Note: The scripts directory should be treated with extra care as it is a mix
      of oe-core and poky-specific files.