| 1 |
neysx 06/10/25 12:54:26 |
| 2 |
|
| 3 |
Modified: gentoo-amd64-faq.xml |
| 4 |
Log: |
| 5 |
#152771 revamped AMD64 FAQ |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.22 xml/htdocs/doc/en/gentoo-amd64-faq.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.22&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.22&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?r1=1.21&r2=1.22 |
| 13 |
|
| 14 |
Index: gentoo-amd64-faq.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v |
| 17 |
retrieving revision 1.21 |
| 18 |
retrieving revision 1.22 |
| 19 |
diff -u -r1.21 -r1.22 |
| 20 |
--- gentoo-amd64-faq.xml 6 Oct 2006 22:01:53 -0000 1.21 |
| 21 |
+++ gentoo-amd64-faq.xml 25 Oct 2006 12:54:26 -0000 1.22 |
| 22 |
@@ -1,18 +1,18 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.21 2006/10/06 22:01:53 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.22 2006/10/25 12:54:26 neysx Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/gentoo-amd64-faq.xml"> |
| 29 |
<title>Gentoo Linux/AMD64 Frequently Asked Questions</title> |
| 30 |
|
| 31 |
<author title="Editor"> |
| 32 |
- <mail link="metalgod@g.o">Luis Medinas</mail> |
| 33 |
+ <mail link="blubb@g.o">Simon Stelling</mail> |
| 34 |
</author> |
| 35 |
<author title="Editor"> |
| 36 |
- <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 37 |
+ <mail link="metalgod@g.o">Luis Medinas</mail> |
| 38 |
</author> |
| 39 |
<author title="Editor"> |
| 40 |
- <mail link="blubb@g.o">Simon Stelling</mail> |
| 41 |
+ <mail link="gerrynjr@g.o">Gerald J. Normandin Jr.</mail> |
| 42 |
</author> |
| 43 |
<author title="Editor"> |
| 44 |
<mail link="neysx@g.o">Xavier Neys</mail> |
| 45 |
@@ -26,8 +26,8 @@ |
| 46 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 47 |
<license/> |
| 48 |
|
| 49 |
-<version>1.15</version> |
| 50 |
-<date>2006-10-06</date> |
| 51 |
+<version>1.16</version> |
| 52 |
+<date>2006-10-25</date> |
| 53 |
|
| 54 |
<chapter> |
| 55 |
<title>Questions</title> |
| 56 |
@@ -38,9 +38,9 @@ |
| 57 |
<p> |
| 58 |
This document contains the most commonly asked questions about Gentoo/AMD64. We |
| 59 |
intend to help and provide useful information about Gentoo/AMD64. Some of these |
| 60 |
-questions can be found in forums, IRC, or mailing lists. If you have suggestions |
| 61 |
-or questions about this FAQ, you are welcome to send an e-mail to the authors |
| 62 |
-explaining the problem. |
| 63 |
+questions can be found in forums, IRC, or mailing lists. If you have |
| 64 |
+suggestions or questions about this FAQ, you are welcome to send an e-mail to |
| 65 |
+<mail>amd64@g.o</mail>. |
| 66 |
</p> |
| 67 |
|
| 68 |
</body> |
| 69 |
@@ -56,9 +56,6 @@ |
| 70 |
<uri link="#perfup">Will I have a performance upgrade if I use a 64-bit |
| 71 |
system instead of 32-bit?</uri> |
| 72 |
</li> |
| 73 |
- <li> |
| 74 |
- <uri link="#emul32">How do I get 32-bit emulation for my system?</uri> |
| 75 |
- </li> |
| 76 |
<li><uri link="#multilib">What is multilib and how can I use it?</uri></li> |
| 77 |
<li><uri link="#chroot32">How do I create a 32-bit chroot?</uri></li> |
| 78 |
<li> |
| 79 |
@@ -92,7 +89,6 @@ |
| 80 |
<ul> |
| 81 |
<li><uri link="#flash">Can I get Macromedia Flash working?</uri></li> |
| 82 |
<li><uri link="#OOo">Can I get OpenOffice.org working?</uri></li> |
| 83 |
- <li><uri link="#java">How do I get java working in my browser?</uri></li> |
| 84 |
<li> |
| 85 |
<uri link="#masked">I want to install package foo, but emerge says: (masked |
| 86 |
by: ~amd64 keyword)</uri> |
| 87 |
@@ -110,7 +106,6 @@ |
| 88 |
<body> |
| 89 |
|
| 90 |
<ul> |
| 91 |
- <li><uri link="#bugs">How do I report bugs?</uri></li> |
| 92 |
<li><uri link="#project">How can I help?</uri></li> |
| 93 |
</ul> |
| 94 |
|
| 95 |
@@ -139,24 +134,10 @@ |
| 96 |
|
| 97 |
<p> |
| 98 |
You should use simple <c>CFLAGS</c> to avoid future problems with your system. |
| 99 |
-For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or |
| 100 |
-Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for an EM64T processor. If |
| 101 |
-you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp -O2 |
| 102 |
--pipe -msse2"</c> for an AMD64 processor; for an EM64T, you should use |
| 103 |
-<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>. |
| 104 |
+Supported <c>CFLAGS</c> are <c>-O2 -march=k8 -pipe</c> for non-EM64T systems and |
| 105 |
+<c>-O2 -march=nocona -pipe</c> for EM64T systems. |
| 106 |
</p> |
| 107 |
|
| 108 |
-<note> |
| 109 |
-<c>-march=k8</c> is the same as <c>-march=athlon64</c> and |
| 110 |
-<c>-march=opteron</c>. |
| 111 |
-</note> |
| 112 |
- |
| 113 |
-<warn> |
| 114 |
-You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in |
| 115 |
-your <c>CFLAGS</c>. They are automatically added whenever they are needed. |
| 116 |
-Please also note that the <c>-Os</c> flag is currently not supported. |
| 117 |
-</warn> |
| 118 |
- |
| 119 |
</body> |
| 120 |
</section> |
| 121 |
<section id="kernel"> |
| 122 |
@@ -167,9 +148,7 @@ |
| 123 |
You can use almost all kernel sources available in Portage. We recommend using |
| 124 |
<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux. |
| 125 |
It contains lots of AMD64-specific patches and therefore is the only kernel |
| 126 |
-officially supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as |
| 127 |
-well. If you feel brave or you need extra hardware support, you can always try |
| 128 |
-the experimental kernel from Andrew Morton called <c>mm-sources</c>. |
| 129 |
+officially supported by Gentoo/AMD64. |
| 130 |
</p> |
| 131 |
|
| 132 |
<warn> |
| 133 |
@@ -177,6 +156,23 @@ |
| 134 |
as <c>PREEMPT</c>. |
| 135 |
</warn> |
| 136 |
|
| 137 |
+<p> |
| 138 |
+Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel. |
| 139 |
+</p> |
| 140 |
+ |
| 141 |
+<pre caption="Activating IA32 Emulation in Kernel source"> |
| 142 |
+# <i>cd /usr/src/linux</i> |
| 143 |
+# <i>make menuconfig</i> |
| 144 |
+ |
| 145 |
+Executable file formats / Emulations ---> |
| 146 |
+ [*] IA32 Emulation |
| 147 |
+</pre> |
| 148 |
+ |
| 149 |
+<warn> |
| 150 |
+You may experience build failures on multilib-systems if you deactivate this |
| 151 |
+option. |
| 152 |
+</warn> |
| 153 |
+ |
| 154 |
</body> |
| 155 |
</section> |
| 156 |
<section id="perfup"> |
| 157 |
@@ -197,36 +193,6 @@ |
| 158 |
|
| 159 |
</body> |
| 160 |
</section> |
| 161 |
-<section id="emul32"> |
| 162 |
-<title>How do I get 32-bit emulation for my system?</title> |
| 163 |
-<body> |
| 164 |
- |
| 165 |
-<p> |
| 166 |
-You have to install a few packages to get 32-bit libraries into your system. |
| 167 |
-These packages are automatically pulled in as dependencies for 32-bit |
| 168 |
-applications by Portage, so there is no need to manually emerge them. You can |
| 169 |
-install such packages by doing: |
| 170 |
-</p> |
| 171 |
- |
| 172 |
-<pre caption="Installing 32-bit libraries"> |
| 173 |
-# <i>emerge emul-linux-x86-baselibs</i> |
| 174 |
-# <i>emerge emul-linux-x86-compat</i> |
| 175 |
-</pre> |
| 176 |
- |
| 177 |
-<p> |
| 178 |
-Furthermore, you need the <c>IA32_EMULATION</c> option activated in the kernel. |
| 179 |
-</p> |
| 180 |
- |
| 181 |
-<pre caption="Activating IA32 Emulation in Kernel source"> |
| 182 |
-# <i>cd /usr/src/linux</i> |
| 183 |
-# <i>make menuconfig</i> |
| 184 |
- |
| 185 |
-Executable file formats / Emulations ---> |
| 186 |
- [*] IA32 Emulation |
| 187 |
-</pre> |
| 188 |
- |
| 189 |
-</body> |
| 190 |
-</section> |
| 191 |
<section id="multilib"> |
| 192 |
<title>What is multilib and how can I use it?</title> |
| 193 |
<body> |
| 194 |
@@ -240,6 +206,11 @@ |
| 195 |
according profile. The default is a multilib-enabled profile. |
| 196 |
</p> |
| 197 |
|
| 198 |
+<warn> |
| 199 |
+Currently you cannot switch from a no-multilib to a multilib-enabled profile, |
| 200 |
+so think over your decision twice before you use the no-multilib profile. |
| 201 |
+</warn> |
| 202 |
+ |
| 203 |
</body> |
| 204 |
</section> |
| 205 |
<section id="chroot32"> |
| 206 |
@@ -247,8 +218,7 @@ |
| 207 |
<body> |
| 208 |
|
| 209 |
<p> |
| 210 |
-Please read the <uri |
| 211 |
-link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=2">32-bit chroot |
| 212 |
+Please read the <uri link="/proj/en/base/amd64/howtos/chroot.xml">32-bit chroot |
| 213 |
guide</uri>. |
| 214 |
</p> |
| 215 |
|
| 216 |
@@ -344,9 +314,9 @@ |
| 217 |
<body> |
| 218 |
|
| 219 |
<p> |
| 220 |
-Yes. To get Flash working, you need a 32-bit browser like <c>mozilla-bin</c>, |
| 221 |
+Yes. To get Flash working, you need a 32-bit browser like |
| 222 |
<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a |
| 223 |
-64-bit version. After emerging the -bin-package of your favorite browser, |
| 224 |
+64-bit version. After emerging the -bin package of your favorite browser, |
| 225 |
install Flash by doing <c>emerge netscape-flash</c>. |
| 226 |
</p> |
| 227 |
|
| 228 |
@@ -357,27 +327,14 @@ |
| 229 |
<body> |
| 230 |
|
| 231 |
<p> |
| 232 |
-OpenOffice 1.x and 2.0.x do not build on 64-bit systems, so you have to use the |
| 233 |
-32-bit binary version, available in Portage as <c>openoffice-bin</c>. |
| 234 |
+OpenOffice versions prior to 2.0.4 do not build on 64-bit systems, so you have to use the |
| 235 |
+32-bit binary version, available in Portage as <c>app-office/openoffice-bin</c>. |
| 236 |
+If you feel brave you can <c>emerge openoffice</c>, but be aware that the 64-bit version |
| 237 |
+is not yet tested out enough to be considered stable. |
| 238 |
</p> |
| 239 |
|
| 240 |
</body> |
| 241 |
</section> |
| 242 |
-<section id="java"> |
| 243 |
-<title>How do I get java working in my browser?</title> |
| 244 |
-<body> |
| 245 |
- |
| 246 |
-<p> |
| 247 |
-Blackdown provides a 64-bit JRE. To install it, <c>emerge blackdown-jre</c>. |
| 248 |
-Then, perform the following step: |
| 249 |
-</p> |
| 250 |
- |
| 251 |
-<pre caption="Example of java link to browser plugins"> |
| 252 |
-# <i>ln -s /opt/blackdown-jre-*/plugin/amd64/mozilla/libjavaplugin_oji.so /usr/lib64/nsbrowser/plugins/libjavaplugin_oji.so</i> |
| 253 |
-</pre> |
| 254 |
- |
| 255 |
-</body> |
| 256 |
-</section> |
| 257 |
<section id="masked"> |
| 258 |
<title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title> |
| 259 |
<body> |
| 260 |
@@ -401,11 +358,11 @@ |
| 261 |
This means that the package has not been tested yet. It does <e>not |
| 262 |
necessarily</e> mean that the package does not work. You can unmask it by |
| 263 |
accepting another architecture for the package. The following example shows you |
| 264 |
-can tell Portage to accept the ~x86 keyword for a given package. |
| 265 |
+can tell Portage to accept any keyword for a given package. |
| 266 |
</p> |
| 267 |
|
| 268 |
<pre caption="Example of adding package keywords"> |
| 269 |
-# <i>echo "category/packagename ~x86" >> /etc/portage/package.keywords</i> |
| 270 |
+# <i>echo "category/packagename ~* *" >> /etc/portage/package.keywords</i> |
| 271 |
# <i>emerge packagename</i> |
| 272 |
</pre> |
| 273 |
|
| 274 |
@@ -416,7 +373,7 @@ |
| 275 |
</p> |
| 276 |
|
| 277 |
<warn> |
| 278 |
-Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It |
| 279 |
+Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It |
| 280 |
will most certainly break your tree. |
| 281 |
</warn> |
| 282 |
|
| 283 |
@@ -426,20 +383,6 @@ |
| 284 |
|
| 285 |
<chapter> |
| 286 |
<title>How can I help the Gentoo/AMD64 project?</title> |
| 287 |
-<section id="bugs"> |
| 288 |
-<title>How do I report bugs?</title> |
| 289 |
-<body> |
| 290 |
- |
| 291 |
-<p> |
| 292 |
-If you find a bug or you want to send us patches, you need to file a bug |
| 293 |
-report. It only takes you a little while, and your help is really appreciated. |
| 294 |
-Please follow the <uri |
| 295 |
-link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=1">Filing a Bug |
| 296 |
-Guide</uri>. |
| 297 |
-</p> |
| 298 |
- |
| 299 |
-</body> |
| 300 |
-</section> |
| 301 |
<section id="project"> |
| 302 |
<title>How can I help?</title> |
| 303 |
<body> |
| 304 |
@@ -454,8 +397,7 @@ |
| 305 |
<li>Filing general bug reports</li> |
| 306 |
<li>Testing software that does not yet have the <c>~amd64</c> keyword</li> |
| 307 |
<li> |
| 308 |
- Participating in the <uri |
| 309 |
- link="/proj/en/base/amd64/at/index.xml">Arch Testers |
| 310 |
+ Participating in the <uri link="/proj/en/base/amd64/at/">Arch Testers |
| 311 |
project</uri> |
| 312 |
</li> |
| 313 |
<li> |
| 314 |
@@ -475,8 +417,8 @@ |
| 315 |
<body> |
| 316 |
|
| 317 |
<p> |
| 318 |
-If any of your questions wasn't answered here, you can try other resources listed on |
| 319 |
-<uri link="/proj/en/base/amd64/index.xml">our project homepage</uri>. You can |
| 320 |
+If any of your questions wasn't answered here, you can try other resources |
| 321 |
+listed on <uri link="/proj/en/base/amd64/">our project homepage</uri>. You can |
| 322 |
also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri |
| 323 |
link="http://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>, |
| 324 |
or on the <c>gentoo-amd64@l.g.o</c> mailing list. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
-- |
| 329 |
gentoo-doc-cvs@g.o mailing list |
Archives