path: root/documentation/poky-ref-manual/faq.xml

<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

<appendix id='faq'>
<title>FAQ</title>
<qandaset>
    <qandaentry>
        <question>
            <para>
                How does Poky differ from <ulink url='http://www.openembedded.org/'>OpenEmbedded</ulink>?
            </para>
        </question>
        <answer>
            <para>
                Poky is the Yocto Project build system that was derived from <ulink 
                url='http://www.openembedded.org/'>OpenEmbedded</ulink>.
                Poky is a stable, smaller subset focused on the GNOME Mobile environment. 
                Development in the Yocto Project using Poky is closely tied to OpenEmbedded with 
                features being merged regularly between the two for mutual benefit.
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                I only have Python 2.4 or 2.5 but BitBake requires Python 2.6 or 2.7.
                Can I still use the Yocto Project?
            </para>
        </question>
        <answer>
            <para>
                You can use a stand-alone tarball to provide Python 2.6.
                You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations:
                <itemizedlist>
                    <listitem><para><ulink url='http://autobuilder.yoctoproject.org/downloads/miscsupport/yocto-1.0-python-nativesdk/python-nativesdk-standalone-i686.tar.bz2'>32-bit tarball</ulink></para></listitem>
                    <listitem><para><ulink url='http://autobuilder.yoctoproject.org/downloads/miscsupport/yocto-1.0-python-nativesdk/python-nativesdk-standalone-x86_64.tar.bz2'>64-bit tarball</ulink></para></listitem>
                </itemizedlist>
            </para>
            <para>
                These tarballs are self-contained with all required libraries and should work 
                on most Linux systems.  
                To use the tarballs extract them into the root 
                directory and run the appropriate command:
                <literallayout class='monospaced'>
     $ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH
     $ export PATH=/opt/poky/sysroots/x86_64-pokysdk-linux/usr/bin/:$PATH
                </literallayout>
            </para>
            <para>
                Once you run the command, BitBake uses Python 2.6.
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                How can you claim Poky is stable?
            </para>
        </question>
        <answer>
            <para>
                There are three areas that help with stability;
                <itemizedlist>
                    <listitem><para>The Yocto Project team keeps Poky small and focused.
                        It contains around 650 packages as compared to over 5000 for full 
                        OpenEmbedded.</para></listitem>
                    <listitem><para>The Yocto Project only supports hardware that the 
                        team has access to for testing.</para></listitem>
                    <listitem><para>The Yocto Project uses an an autobuilder,
                        which provides continuous build and integration tests.</para></listitem>
                </itemizedlist>
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                How do I get support for my board added to the Yocto Project?
            </para>
        </question>
        <answer>
            <para>
                There are two main ways to get a board supported in Poky;
                <itemizedlist>
                    <listitem><para>Send the Yocto Project team information on the board
                        and if the team does not have it yet they will consider adding it.</para></listitem>
                    <listitem><para>Send the Yocto Project team the BitBake recipes if you have them.
                        </para></listitem>
                </itemizedlist>
                Usually, if the board is not a completely exotic, adding support in 
                the Yocto Project is fairly straightforward.
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                Are there any products running poky?
            </para>
        </question>
        <answer>
            <para>
                The <ulink url='http://vernier.com/labquest/'>Vernier LabQuest</ulink> is using 
                Poky.  
                See the <ulink url='http://www.vernier.com/products/interfaces/labq/'>Vernier LabQuest</ulink>
                for more information.
                There are a number of pre-production devices using Poky and the Yocto Project team
                announces them as soon as they are released.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                What is the Poky output ?
            </para>
        </question>
        <answer>
            <para>
                The output of a Poky build will depend on how it was started, as the same set of recipes can be used to output various formats. Usually the output is a flashable image ready for the target device.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                How do I add my package to Poky?
            </para>
        </question>
        <answer>
            <para>
                To add a package you need to create a BitBake recipe - see the Poky handbook to find out how to create a recipe.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                Do I have to reflash my entire board with a new poky image when recompiling a package?
            </para>
        </question>
        <answer>
            <para>
                Poky can build packages in various formats, ipk (for ipkg/opkg), Debian package (.deb), or RPM. The packages can then be upgraded using the package tools on the device, much like on a desktop distribution like Ubuntu or Fedora.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                What is GNOME Mobile? What's the difference between GNOME Mobile and GNOME?
            </para>
        </question>
        <answer>
            <para>
                <ulink url='http://www.gnome.org/mobile/'>GNOME Mobile</ulink> is a subset of the GNOME platform targeted at mobile and embedded devices. The the main difference between GNOME Mobile and standard GNOME is that desktop-orientated libraries have been removed, along with deprecated libraries, creating a much smaller footprint. 
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                I see the error 'chmod: XXXXX new permissions are r-xrwxrwx, not r-xr-xr-x'. What's wrong?
            </para>
        </question>
        <answer>
            <para>
                You're probably running the build on an NTFS filesystem. Use a sane one like ext2/3/4 instead!
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                How do I make Poky work in RHEL/CentOS?
            </para>
        </question>
        <answer>
            <para>
                To get Poky working under RHEL/CentOS 5.1 you need to first install some required packages. The standard CentOS packages needed are:
                <itemizedlist>
                    <listitem>
                        <para>
                            "Development tools" (selected during installation)
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            texi2html
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            compat-gcc-34
                        </para>
                    </listitem>
                </itemizedlist>
            </para>

            <para>
                On top of those the following external packages are needed:
                <itemizedlist>
                    <listitem>
                        <para>
                            python-sqlite2 from <ulink
                                url='http://dag.wieers.com/rpm/packages/python-sqlite2/'>DAG
                                repository</ulink>
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            help2man from <ulink
                                url='http://centos.karan.org/el5/extras/testing/i386/RPMS/help2man-1.33.1-2.noarch.rpm'>Karan
                                repository</ulink>
                        </para>
                    </listitem>
                </itemizedlist>
            </para>

            <para>
                Once these packages are installed Poky will be able to build standard images however there 
                may be a problem with QEMU segfaulting. You can either disable the generation of binary 
                locales by setting <glossterm><link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>ENABLE_BINARY_LOCALE_GENERATION</link>
                </glossterm> to "0" or remove the linux-2.6-execshield.patch from the kernel and rebuild 
                it since its that patch which causes the problems with QEMU.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                I see lots of 404 responses for files on 
                http://autobuilder.yoctoproject.org/sources/*. Is something wrong?
            </para>
        </question>
        <answer>
            <para>
                Nothing is wrong, Poky will check any configured source mirrors before downloading 
                from the upstream sources. It does this searching for both source archives and 
                pre-checked out versions of SCM managed software. This is so in large installations, 
                it can reduce load on the SCM servers themselves. The address above is one of the 
                default mirrors configured into standard Poky so if an upstream source disappears, 
                we can place sources there so builds continue to work.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                I have a machine specific data in a package for one machine only but the package is 
                 being marked as machine specific in all cases, how do I stop it?
            </para>
        </question>
        <answer>
            <para>
                Set <glossterm><link linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link>
                </glossterm> = "0" in the .bb file but make sure the package is manually marked as 
                machine specific in the case that needs it. The code which handles <glossterm><link 
                linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link></glossterm>
		is in base.bbclass.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                I'm behind a firewall and need to use a proxy server. How do I do that?
            </para>
        </question>
        <answer>
            <para>
                Most source fetching by Poky is done by wget and you therefore need to specify the proxy 
                settings in a .wgetrc file in your home directory. Example settings in that file would be
                'http_proxy = http://proxy.yoyodyne.com:18023/' and 'ftp_proxy = http://proxy.yoyodyne.com:18023/'.
                Poky also includes a site.conf.sample file which shows how to configure cvs and git proxy servers
                if needed.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                I'm using Ubuntu Intrepid and am seeing build failures. What’s wrong?
            </para>
        </question>
        <answer>
            <para>
	        In Intrepid, Ubuntu turned on by default normally optional compile-time security features 
		and warnings. There are more details at <ulink
                url='https://wiki.ubuntu.com/CompilerFlags'>https://wiki.ubuntu.com/CompilerFlags</ulink>.
		You can work around this problem by disabling those options by adding " -Wno-format-security -U_FORTIFY_SOURCE" 
		to the BUILD_CPPFLAGS variable in conf/bitbake.conf.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                What’s the difference between foo and foo-native?
            </para>
        </question>
        <answer>
            <para>
                The *-native targets are designed to run on the system the build is running on. These are usually tools that are needed to assist the build in some way such as quilt-native which is used to apply patches. The non-native version is the one that would run on the target device.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                I'm seeing random build failures. Help?!
            </para>
        </question>
        <answer>
            <para>
                If the same build is failing in totally different and random ways the most likely explanation is that either the hardware you're running it on has some problem or if you are running it under virtualisation, the virtualisation probably has bugs. Poky processes a massive amount of data causing lots of network, disk and cpu activity and is sensitive to even single bit failure in any of these areas. Totally random failures have always been traced back to hardware or virtualisation issues.
            </para>
        </answer>
    </qandaentry>
    <qandaentry>
        <question>
            <para>
                What do we need to ship for license compliance?
            </para>
        </question>
        <answer>
            <para>
                This is a difficult question and you need to consult your lawyer for the answer for your specific case. Its worth bearing in mind that for GPL compliance there needs to be enough information shipped to allow someone else to rebuild the same end result as you are shipping. This means sharing the source code, any patches applied to it but also any configuration information about how that package was configured and built.
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                How do I disable the cursor on my touchscreen device?
            </para>
        </question>
        <answer>
            <para>
                You need to create a form factor file as described in 
                <xref linkend='bsp-filelayout-misc-recipes'>"Miscellaneous Recipe Files"</xref>
                and set the <filename>HAVE_TOUCHSCREEN</filename> variable equal to one.
                <literallayout class='monospaced'>
     HAVE_TOUCHSCREEN=1
                </literallayout>
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                How do I make sure connected network interfaces are brought up by default?
            </para>
        </question>
        <answer>
            <para>
                The default interfaces file provided by the netbase recipe does not 
                automatically bring up network interfaces. 
                Therefore you will need to add a BSP-specific netbase that includes an interfaces 
                file.
                See <xref linkend='bsp-filelayout-misc-recipes'>"Miscellaneous Recipe Files"</xref>
                for information on creating these types of miscellaneous recipe files.
            </para>
            <para>
                For example, add the following files to your layer:
                <literallayout class='monospaced'>
     meta-MACHINE/recipes-bsp/netbase/netbase/MACHINE/interfaces
     meta-MACHINE/recipes-bsp/netbase/netbase_4.44.bbappend
                </literallayout>
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                How do I create images with more free space?
            </para>
        </question>
        <answer>
            <para>
                Images are created to be 1.2 times the size of the populated root filesystem. 
                To modify this ratio so that there is more free space available you need to 
                set the configuration value <filename>IMAGE_OVERHEAD_FACTOR</filename>.  
                For example, setting <filename>IMAGE_OVERHEAD_FACTOR</filename> to 1.5 sets 
                the image size ratio to one and a half times the size of the populated 
                root filesystem.
                <literallayout class='monospaced'>
     IMAGE_OVERHEAD_FACTOR = "1.5"
                </literallayout>
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                Why don't you support directories with spaces in the pathnames?
            </para>
        </question>
        <answer>
            <para>
                We have tried to do this before but too many of the tools we depend on such as autoconf 
                break when they find spaces in pathnames.  
                Until that situation changes we will not support spaces in pathnames.
            </para>
        </answer>
    </qandaentry>

    <qandaentry>
        <question>
            <para>
                How do I use an external toolchain?
            </para>
        </question>
        <answer>
            <para>
                The toolchain configuration is very flexible and customizable.
                It is primarily controlled with the TCMODE variable.
                This variable controls which file to include 
                (<filename>conf/distro/include/tcmode-*.inc</filename>).
            </para>
            <para>
                The default value of TCMODE is "default".
                However, other patterns are accepted.
                In particular, "external-*" refers to external toolchains of which there are some basic examples
                included with the core.
                A user can use their own custom toolchain definition in their own layer 
                (or <filename>local.conf</filename> directory) at the location 
                <filename>conf/distro/include/tcmode-*.inc</filename>.
            </para>
            <para>
                In addition to the toolchain configuration, you also need a corresponding toolchain recipe file.
                This recipe file needs to package up any pre-built objects in the toolchain such as 
                <filename>libgcc</filename>, <filename>libstdcc++</filename>, 
                any locales and <filename>libc</filename>.
                An example is the <filename>external-csl-toolchain_2008q3-72.bb</filename>, which reuses the core 
                <filename>libc</filename> packaging class to do most of the work.
            </para>
        </answer>
    </qandaentry>




    <qandaentry>
        <question>
            <para>
                How does Poky obtain source code and will it work behind my firewall or proxy server?
            </para>
        </question>
        <answer>
            <para>
                The way Poky obtains source code is highly configurable.
                You can setup Poky to get source code in most environments if
                HTTP transport is available.
            </para>
            <para>
                When Poky searches for source code it first tries the local download directory.
                If that location fails, Poky tries PREMIRRORS, the upstream source, 
                and then MIRRORS in that order.
            </para>
            <para>
                By default, Poky uses the Yocto Project source PREMIRRORS for SCM-based sources, 
                upstreams for normal tarballs and then falls back to a number of other mirrors 
                including the Yocto Project source mirror if those fail.
            </para>
            <para>
                As an example, you could add a specific server for Poky to attempt before any
                others by adding something like the following to the <filename>local.conf</filename>
                configuration file:
                <literallayout class='monospaced'>
     PREMIRRORS_prepend = "\
     git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
     ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
     http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
     https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
                </literallayout>
            </para>
            <para>
                These changes cause Poky to intercept GIT, FTP, HTTP, and HTTPS
                requests and direct them to the <filename>http://</filename> sources mirror.
                You can use <filename>file://</filename> URLs to point to local directories 
                or network shares as well.
            </para>
            <para>
                Aside from the previous technique, these options also exist:
                <literallayout class='monospaced'>
     BB_NO_NETWORK = "1"
                </literallayout>
             </para>
             <para>
                 This statement tells BitBake to throw an error instead of trying to access the 
                 Internet.
                 This technique is useful if you want to ensure code builds only from local sources.
             </para>
             <para>
                 Here is another technique:
                 <literallayout class='monospaced'>
     BB_FETCH_PREMIRRORONLY = "1"
                 </literallayout>
             </para>
             <para>
                 This statement limits Poky to pulling source from the PREMIRRORS only.
                 Again, this technique is useful for reproducing builds.
             </para>
             <para>
                 Here is another technique:
                 <literallayout class='monospaced'>
     BB_GENERATE_MIRROR_TARBALLS = "1"
                 </literallayout>
             </para>
             <para>
                 This statement tells Poky to generate mirror tarballs.
                 This technique is useful if you want to create a mirror server.
                 If not, however, the technique can simply waste time during the build.
             </para>
             <para>
                 Finally, consider an example where you are behind an HTTP-only firewall.
                 You could make the following changes to the <filename>local.conf</filename>
                 configuration file as long as the premirror server is up to date:
                 <literallayout class='monospaced'>
     PREMIRRORS_prepend = "\
     ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
     http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
     https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
     BB_FETCH_PREMIRRORONLY = "1" 
                 </literallayout>
             </para>
             <para>
                 These changes would cause Poky to successfully fetch source over HTTP and 
                 any network accesses to anything other than the premirror would fail.
             </para>
             <para>
                 Poky also honors the standard environment variables 
                 <filename>http_proxy</filename>, <filename>ftp_proxy</filename>, 
                 <filename>https_proxy</filename>, and <filename>all_proxy</filename>
                 to redirect requests through proxy servers.
             </para>
        </answer>
    </qandaentry>



</qandaset>
</appendix>
<!-- 
vim: expandtab tw=80 ts=4 
-->