f5205c568c
By default LDFLAGSICUDT=-nodefaultlibs -nostdlib for Linux which means DT_NEEDED section for libicu will not be populated with dependencies when we reset it to be empty then the default libraries it needs are added to DT_NEEDED section in ELF header This patch is a workaround as I consider it for now, since it could be a problem in glibc dynamic loader for arm (especially for hf case) where its unable to load shared objects which dont have any dependencies expressed in DT_NEEDED segment. here is when LDFLAGSICUDT=-nodefaultlibs -nostdlib Dynamic section at offset 0x1549c10 contains 8 entries: Tag Type Name/Value 0x0000000e (SONAME) Library soname: [libicudata.so.51] 0x00000010 (SYMBOLIC) 0x0 0x6ffffef5 (GNU_HASH) 0xf8 0x00000005 (STRTAB) 0x188 0x00000006 (SYMTAB) 0x138 0x0000000a (STRSZ) 54 (bytes) 0x0000000b (SYMENT) 16 (bytes) 0x00000000 (NULL) 0x0 here is one with LDFLAGSICUDT empty Dynamic section at offset 0x154a014 contains 22 entries: Tag Type Name/Value 0x00000001 (NEEDED) Shared library: [libc.so.6] 0x0000000e (SONAME) Library soname: [libicudata.so.51] 0x00000010 (SYMBOLIC) 0x0 0x0000000c (INIT) 0x33c 0x0000000d (FINI) 0x500 0x6ffffef5 (GNU_HASH) 0xf8 0x00000005 (STRTAB) 0x204 0x00000006 (SYMTAB) 0x144 0x0000000a (STRSZ) 192 (bytes) 0x0000000b (SYMENT) 16 (bytes) 0x00000003 (PLTGOT) 0x154a0f8 0x00000002 (PLTRELSZ) 16 (bytes) 0x00000014 (PLTREL) REL 0x00000017 (JMPREL) 0x32c 0x00000011 (REL) 0x2fc 0x00000012 (RELSZ) 48 (bytes) 0x00000013 (RELENT) 8 (bytes) 0x6ffffffe (VERNEED) 0x2dc 0x6fffffff (VERNEEDNUM) 1 0x6ffffff0 (VERSYM) 0x2c4 0x6ffffffa (RELCOUNT) 1 0x00000000 (NULL) 0x0 btw. ldd reveals the fist one to be static library while the second one is detected as shared library. This could be a clue into how elf headers are being interpreted by dynamic loader. The data seems to be all static in libicudata which could load it quicker and thats what could be confusing dynamic linker ..may be (From OE-Core rev: 644c307f63f0f0b7e97140850d3d1d2124b11b1b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.