From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2
Date: Mon, 25 Jul 2005 04:09:32 +0200 [thread overview]
Message-ID: <42E449DC.1080307@planet.nl> (raw)
In-Reply-To: <20050723170853.GB23955@nexon>
Patrick Börjesson schreef:
> On 05/07/23 18:37, Richard Fish wrote:
>
>>>>And it seems to me that if there is a bug, it might be a *documentation*
>>>>bug (because the other person who mentioned using march=k8 said that
>>>>that was the recommendation of the docs, but that seems to no longer be
>>>>the case, if people using this flag are regularly receiving compilation
>>>>errors).
>>>>
>>>
>>>Documentation bug? Not recommended by the docs any more?
>>>You might want to actually try to find information about the subjects
>>>you respond to.
>>>
>>>Straight out of the AMD64 Gentoo Handbook:
>>>"AMD64 users who want to use a native 64 bit system should use
>>>-march=k8"
>>>Combining that cite with the information from the gcc info page, I'm
>>>pretty sure it's not a "documentation bug".
>>>
>>>
>>>
>>
>>Hold on...the -march thing would be an easy mistake to make for those of
>>us who don't run AMD processors, and are just trying to help. Afterall,
>>the platform keyword is "amd64". And gcc info says that k8, opteron,
>>athlon64, and athlon-fx are all equivalent, although I would suggest
>>that the non-k8 options are more descriptive.
>
>
> Of course, but in this case it wasn't an oversight... The poster
> explicitly said that using march=k8 seemed to no longer be the
> recommendation of the docs. That implies at least _some_ looking into
> the subject before posting...
>
If the poster being referred to is me, that wasn't what I meant to say,
or rather what I meant to be *understood*-- what I meant was that
apparently the Handbook recommends using the k8 flag, but people using
that flag seem (and I stress "seem", as I don't follow this issue that
closely, naturally) to be running into problems, whereas those using the
amd64 flag are not (or at least not the same problems).
Now, I don't know the truth of the matter, but that would lead me to
suspect that there could be *outdated information in the Gentoo
documentation* (thus, a "documentation bug"), which, if those affected
can verify, should perhaps be submitted.
Sorry for the confusion.
Holly
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-25 2:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 11:38 [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Jules Colding
2005-07-23 12:36 ` Patrick Börjesson
2005-07-23 12:50 ` Holly Bostick
2005-07-23 13:14 ` Jules Colding
2005-07-23 15:51 ` Patrick Börjesson
2005-07-23 16:37 ` Richard Fish
2005-07-23 17:08 ` Patrick Börjesson
2005-07-23 18:19 ` Richard Fish
2005-07-23 23:02 ` Patrick Börjesson
2005-07-24 12:43 ` Jules Colding
2005-07-25 2:09 ` Holly Bostick [this message]
2005-07-23 18:38 ` neil
2005-07-24 17:23 ` Neil Bothwick
2005-07-23 18:46 ` Bob Sanders
2005-07-23 18:51 ` Zac Medico
2005-07-23 21:26 ` Richard Fish
2005-07-24 12:28 ` Jules Colding
2005-07-24 11:07 ` Jules Colding
2005-07-24 13:20 ` Richard Fish
2005-07-24 13:28 ` Jules Colding
2005-07-24 13:51 ` Richard Fish
2005-07-24 13:57 ` Jules Colding
2005-07-24 13:58 ` Richard Fish
2005-07-24 14:27 ` Jules Colding
2005-07-24 14:43 ` Rumen Yotov
2005-07-24 14:47 ` Jules Colding
2005-07-24 15:06 ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 (AMD64 users please help) Richard Fish
2005-07-24 15:12 ` Jules Colding
2005-07-24 18:10 ` Bob Sanders
2005-07-24 18:59 ` Jules Colding
2005-07-24 19:14 ` Richard Fish
2005-07-26 1:37 ` Bob Sanders
2005-07-24 14:00 ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Zac Medico
2005-07-24 15:29 ` neil
2005-07-24 12:22 ` Jules Colding
2005-07-24 12:38 ` Jules Colding
2005-07-24 12:48 ` Richard Fish
2005-07-24 13:10 ` Jules Colding
2005-07-24 13:30 ` Richard Fish
2005-07-24 13:28 ` Rumen Yotov
2005-07-24 13:35 ` Jules Colding
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=42E449DC.1080307@planet.nl \
--to=motub@planet.nl \
--cc=gentoo-user@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