From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DwMOM-00037s-OO for garchives@archives.gentoo.org; Sat, 23 Jul 2005 15:58:23 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6NFuJ2K023756; Sat, 23 Jul 2005 15:56:19 GMT Received: from nexon.borjesson.homedns.org (h160n5c1o1031.bredband.skanova.com [217.209.226.160]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6NFpHXk016586 for ; Sat, 23 Jul 2005 15:51:17 GMT Received: by nexon.borjesson.homedns.org (Postfix, from userid 1000) id 1A70F67CE3; Sat, 23 Jul 2005 17:51:55 +0200 (CEST) Date: Sat, 23 Jul 2005 17:51:55 +0200 From: Patrick =?iso-8859-1?Q?B=F6rjesson?= To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Message-ID: <20050723155155.GA23955@nexon> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <1122118718.3489.3.camel@omc-2.omesc.com> <42E23D20.3000802@planet.nl> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: <42E23D20.3000802@planet.nl> User-Agent: Mutt/1.5.8i X-Archives-Salt: 41592f45-49c6-4ef7-ac55-e3407e3c4ca0 X-Archives-Hash: 98f174a90e9eadb1ac125938edca81fc --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05/07/23 14:50, Holly Bostick wrote: > Jules Colding schreef: > > "emerge --sync && emerge -vauDN" today gave me the following error. > >=20 [snip] >=20 > 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. >=20 > 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: >=20 > CFLAGS=3D"-march=3Dk8 >=20 > I am, of course, not a 64-bit user, so I don't know anything about this, > but I have seen several responses to similar questions that suggest that > the correct flag is >=20 > march=3Damd64 Looking at gcc's info page, there is no amd64 target. The only ones I can find that seems reasonable are k8 and athlon64. I use k8 myself and haven't had _any_ problems with it.=20 > 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 really don't see how this could be a configuration problem, since it would have complained about an erroneous compilation flag if it was the k8 thing that was at fault... And missing files (which the compilation error points at) sounds pretty much like a valid bug to me... > I think it's always wise to try to make sure that it really is a bug > before posting it. Of course, but looking at the ordinary response from developers to these kind of emails, I'd guess that b.g.o is where they want the report, not here... > 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=3Dk8 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?=20 You might want to actually try to find information about the subjects you respond to.=20 Straight out of the AMD64 Gentoo Handbook: "AMD64 users who want to use a native 64 bit system should use -march=3Dk8" Combining that cite with the information from the gcc info page, I'm pretty sure it's not a "documentation bug".=20 --=20 Regards, Patrick B=F6rjesson PGP signature: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0x2179= 2A5D PGP fingerprint: 74AF D4EF 6BDE CF77 16BE 6A29 CDB8 7607 2179 2A5D --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC4mebzbh2ByF5Kl0RAsaHAJ9+qDkeSpIEirpUaJLP5rsNFvJYvgCfW00C WlQjdVzTGZkYDZ7Nlru3tdo= =APjf -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- -- gentoo-user@gentoo.org mailing list