From: neil <neil@ep.mine.nu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2
Date: Sat, 23 Jul 2005 19:38:06 +0100 [thread overview]
Message-ID: <42E28E8E.1040208@ep.mine.nu> (raw)
In-Reply-To: <42E23D20.3000802@planet.nl>
Holly Bostick wrote:
> Well, since I just (literally, 10 minutes ago) emerged
> mozilla-firefox-1.0.6-r2, and had no problems on a 32-bit system, I must
> suspect that this is a 64-bit issue.
Nope. I emerged both firefox and thunderbird without issue on my AMD64
4000+ about 14 hours ago.
> In that regard, I see at least one thing in your emerge info that has
> been called into question for 64-bit users in recent threads:
>
> CFLAGS="-march=k8
I use k8. k8, opteron, etc., etc. are supposed to be synonyms as I
understand it. k8 is the preferred one according to most sources I have
read but, if they are truly synonyms, I'm not sure why one should be
preferred over another.
> Oh, and despite what Patrick said, I think you were right to post here
> first-- no need to clog up b.g.o with what might be a configuration
> problem and waste developer's time closing an invalid bug.
>
> I think it's always wise to try to make sure that it really is a bug
> before posting it.
Quite right. I doubt that it is a bug - more likely a broken system in
some way.
> 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
No errors here. :)
Be lucky,
Neil
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-23 18:45 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
2005-07-23 18:38 ` neil [this message]
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=42E28E8E.1040208@ep.mine.nu \
--to=neil@ep.mine.nu \
--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