On 05/07/23 20:19, Richard Fish wrote: > Patrick Börjesson wrote: > > 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 > could only be read as telling the OP that he has posted to the wrong > place, and that we do not welcome such things here.
Ok, reading my original post again I can see your point ;) > Plus, the OP message was very much of the "here is the output of a > failed build, what does it mean" variety. Many such posts come from > people who don't know how to recognize the actual source of the build > failure. Whether it says "missing file", "unresolved symbol", "locking > failed", or "compiler bug", they simply do not know what it *really* > means (and sometimes, not even what line contains the real problem). Ok, I might have read a bit too much into the fact that he posted the output of "emerge info". Not very usual in this list (from what I've seen in the last couple of years) since most people who don't know what line in the build failure is relevant mostly don't give much information either concerning arch and other information that might be important to help finding the cause. Although... I would suggest that the OP give a more explicit "question", since I was really not sure if it was a "anyone seen this before?", "I'm a n00b, please solve this for me!" or a "where should I take this to get it solved?" question. > Now, I don't mean to offend any users here. I don't expect everybody > running Gentoo to be a programmer or linux expert. So I will say it > clearly: if a user encounters an error in emerge that he doesn't know > what to do with, it is entirely appropriate to post here first. Agreed > > 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... > > No, Holly said that her advice was based on "recent threads". A recent > thread on this list involving gzip on by an amd64 user suggested trying > different march options. Now, it was _bad_ advice (sorry Holly, but it > was!), but Holly did say she doesn't use amd64 and wasn't sure. Ok. I just make it a point of trying to find a bit more information, than just previous threads in a user mailinglist, about the things I suggest. But I'll try being more forgiving towards those who might not next time ;) > > 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 > platform very well! :-) Ehm... now let's not take this overboard ;) I'm by no means an expert (or even near experienced) on this arch. I'm just saying I might have at least some information that might be more relevant than a 32 bit only person might have... > > 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 > whether the problem was an actual bug or not. Maybe, but I'm still inclined to give short (and sometimes uninformative) answers to questions that doesn't really give enough information regarding both the experience level of the person, and especially what he/she wants help with. -- Regards, Patrick Börjesson PGP signature: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21792A5D PGP fingerprint: 74AF D4EF 6BDE CF77 16BE 6A29 CDB8 7607 2179 2A5D
pgpdswVpJHBjf.pgp
Description: PGP signature
