/[gentoo]/xml/htdocs/doc/en/gentoo-amd64-faq.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-amd64-faq.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.21 Revision 1.22
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.21 2006/10/06 22:01:53 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.22 2006/10/25 12:54:26 neysx Exp $ -->
4 4
5<guide link="/doc/en/gentoo-amd64-faq.xml"> 5<guide link="/doc/en/gentoo-amd64-faq.xml">
6<title>Gentoo Linux/AMD64 Frequently Asked Questions</title> 6<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
7 7
8<author title="Editor">
9 <mail link="blubb@gentoo.org">Simon Stelling</mail>
10</author>
8<author title="Editor"> 11<author title="Editor">
9 <mail link="metalgod@gentoo.org">Luis Medinas</mail> 12 <mail link="metalgod@gentoo.org">Luis Medinas</mail>
10</author> 13</author>
11<author title="Editor"> 14<author title="Editor">
12 <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail> 15 <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
13</author> 16</author>
14<author title="Editor"> 17<author title="Editor">
15 <mail link="blubb@gentoo.org">Simon Stelling</mail>
16</author>
17<author title="Editor">
18 <mail link="neysx@gentoo.org">Xavier Neys</mail> 18 <mail link="neysx@gentoo.org">Xavier Neys</mail>
19</author> 19</author>
20 20
21<abstract> 21<abstract>
22This is the Gentoo Linux/AMD64 Frequently Asked Questions 22This is the Gentoo Linux/AMD64 Frequently Asked Questions
24 24
25<!-- The content of this document is licensed under the CC-BY-SA license --> 25<!-- The content of this document is licensed under the CC-BY-SA license -->
26<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 26<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
27<license/> 27<license/>
28 28
29<version>1.15</version> 29<version>1.16</version>
30<date>2006-10-06</date> 30<date>2006-10-25</date>
31 31
32<chapter> 32<chapter>
33<title>Questions</title> 33<title>Questions</title>
34<section> 34<section>
35<title>Introduction to Gentoo/AMD64 FAQ</title> 35<title>Introduction to Gentoo/AMD64 FAQ</title>
36<body> 36<body>
37 37
38<p> 38<p>
39This document contains the most commonly asked questions about Gentoo/AMD64. We 39This document contains the most commonly asked questions about Gentoo/AMD64. We
40intend to help and provide useful information about Gentoo/AMD64. Some of these 40intend to help and provide useful information about Gentoo/AMD64. Some of these
41questions can be found in forums, IRC, or mailing lists. If you have suggestions 41questions can be found in forums, IRC, or mailing lists. If you have
42or questions about this FAQ, you are welcome to send an e-mail to the authors 42suggestions or questions about this FAQ, you are welcome to send an e-mail to
43explaining the problem. 43<mail>amd64@gentoo.org</mail>.
44</p> 44</p>
45 45
46</body> 46</body>
47</section> 47</section>
48<section> 48<section>
54 <li><uri link="#kernel">What kernel should I use?</uri></li> 54 <li><uri link="#kernel">What kernel should I use?</uri></li>
55 <li> 55 <li>
56 <uri link="#perfup">Will I have a performance upgrade if I use a 64-bit 56 <uri link="#perfup">Will I have a performance upgrade if I use a 64-bit
57 system instead of 32-bit?</uri> 57 system instead of 32-bit?</uri>
58 </li> 58 </li>
59 <li>
60 <uri link="#emul32">How do I get 32-bit emulation for my system?</uri>
61 </li>
62 <li><uri link="#multilib">What is multilib and how can I use it?</uri></li> 59 <li><uri link="#multilib">What is multilib and how can I use it?</uri></li>
63 <li><uri link="#chroot32">How do I create a 32-bit chroot?</uri></li> 60 <li><uri link="#chroot32">How do I create a 32-bit chroot?</uri></li>
64 <li> 61 <li>
65 <uri link="#upgradex86">Can I upgrade from my x86 system to amd64 by doing 62 <uri link="#upgradex86">Can I upgrade from my x86 system to amd64 by doing
66 emerge -e world?</uri> 63 emerge -e world?</uri>
90<body> 87<body>
91 88
92<ul> 89<ul>
93 <li><uri link="#flash">Can I get Macromedia Flash working?</uri></li> 90 <li><uri link="#flash">Can I get Macromedia Flash working?</uri></li>
94 <li><uri link="#OOo">Can I get OpenOffice.org working?</uri></li> 91 <li><uri link="#OOo">Can I get OpenOffice.org working?</uri></li>
95 <li><uri link="#java">How do I get java working in my browser?</uri></li>
96 <li> 92 <li>
97 <uri link="#masked">I want to install package foo, but emerge says: (masked 93 <uri link="#masked">I want to install package foo, but emerge says: (masked
98 by: ~amd64 keyword)</uri> 94 by: ~amd64 keyword)</uri>
99 </li> 95 </li>
100 <li> 96 <li>
108<section> 104<section>
109<title>How can I help the Gentoo/AMD64 project?</title> 105<title>How can I help the Gentoo/AMD64 project?</title>
110<body> 106<body>
111 107
112<ul> 108<ul>
113 <li><uri link="#bugs">How do I report bugs?</uri></li>
114 <li><uri link="#project">How can I help?</uri></li> 109 <li><uri link="#project">How can I help?</uri></li>
115</ul> 110</ul>
116 111
117</body> 112</body>
118</section> 113</section>
137<title>What CFLAGS should I use for AMD64/EM64T?</title> 132<title>What CFLAGS should I use for AMD64/EM64T?</title>
138<body> 133<body>
139 134
140<p> 135<p>
141You should use simple <c>CFLAGS</c> to avoid future problems with your system. 136You should use simple <c>CFLAGS</c> to avoid future problems with your system.
142For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or 137Supported <c>CFLAGS</c> are <c>-O2 -march=k8 -pipe</c> for non-EM64T systems and
143Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for an EM64T processor. If 138<c>-O2 -march=nocona -pipe</c> for EM64T systems.
144you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp -O2
145-pipe -msse2"</c> for an AMD64 processor; for an EM64T, you should use
146<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>.
147</p> 139</p>
148
149<note>
150<c>-march=k8</c> is the same as <c>-march=athlon64</c> and
151<c>-march=opteron</c>.
152</note>
153
154<warn>
155You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in
156your <c>CFLAGS</c>. They are automatically added whenever they are needed.
157Please also note that the <c>-Os</c> flag is currently not supported.
158</warn>
159 140
160</body> 141</body>
161</section> 142</section>
162<section id="kernel"> 143<section id="kernel">
163<title>What kernel should I use for AMD64?</title> 144<title>What kernel should I use for AMD64?</title>
165 146
166<p> 147<p>
167You can use almost all kernel sources available in Portage. We recommend using 148You can use almost all kernel sources available in Portage. We recommend using
168<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux. 149<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
169It contains lots of AMD64-specific patches and therefore is the only kernel 150It contains lots of AMD64-specific patches and therefore is the only kernel
170officially supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as 151officially supported by Gentoo/AMD64.
171well. If you feel brave or you need extra hardware support, you can always try
172the experimental kernel from Andrew Morton called <c>mm-sources</c>.
173</p> 152</p>
174 153
175<warn> 154<warn>
176You should watch out for some kernel features which are not well tested, such 155You should watch out for some kernel features which are not well tested, such
177as <c>PREEMPT</c>. 156as <c>PREEMPT</c>.
157</warn>
158
159<p>
160Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel.
161</p>
162
163<pre caption="Activating IA32 Emulation in Kernel source">
164# <i>cd /usr/src/linux</i>
165# <i>make menuconfig</i>
166
167Executable file formats / Emulations ---&gt;
168 [*] IA32 Emulation
169</pre>
170
171<warn>
172You may experience build failures on multilib-systems if you deactivate this
173option.
178</warn> 174</warn>
179 175
180</body> 176</body>
181</section> 177</section>
182<section id="perfup"> 178<section id="perfup">
195<uri link="http://forums.gentoo.org">forums</uri>. 191<uri link="http://forums.gentoo.org">forums</uri>.
196</p> 192</p>
197 193
198</body> 194</body>
199</section> 195</section>
200<section id="emul32">
201<title>How do I get 32-bit emulation for my system?</title>
202<body>
203
204<p>
205You have to install a few packages to get 32-bit libraries into your system.
206These packages are automatically pulled in as dependencies for 32-bit
207applications by Portage, so there is no need to manually emerge them. You can
208install such packages by doing:
209</p>
210
211<pre caption="Installing 32-bit libraries">
212# <i>emerge emul-linux-x86-baselibs</i>
213# <i>emerge emul-linux-x86-compat</i>
214</pre>
215
216<p>
217Furthermore, you need the <c>IA32_EMULATION</c> option activated in the kernel.
218</p>
219
220<pre caption="Activating IA32 Emulation in Kernel source">
221# <i>cd /usr/src/linux</i>
222# <i>make menuconfig</i>
223
224Executable file formats / Emulations ---&gt;
225 [*] IA32 Emulation
226</pre>
227
228</body>
229</section>
230<section id="multilib"> 196<section id="multilib">
231<title>What is multilib and how can I use it?</title> 197<title>What is multilib and how can I use it?</title>
232<body> 198<body>
233 199
234<p> 200<p>
238applications if all shared libraries it needs are available as 32-bit objects. 204applications if all shared libraries it needs are available as 32-bit objects.
239You can choose whether you want multilib support or not by selecting the 205You can choose whether you want multilib support or not by selecting the
240according profile. The default is a multilib-enabled profile. 206according profile. The default is a multilib-enabled profile.
241</p> 207</p>
242 208
209<warn>
210Currently you cannot switch from a no-multilib to a multilib-enabled profile,
211so think over your decision twice before you use the no-multilib profile.
212</warn>
213
243</body> 214</body>
244</section> 215</section>
245<section id="chroot32"> 216<section id="chroot32">
246<title>How do I create a 32-bit chroot?</title> 217<title>How do I create a 32-bit chroot?</title>
247<body> 218<body>
248 219
249<p> 220<p>
250Please read the <uri 221Please read the <uri link="/proj/en/base/amd64/howtos/chroot.xml">32-bit chroot
251link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=2">32-bit chroot
252guide</uri>. 222guide</uri>.
253</p> 223</p>
254 224
255</body> 225</body>
256</section> 226</section>
342<section id="flash"> 312<section id="flash">
343<title>Can I get Macromedia Flash working?</title> 313<title>Can I get Macromedia Flash working?</title>
344<body> 314<body>
345 315
346<p> 316<p>
347Yes. To get Flash working, you need a 32-bit browser like <c>mozilla-bin</c>, 317Yes. To get Flash working, you need a 32-bit browser like
348<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a 318<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
34964-bit version. After emerging the -bin-package of your favorite browser, 31964-bit version. After emerging the -bin package of your favorite browser,
350install Flash by doing <c>emerge netscape-flash</c>. 320install Flash by doing <c>emerge netscape-flash</c>.
351</p> 321</p>
352 322
353</body> 323</body>
354</section> 324</section>
355<section id="OOo"> 325<section id="OOo">
356<title>Can I get OpenOffice.org working?</title> 326<title>Can I get OpenOffice.org working?</title>
357<body> 327<body>
358 328
359<p> 329<p>
360OpenOffice 1.x and 2.0.x do not build on 64-bit systems, so you have to use the 330OpenOffice versions prior to 2.0.4 do not build on 64-bit systems, so you have to use the
36132-bit binary version, available in Portage as <c>openoffice-bin</c>. 33132-bit binary version, available in Portage as <c>app-office/openoffice-bin</c>.
362</p> 332If you feel brave you can <c>emerge openoffice</c>, but be aware that the 64-bit version
363 333is not yet tested out enough to be considered stable.
364</body>
365</section>
366<section id="java">
367<title>How do I get java working in my browser?</title>
368<body>
369
370<p> 334</p>
371Blackdown provides a 64-bit JRE. To install it, <c>emerge blackdown-jre</c>.
372Then, perform the following step:
373</p>
374
375<pre caption="Example of java link to browser plugins">
376# <i>ln -s /opt/blackdown-jre-*/plugin/amd64/mozilla/libjavaplugin_oji.so /usr/lib64/nsbrowser/plugins/libjavaplugin_oji.so</i>
377</pre>
378 335
379</body> 336</body>
380</section> 337</section>
381<section id="masked"> 338<section id="masked">
382<title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title> 339<title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title>
399 356
400<p> 357<p>
401This means that the package has not been tested yet. It does <e>not 358This means that the package has not been tested yet. It does <e>not
402necessarily</e> mean that the package does not work. You can unmask it by 359necessarily</e> mean that the package does not work. You can unmask it by
403accepting another architecture for the package. The following example shows you 360accepting another architecture for the package. The following example shows you
404can tell Portage to accept the ~x86 keyword for a given package. 361can tell Portage to accept any keyword for a given package.
405</p> 362</p>
406 363
407<pre caption="Example of adding package keywords"> 364<pre caption="Example of adding package keywords">
408# <i>echo "category/packagename ~x86" >> /etc/portage/package.keywords</i> 365# <i>echo "category/packagename ~* *" >> /etc/portage/package.keywords</i>
409# <i>emerge packagename</i> 366# <i>emerge packagename</i>
410</pre> 367</pre>
411 368
412<p> 369<p>
413If it works fine for you, please let us know and file a bug on <uri 370If it works fine for you, please let us know and file a bug on <uri
414link="http://bugs.gentoo.org/">Gentoo's Bugzilla</uri>, so that the AMD64 team 371link="http://bugs.gentoo.org/">Gentoo's Bugzilla</uri>, so that the AMD64 team
415can keyword the package and other users can benefit from your test. 372can keyword the package and other users can benefit from your test.
416</p> 373</p>
417 374
418<warn> 375<warn>
419Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It 376Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It
420will most certainly break your tree. 377will most certainly break your tree.
421</warn> 378</warn>
422 379
423</body> 380</body>
424</section> 381</section>
425</chapter> 382</chapter>
426 383
427<chapter> 384<chapter>
428<title>How can I help the Gentoo/AMD64 project?</title> 385<title>How can I help the Gentoo/AMD64 project?</title>
429<section id="bugs">
430<title>How do I report bugs?</title>
431<body>
432
433<p>
434If you find a bug or you want to send us patches, you need to file a bug
435report. It only takes you a little while, and your help is really appreciated.
436Please follow the <uri
437link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">Filing a Bug
438Guide</uri>.
439</p>
440
441</body>
442</section>
443<section id="project"> 386<section id="project">
444<title>How can I help?</title> 387<title>How can I help?</title>
445<body> 388<body>
446 389
447<p> 390<p>
452 395
453<ul> 396<ul>
454 <li>Filing general bug reports</li> 397 <li>Filing general bug reports</li>
455 <li>Testing software that does not yet have the <c>~amd64</c> keyword</li> 398 <li>Testing software that does not yet have the <c>~amd64</c> keyword</li>
456 <li> 399 <li>
457 Participating in the <uri 400 Participating in the <uri link="/proj/en/base/amd64/at/">Arch Testers
458 link="/proj/en/base/amd64/at/index.xml">Arch Testers
459 project</uri> 401 project</uri>
460 </li> 402 </li>
461 <li> 403 <li>
462 Help answering questions on the mailing lists, forums and IRC channels 404 Help answering questions on the mailing lists, forums and IRC channels
463 </li> 405 </li>
473<section id="other"> 415<section id="other">
474<title>Where can I get more help or information about Gentoo/AMD64?</title> 416<title>Where can I get more help or information about Gentoo/AMD64?</title>
475<body> 417<body>
476 418
477<p> 419<p>
478If any of your questions wasn't answered here, you can try other resources listed on 420If any of your questions wasn't answered here, you can try other resources
479<uri link="/proj/en/base/amd64/index.xml">our project homepage</uri>. You can 421listed on <uri link="/proj/en/base/amd64/">our project homepage</uri>. You can
480also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri 422also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri
481link="http://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>, 423link="http://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>,
482or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list. 424or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list.
483</p> 425</p>
484 426

Legend:
Removed from v.1.21  
changed lines
  Added in v.1.22

  ViewVC Help
Powered by ViewVC 1.1.20