mirror of
https://git.yoctoproject.org/poky
synced 2026-05-30 00:20:08 +00:00
Robert Yang
238e9b54e2
There would be an error when the TMPDIR is long/deep, for example when len(TMPDIR) = 350 while our supported longest value is 410: [snip] aclocal: error: cannot open xxx autoreconf: aclocal failed with exit status: 1 ERROR: autoreconf execution failed. [snip] Let aclocal use the relative path for the m4 file rather than the absolute would fix the problem. Another fix is that we can modify autotools.bbclass to let it use the relative path rather than the absolute, but I don't think that we have to do that based on the following 2 thoughts: * The coreutils is the only recipe which has this issue as far as we know when len(TMPDIR) <= 410, because it has the most amount of m4 files (more than 400 ones). * That would impact all the recipes which use autotools.bbclass, and we are not sure about the side effect, for example, it would break the build there is a sub-configure. [YOCTO #2766] (From OE-Core rev: 22ac874512c2c1213aae8e1644bd59050b37a63c) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.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 = "") 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.