From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Seyed Abolfazl Mortazavizadeh <mortazavi1369@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Gcc problem
Date: Wed, 13 Apr 2022 14:57:24 +0100 [thread overview]
Message-ID: <CAH6eHdSDMbcbGvoqWGC0NC__K0aoxLq-Gjo73SSeoAEBhA_hFA@mail.gmail.com> (raw)
In-Reply-To: <CAAG=NiE0z9_sMwCinFO47DHfwRGqPa+OvBp=K=8BRbPaXDdauw@mail.gmail.com>
N.B. everybody who emails this list has a "Gcc problem", so you're far
more likely to get a useful answer if you use a more relevant Subject
for your email.
For example, if the problem relates to build an ARM cross compiler,
then say so in the subject.
next prev parent reply other threads:[~2022-04-13 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 13:44 Seyed Abolfazl Mortazavizadeh
2022-04-13 13:57 ` Jonathan Wakely [this message]
2022-04-13 14:34 ` Nucleo F767ZI, STM32CubeIDE problem, CC1 error Seyed Abolfazl Mortazavizadeh
2022-04-13 20:49 ` Alexander Shpilkin
-- strict thread matches above, loose matches on Subject: below --
2005-10-12 19:09 Gcc problem Paul Mitchell
2001-09-20 18:01 gcc problem mouhcin chergou
2000-09-20 8:32 GCC problem Djoko Djordjevic
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=CAH6eHdSDMbcbGvoqWGC0NC__K0aoxLq-Gjo73SSeoAEBhA_hFA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mortazavi1369@gmail.com \
/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).