summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/faq.xml
diff options
context:
space:
mode:
authorRichard Purdie <rpurdie@linux.intel.com>2010-10-15 11:55:59 +0100
committerRichard Purdie <rpurdie@linux.intel.com>2010-10-15 11:55:59 +0100
commit22083287912ebd552e33b79f7c567bc966376d43 (patch)
treea16fa012a97a249e25a405d4092b0a89321bfaf6 /documentation/poky-ref-manual/faq.xml
parent13a702e9e572a2dc9f6b52a1531a2237d4d98ff1 (diff)
downloadpoky-22083287912ebd552e33b79f7c567bc966376d43.tar.gz
handbook: Move into documentation directory
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'documentation/poky-ref-manual/faq.xml')
-rw-r--r--documentation/poky-ref-manual/faq.xml314
1 files changed, 314 insertions, 0 deletions
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml
new file mode 100644
index 0000000000..b209fff81d
--- /dev/null
+++ b/documentation/poky-ref-manual/faq.xml
@@ -0,0 +1,314 @@
1<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
3
4<appendix id='faq'>
5<title>FAQ</title>
6<qandaset>
7 <qandaentry>
8 <question>
9 <para>
10 How does Poky differ from <ulink url='http://www.openembedded.org/'>OpenEmbedded</ulink>?
11 </para>
12 </question>
13 <answer>
14 <para>
15 Poky is a derivative of <ulink
16 url='http://www.openembedded.org/'>OpenEmbedded</ulink>, a stable,
17 smaller subset focused on the GNOME Mobile environment. Development
18 in Poky is closely tied to OpenEmbedded with features being merged
19 regularly between the two for mutual benefit.
20 </para>
21 </answer>
22 </qandaentry>
23 <qandaentry>
24 <question>
25 <para>
26 How can you claim Poky is stable?
27 </para>
28 </question>
29 <answer>
30 <para>
31 There are three areas that help with stability;
32
33 <itemizedlist>
34 <listitem>
35 <para>
36 We keep Poky small and focused - around 650 packages compared to over 5000 for full OE
37 </para>
38 </listitem>
39 <listitem>
40 <para>
41 We only support hardware that we have access to for testing
42 </para>
43 </listitem>
44 <listitem>
45 <para>
46 We have an autobuilder which provides continuous build and integration tests
47 </para>
48 </listitem>
49 </itemizedlist>
50 </para>
51 </answer>
52 </qandaentry>
53 <qandaentry>
54 <question>
55 <para>
56 How do I get support for my board added to Poky?
57 </para>
58 </question>
59 <answer>
60 <para>
61 There are two main ways to get a board supported in Poky;
62 <itemizedlist>
63 <listitem>
64 <para>
65 Send us the board if we don't have it yet
66 </para>
67 </listitem>
68 <listitem>
69 <para>
70 Send us bitbake recipes if you have them (see the Poky handbook to find out how to create recipes)
71 </para>
72 </listitem>
73 </itemizedlist>
74 Usually if it's not a completely exotic board then adding support in Poky should be fairly straightforward.
75 </para>
76 </answer>
77 </qandaentry>
78 <qandaentry>
79 <question>
80 <para>
81 Are there any products running poky ?
82 </para>
83 </question>
84 <answer>
85 <para>
86 The <ulink url='http://vernier.com/labquest/'>Vernier Labquest</ulink> is using Poky (for more about the Labquest see the case study at OpenedHand). There are a number of pre-production devices using Poky and we will announce those as soon as they are released.
87 </para>
88 </answer>
89 </qandaentry>
90 <qandaentry>
91 <question>
92 <para>
93 What is the Poky output ?
94 </para>
95 </question>
96 <answer>
97 <para>
98 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.
99 </para>
100 </answer>
101 </qandaentry>
102 <qandaentry>
103 <question>
104 <para>
105 How do I add my package to Poky?
106 </para>
107 </question>
108 <answer>
109 <para>
110 To add a package you need to create a bitbake recipe - see the Poky handbook to find out how to create a recipe.
111 </para>
112 </answer>
113 </qandaentry>
114 <qandaentry>
115 <question>
116 <para>
117 Do I have to reflash my entire board with a new poky image when recompiling a package?
118 </para>
119 </question>
120 <answer>
121 <para>
122 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.
123 </para>
124 </answer>
125 </qandaentry>
126 <qandaentry>
127 <question>
128 <para>
129 What is GNOME Mobile? What's the difference between GNOME Mobile and GNOME?
130 </para>
131 </question>
132 <answer>
133 <para>
134 <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.
135 </para>
136 </answer>
137 </qandaentry>
138 <qandaentry>
139 <question>
140 <para>
141 I see the error 'chmod: XXXXX new permissions are r-xrwxrwx, not r-xr-xr-x'. What's wrong?
142 </para>
143 </question>
144 <answer>
145 <para>
146 You're probably running the build on an NTFS filesystem. Use a sane one like ext2/3/4 instead!
147 </para>
148 </answer>
149 </qandaentry>
150 <qandaentry>
151 <question>
152 <para>
153 How do I make Poky work in RHEL/CentOS?
154 </para>
155 </question>
156 <answer>
157 <para>
158 To get Poky working under RHEL/CentOS 5.1 you need to first install some required packages. The standard CentOS packages needed are:
159 <itemizedlist>
160 <listitem>
161 <para>
162 "Development tools" (selected during installation)
163 </para>
164 </listitem>
165 <listitem>
166 <para>
167 texi2html
168 </para>
169 </listitem>
170 <listitem>
171 <para>
172 compat-gcc-34
173 </para>
174 </listitem>
175 </itemizedlist>
176 </para>
177
178 <para>
179 On top of those the following external packages are needed:
180 <itemizedlist>
181 <listitem>
182 <para>
183 python-sqlite2 from <ulink
184 url='http://dag.wieers.com/rpm/packages/python-sqlite2/'>DAG
185 repository</ulink>
186 </para>
187 </listitem>
188 <listitem>
189 <para>
190 help2man from <ulink
191 url='http://centos.karan.org/el5/extras/testing/i386/RPMS/help2man-1.33.1-2.noarch.rpm'>Karan
192 repository</ulink>
193 </para>
194 </listitem>
195 </itemizedlist>
196 </para>
197
198 <para>
199 Once these packages are installed Poky will be able to build standard images however there
200 may be a problem with QEMU segfaulting. You can either disable the generation of binary
201 locales by setting <glossterm><link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>ENABLE_BINARY_LOCALE_GENERATION</link>
202 </glossterm> to "0" or remove the linux-2.6-execshield.patch from the kernel and rebuild
203 it since its that patch which causes the problems with QEMU.
204 </para>
205 </answer>
206 </qandaentry>
207 <qandaentry>
208 <question>
209 <para>
210 I see lots of 404 responses for files on http://pokylinux.org/sources/*. Is something wrong?
211 </para>
212 </question>
213 <answer>
214 <para>
215 Nothing is wrong, Poky will check any configured source mirrors before downloading
216 from the upstream sources. It does this searching for both source archives and
217 pre-checked out versions of SCM managed software. This is so in large installations,
218 it can reduce load on the SCM servers themselves. The address above is one of the
219 default mirrors configured into standard Poky so if an upstream source disappears,
220 we can place sources there so builds continue to work.
221 </para>
222 </answer>
223 </qandaentry>
224 <qandaentry>
225 <question>
226 <para>
227 I have a machine specific data in a package for one machine only but the package is
228 being marked as machine specific in all cases, how do I stop it?
229 </para>
230 </question>
231 <answer>
232 <para>
233 Set <glossterm><link linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link>
234 </glossterm> = "0" in the .bb file but make sure the package is manually marked as
235 machine specific in the case that needs it. The code which handles <glossterm><link
236 linkend='var-SRC_URI_OVERRIDES_PACKAGE_ARCH'>SRC_URI_OVERRIDES_PACKAGE_ARCH</link></glossterm>
237 is in base.bbclass.
238 </para>
239 </answer>
240 </qandaentry>
241 <qandaentry>
242 <question>
243 <para>
244 I'm behind a firewall and need to use a proxy server. How do I do that?
245 </para>
246 </question>
247 <answer>
248 <para>
249 Most source fetching by Poky is done by wget and you therefore need to specify the proxy
250 settings in a .wgetrc file in your home directory. Example settings in that file would be
251 'http_proxy = http://proxy.yoyodyne.com:18023/' and 'ftp_proxy = http://proxy.yoyodyne.com:18023/'.
252 Poky also includes a site.conf.sample file which shows how to configure cvs and git proxy servers
253 if needed.
254 </para>
255 </answer>
256 </qandaentry>
257 <qandaentry>
258 <question>
259 <para>
260 I'm using Ubuntu Intrepid and am seeing build failures. Whats wrong?
261 </para>
262 </question>
263 <answer>
264 <para>
265 In Intrepid, Ubuntu turned on by default normally optional compile-time security features
266 and warnings. There are more details at <ulink
267 url='https://wiki.ubuntu.com/CompilerFlags'>https://wiki.ubuntu.com/CompilerFlags</ulink>.
268 You can work around this problem by disabling those options by adding " -Wno-format-security -U_FORTIFY_SOURCE"
269 to the BUILD_CPPFLAGS variable in conf/bitbake.conf.
270 </para>
271 </answer>
272 </qandaentry>
273 <qandaentry>
274 <question>
275 <para>
276 Whats the difference between foo and foo-native?
277 </para>
278 </question>
279 <answer>
280 <para>
281 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.
282 </para>
283 </answer>
284 </qandaentry>
285 <qandaentry>
286 <question>
287 <para>
288 I'm seeing random build failures. Help?!
289 </para>
290 </question>
291 <answer>
292 <para>
293 If the same build is failing in totally different and random ways the most likely explaination 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 senstive to even single bit failure in any of these areas. Totally random failures have always been traced back to hardware or virtualisation issues.
294 </para>
295 </answer>
296 </qandaentry>
297 <qandaentry>
298 <question>
299 <para>
300 What do we need to ship for licence complience?
301 </para>
302 </question>
303 <answer>
304 <para>
305 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 complience 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.
306 </para>
307 </answer>
308 </qandaentry>
309</qandaset>
310</appendix>
311<!--
312vim: expandtab tw=80 ts=4
313-->
314
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-02 23:47:41 +0000