public inbox for gentoo-sparc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hamish Greig <hgreig@bigpond.net.au>
To: gentoo-sparc@lists.gentoo.org
Subject: Re: [gentoo-sparc] Another quiet question
Date: Tue, 12 Feb 2008 12:33:38 +1100	[thread overview]
Message-ID: <47B0F772.7020904@bigpond.net.au> (raw)
In-Reply-To: <38D04BF3A4B7B2499D19EB1DB54285EA06B9C5C5@FNB1EX01.gci.com>

Leif, lose the attitude. You are asking questions of this list and 
asking the list to do work ascertaining what you have done and what you 
are capable of doing. Please read
http://www.catb.org/~esr/faqs/smart-questions.html
We know nothing of your problems except that you can cut and paste 
errors. I am not offended by your terseness, just frustrated that you 
aren't being forthcoming with more information, which would allow people 
to immediately help or state inability to help past where you have 
already got to. The extra information you have given below doesn't 
particularly help and as I think you want the problem fixed I suggest 
you become involved in the solution instead of expecting a solution to 
be given to you because you are using gentoo's product. Open source tech 
support doesn't work like that unless you have a support contract (== $$$)
Thanks
Hamish

Leif Sawyer wrote:
> Hamish Greig [mailto:hgreig@bigpond.net.au] 
>> I think the reason no-one responds to your posts are because 
>> they are not structured in any methodical way. No sequence 
>> showing how you've already tried to investigate the problem, 
>> just a post asking for an answer, which doesn't get a lot of 
>> respect from people who've taken time and effort to learn 
>> things already.
> 
> I'm sorry that my terseness offends your sensibilities.  All
> the information that I had available was in the post, i.e.,
> gcc failed to build.
> 
>> What more than this dump can you tell us about this error? 
> 
> it's reproducable.  it's not caused by OOM, but obviously by
> a build-level error, because certain objects that the source
> code thinks should be available, aren't.  Perhaps looking at
> the detail I provided a bit closer might reveal that fact, in
> an obvious sort of manner (i.e., an ld error)
> 
>> What have you already done to investigate it? what level of 
>> skill do you have in this area? are we expected to fix it for 
>> you step by step or to guide you to a resolution?
> 
> Since I'm neither a maintainer, nor a GCC developer, but simply
> a gentoo-sparc user, my job is to report the bugs that I see.
> 
> If you are a developer or maintainer, one might questions the
> validity in your stance of attacking users for not providing
> the information that -you- feel is needed, instead of simply
> asking for additional detail.
> 
> It's no wonder the list is dry and gentoo is losing it's path.


-- 
gentoo-sparc@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-12  1:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  9:15 [gentoo-sparc] PCI-SUN4V: strange virtual-dma size Alexander Piavka
2008-01-09 22:38 ` [gentoo-sparc] Correctable ECC Error question Leif Sawyer
2008-02-11 23:03   ` [gentoo-sparc] Another quiet question Leif Sawyer
2008-02-12  0:47     ` Hamish Greig
2008-02-12  1:16       ` Leif Sawyer
2008-02-12  1:33         ` Hamish Greig [this message]
2008-02-13 17:29           ` Javier O. Augusto
2008-02-12  0:40   ` [gentoo-sparc] Correctable ECC Error question Hamish Greig
2008-02-12  1:10     ` Leif Sawyer

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=47B0F772.7020904@bigpond.net.au \
    --to=hgreig@bigpond.net.au \
    --cc=gentoo-sparc@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