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 1DwOgV-0005Ma-Ce for garchives@archives.gentoo.org; Sat, 23 Jul 2005 18:25:15 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6NINFaM001158; Sat, 23 Jul 2005 18:23:15 GMT Received: from smtp107.mail.sc5.yahoo.com (smtp107.mail.sc5.yahoo.com [66.163.169.227]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6NIGKQJ024835 for ; Sat, 23 Jul 2005 18:16:21 GMT Received: (qmail 87944 invoked from network); 23 Jul 2005 18:17:01 -0000 Received: from unknown (HELO ?192.168.50.105?) (richard?j?fish@212.180.33.26 with plain) by smtp107.mail.sc5.yahoo.com with SMTP; 23 Jul 2005 18:17:01 -0000 Message-ID: <42E28A4D.1020707@asmallpond.org> Date: Sat, 23 Jul 2005 20:19:57 +0200 From: Richard Fish User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 References: <1122118718.3489.3.camel@omc-2.omesc.com> <42E23D20.3000802@planet.nl> <20050723155155.GA23955@nexon> <42E27234.9020002@asmallpond.org> <20050723170853.GB23955@nexon> In-Reply-To: <20050723170853.GB23955@nexon> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id j6NINFad001158 X-Archives-Salt: 2f6c1eb0-8426-4447-be82-1a68de058822 X-Archives-Hash: 1a3b465a92007e661dfd66eab1aa4f43 Patrick B=F6rjesson wrote: > When did I say that it wasn't frequent with configuration problems > leading to failed builds? I was (and anyone really reading my reply > would realize it) pointing to this specific failed build. > > And I'm just curious; how would a configuration error (that the user > has made) lead to a graphics file missing during the build? (not > counting in those "configurations" where you're yourself editing the > ebuild or otherwise fucking with depends and build options suggested > by the ebuild maintainer) I already said I agree with you, that in this specific case it seems to=20 be a bug appropriate for reporting to b.g.o. But looking at your original response, you said: > I'd think that the developers would rather have that information > posted to http://bugs.gentoo.org/ instead... To me, Holly, and I'd bet many others, the "instead..." in that line=20 could only be read as telling the OP that he has posted to the wrong=20 place, and that we do not welcome such things here. Plus, the OP message was very much of the "here is the output of a=20 failed build, what does it mean" variety. Many such posts come from=20 people who don't know how to recognize the actual source of the build=20 failure. Whether it says "missing file", "unresolved symbol", "locking=20 failed", or "compiler bug", they simply do not know what it *really*=20 means (and sometimes, not even what line contains the real problem). Now, I don't mean to offend any users here. I don't expect everybody=20 running Gentoo to be a programmer or linux expert. So I will say it=20 clearly: if a user encounters an error in emerge that he doesn't know=20 what to do with, it is entirely appropriate to post here first. > Of course, but in this case it wasn't an oversight... The poster > explicitly said that using march=3Dk8 seemed to no longer be the > recommendation of the docs. That implies at least _some_ looking into > the subject before posting... No, Holly said that her advice was based on "recent threads". A recent=20 thread on this list involving gzip on by an amd64 user suggested trying=20 different march options. Now, it was _bad_ advice (sorry Holly, but it=20 was!), but Holly did say she doesn't use amd64 and wasn't sure. > Since I'm myself using the specified platform and have had at least a > bit experience with it Good. Please help educate those of us who don't have or know the amd64=20 platform very well! :-) > Also, since the originator had posted the "emerge info" output, I > assumed that he/she was at least a bit familiar with how bug handling > is handled by Gentoo. Maybe, but I still think it was pretty clear that the OP was not sure=20 whether the problem was an actual bug or not. -Richard --=20 gentoo-user@gentoo.org mailing list