public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: Dave Blanchard <dave@killthe.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GNAT on GCC 10.x has build problems
Date: Mon, 04 Dec 2023 00:06:00 -0300	[thread overview]
Message-ID: <or8r6avf8n.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <20231203131605.ef71855b55269dc7ac8133bd@killthe.net> (Dave Blanchard's message of "Sun, 3 Dec 2023 13:16:05 -0600")

[moving from gcc@ to gcc-help@]

On Dec  3, 2023, Dave Blanchard <dave@killthe.net> wrote:

> I'm not asking for any of your 'help', in case it wasn't obvious.

FWIW, it was obvious to me that you were asking for help in assessing
whether a certain situation you hit had changed in later versions.

I'm afraid we're going to need more details as to what you tried (as in,
which sequence of commands you ran) and which unexpected results it
produced (as in, output), because that was not at all clear to me.  Your
initial message was very light in correct details, and heavy in
incorrect assumptions and venting, wihch makes me hesitant to respond.

I will, however, because in case you really are interested in getting a
useful interaction, you will need to adjust your interface with GCC
developers.  All participants in these mailing lists are expected to
observe the GNU Kind Communication Guidelines, and it was evident that
you weren't familiar with them.  Please have a thorough look.
https://www.gnu.org/philosophy/kind-communication.en.html

Thanks,

-- 
Alexandre Oliva, happy hacker                    https://FSFLA.org/blogs/lxo/
   Free Software Activist                           GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice but
very few check the facts.  Think Assange & Stallman.  The empires strike back

           reply	other threads:[~2023-12-04  3:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20231203131605.ef71855b55269dc7ac8133bd@killthe.net>]

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=or8r6avf8n.fsf@lxoliva.fsfla.org \
    --to=oliva@gnu.org \
    --cc=dave@killthe.net \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).