From: "Xavier Neys" <neysx@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-amd64-faq.xml
Date: Wed, 25 Oct 2006 12:54:26 +0000 [thread overview]
Message-ID: <20061025125426.906E764A3D@smtp.gentoo.org> (raw)
neysx 06/10/25 12:54:26
Modified: gentoo-amd64-faq.xml
Log:
#152771 revamped AMD64 FAQ
Revision Changes Path
1.22 xml/htdocs/doc/en/gentoo-amd64-faq.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.22&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.22&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml?r1=1.21&r2=1.22
Index: gentoo-amd64-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- gentoo-amd64-faq.xml 6 Oct 2006 22:01:53 -0000 1.21
+++ gentoo-amd64-faq.xml 25 Oct 2006 12:54:26 -0000 1.22
@@ -1,18 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.21 2006/10/06 22:01:53 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.22 2006/10/25 12:54:26 neysx Exp $ -->
<guide link="/doc/en/gentoo-amd64-faq.xml">
<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
<author title="Editor">
- <mail link="metalgod@gentoo.org">Luis Medinas</mail>
+ <mail link="blubb@gentoo.org">Simon Stelling</mail>
</author>
<author title="Editor">
- <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
+ <mail link="metalgod@gentoo.org">Luis Medinas</mail>
</author>
<author title="Editor">
- <mail link="blubb@gentoo.org">Simon Stelling</mail>
+ <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
</author>
<author title="Editor">
<mail link="neysx@gentoo.org">Xavier Neys</mail>
@@ -26,8 +26,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.15</version>
-<date>2006-10-06</date>
+<version>1.16</version>
+<date>2006-10-25</date>
<chapter>
<title>Questions</title>
@@ -38,9 +38,9 @@
<p>
This document contains the most commonly asked questions about Gentoo/AMD64. We
intend to help and provide useful information about Gentoo/AMD64. Some of these
-questions can be found in forums, IRC, or mailing lists. If you have suggestions
-or questions about this FAQ, you are welcome to send an e-mail to the authors
-explaining the problem.
+questions can be found in forums, IRC, or mailing lists. If you have
+suggestions or questions about this FAQ, you are welcome to send an e-mail to
+<mail>amd64@gentoo.org</mail>.
</p>
</body>
@@ -56,9 +56,6 @@
<uri link="#perfup">Will I have a performance upgrade if I use a 64-bit
system instead of 32-bit?</uri>
</li>
- <li>
- <uri link="#emul32">How do I get 32-bit emulation for my system?</uri>
- </li>
<li><uri link="#multilib">What is multilib and how can I use it?</uri></li>
<li><uri link="#chroot32">How do I create a 32-bit chroot?</uri></li>
<li>
@@ -92,7 +89,6 @@
<ul>
<li><uri link="#flash">Can I get Macromedia Flash working?</uri></li>
<li><uri link="#OOo">Can I get OpenOffice.org working?</uri></li>
- <li><uri link="#java">How do I get java working in my browser?</uri></li>
<li>
<uri link="#masked">I want to install package foo, but emerge says: (masked
by: ~amd64 keyword)</uri>
@@ -110,7 +106,6 @@
<body>
<ul>
- <li><uri link="#bugs">How do I report bugs?</uri></li>
<li><uri link="#project">How can I help?</uri></li>
</ul>
@@ -139,24 +134,10 @@
<p>
You should use simple <c>CFLAGS</c> to avoid future problems with your system.
-For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or
-Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for an EM64T processor. If
-you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp -O2
--pipe -msse2"</c> for an AMD64 processor; for an EM64T, you should use
-<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>.
+Supported <c>CFLAGS</c> are <c>-O2 -march=k8 -pipe</c> for non-EM64T systems and
+<c>-O2 -march=nocona -pipe</c> for EM64T systems.
</p>
-<note>
-<c>-march=k8</c> is the same as <c>-march=athlon64</c> and
-<c>-march=opteron</c>.
-</note>
-
-<warn>
-You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in
-your <c>CFLAGS</c>. They are automatically added whenever they are needed.
-Please also note that the <c>-Os</c> flag is currently not supported.
-</warn>
-
</body>
</section>
<section id="kernel">
@@ -167,9 +148,7 @@
You can use almost all kernel sources available in Portage. We recommend using
<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
It contains lots of AMD64-specific patches and therefore is the only kernel
-officially supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as
-well. If you feel brave or you need extra hardware support, you can always try
-the experimental kernel from Andrew Morton called <c>mm-sources</c>.
+officially supported by Gentoo/AMD64.
</p>
<warn>
@@ -177,6 +156,23 @@
as <c>PREEMPT</c>.
</warn>
+<p>
+Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel.
+</p>
+
+<pre caption="Activating IA32 Emulation in Kernel source">
+# <i>cd /usr/src/linux</i>
+# <i>make menuconfig</i>
+
+Executable file formats / Emulations --->
+ [*] IA32 Emulation
+</pre>
+
+<warn>
+You may experience build failures on multilib-systems if you deactivate this
+option.
+</warn>
+
</body>
</section>
<section id="perfup">
@@ -197,36 +193,6 @@
</body>
</section>
-<section id="emul32">
-<title>How do I get 32-bit emulation for my system?</title>
-<body>
-
-<p>
-You have to install a few packages to get 32-bit libraries into your system.
-These packages are automatically pulled in as dependencies for 32-bit
-applications by Portage, so there is no need to manually emerge them. You can
-install such packages by doing:
-</p>
-
-<pre caption="Installing 32-bit libraries">
-# <i>emerge emul-linux-x86-baselibs</i>
-# <i>emerge emul-linux-x86-compat</i>
-</pre>
-
-<p>
-Furthermore, you need the <c>IA32_EMULATION</c> option activated in the kernel.
-</p>
-
-<pre caption="Activating IA32 Emulation in Kernel source">
-# <i>cd /usr/src/linux</i>
-# <i>make menuconfig</i>
-
-Executable file formats / Emulations --->
- [*] IA32 Emulation
-</pre>
-
-</body>
-</section>
<section id="multilib">
<title>What is multilib and how can I use it?</title>
<body>
@@ -240,6 +206,11 @@
according profile. The default is a multilib-enabled profile.
</p>
+<warn>
+Currently you cannot switch from a no-multilib to a multilib-enabled profile,
+so think over your decision twice before you use the no-multilib profile.
+</warn>
+
</body>
</section>
<section id="chroot32">
@@ -247,8 +218,7 @@
<body>
<p>
-Please read the <uri
-link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=2">32-bit chroot
+Please read the <uri link="/proj/en/base/amd64/howtos/chroot.xml">32-bit chroot
guide</uri>.
</p>
@@ -344,9 +314,9 @@
<body>
<p>
-Yes. To get Flash working, you need a 32-bit browser like <c>mozilla-bin</c>,
+Yes. To get Flash working, you need a 32-bit browser like
<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
-64-bit version. After emerging the -bin-package of your favorite browser,
+64-bit version. After emerging the -bin package of your favorite browser,
install Flash by doing <c>emerge netscape-flash</c>.
</p>
@@ -357,27 +327,14 @@
<body>
<p>
-OpenOffice 1.x and 2.0.x do not build on 64-bit systems, so you have to use the
-32-bit binary version, available in Portage as <c>openoffice-bin</c>.
+OpenOffice versions prior to 2.0.4 do not build on 64-bit systems, so you have to use the
+32-bit binary version, available in Portage as <c>app-office/openoffice-bin</c>.
+If you feel brave you can <c>emerge openoffice</c>, but be aware that the 64-bit version
+is not yet tested out enough to be considered stable.
</p>
</body>
</section>
-<section id="java">
-<title>How do I get java working in my browser?</title>
-<body>
-
-<p>
-Blackdown provides a 64-bit JRE. To install it, <c>emerge blackdown-jre</c>.
-Then, perform the following step:
-</p>
-
-<pre caption="Example of java link to browser plugins">
-# <i>ln -s /opt/blackdown-jre-*/plugin/amd64/mozilla/libjavaplugin_oji.so /usr/lib64/nsbrowser/plugins/libjavaplugin_oji.so</i>
-</pre>
-
-</body>
-</section>
<section id="masked">
<title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title>
<body>
@@ -401,11 +358,11 @@
This means that the package has not been tested yet. It does <e>not
necessarily</e> mean that the package does not work. You can unmask it by
accepting another architecture for the package. The following example shows you
-can tell Portage to accept the ~x86 keyword for a given package.
+can tell Portage to accept any keyword for a given package.
</p>
<pre caption="Example of adding package keywords">
-# <i>echo "category/packagename ~x86" >> /etc/portage/package.keywords</i>
+# <i>echo "category/packagename ~* *" >> /etc/portage/package.keywords</i>
# <i>emerge packagename</i>
</pre>
@@ -416,7 +373,7 @@
</p>
<warn>
-Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It
+Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It
will most certainly break your tree.
</warn>
@@ -426,20 +383,6 @@
<chapter>
<title>How can I help the Gentoo/AMD64 project?</title>
-<section id="bugs">
-<title>How do I report bugs?</title>
-<body>
-
-<p>
-If you find a bug or you want to send us patches, you need to file a bug
-report. It only takes you a little while, and your help is really appreciated.
-Please follow the <uri
-link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=1">Filing a Bug
-Guide</uri>.
-</p>
-
-</body>
-</section>
<section id="project">
<title>How can I help?</title>
<body>
@@ -454,8 +397,7 @@
<li>Filing general bug reports</li>
<li>Testing software that does not yet have the <c>~amd64</c> keyword</li>
<li>
- Participating in the <uri
- link="/proj/en/base/amd64/at/index.xml">Arch Testers
+ Participating in the <uri link="/proj/en/base/amd64/at/">Arch Testers
project</uri>
</li>
<li>
@@ -475,8 +417,8 @@
<body>
<p>
-If any of your questions wasn't answered here, you can try other resources listed on
-<uri link="/proj/en/base/amd64/index.xml">our project homepage</uri>. You can
+If any of your questions wasn't answered here, you can try other resources
+listed on <uri link="/proj/en/base/amd64/">our project homepage</uri>. You can
also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri
link="http://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>,
or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list.
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2006-10-25 12:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 12:54 Xavier Neys [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 19:46 [gentoo-doc-cvs] cvs commit: gentoo-amd64-faq.xml Joshua Saddler
2008-09-02 7:47 Joshua Saddler
2008-07-25 18:55 Joshua Saddler
2008-05-21 20:10 Sven Vermeulen
2006-11-24 14:47 Josh Saddler
2006-10-06 22:01 Josh Saddler
2006-10-05 0:00 Josh Saddler
2006-10-04 14:23 Xavier Neys
2006-09-18 8:25 Josh Saddler
2006-09-18 6:53 Josh Saddler
2006-06-17 7:04 Shyam Mani
2006-03-28 10:20 Xavier Neys
2006-03-19 22:26 Jan Kundrat
2006-02-26 13:56 Xavier Neys
2006-02-17 18:48 Shyam Mani
2006-02-11 14:22 swift
2006-02-01 9:45 Shyam Mani
2005-12-13 12:17 Xavier Neys
2005-11-23 18:06 Xavier Neys
2005-10-31 13:31 Xavier Neys
2005-09-20 9:13 Lukasz Damentko
2005-09-19 21:50 Lukasz Damentko
2005-08-07 11:15 Alin Dobre
2005-07-16 15:14 Jonathan Smith
2005-07-16 15:08 Jonathan Smith
2005-07-16 9:44 Xavier Neys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061025125426.906E764A3D@smtp.gentoo.org \
--to=neysx@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox