From: Dennis Clarke <dclarke@blastwave.org>
To: gcc-help@gcc.gnu.org
Subject: Re: make fails to build libgcc
Date: Sun, 6 Sep 2020 12:10:10 -0400 [thread overview]
Message-ID: <9075b0c4-7a9e-c753-2e8a-b2cdcd1d05f0@blastwave.org> (raw)
In-Reply-To: <1599383163.829669708@f19.my.com>
On 9/6/20 5:06 AM, fedor_qd@mail.ru wrote:
>
> Hi! I asked several days ago and nobody answers. Any idea?
What did you use for "configure" and what were the results of that
configure command?
What operating system?
What architecture?
What were the env var setup at the time? CFLAGS? CPPFLAGS? etc ?
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
next prev parent reply other threads:[~2020-09-06 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 10:15 Fiodar
2020-09-06 9:06 ` fedor_qd
2020-09-06 16:10 ` Dennis Clarke [this message]
2020-09-06 21:27 ` Re[2]: " fedor_qd
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=9075b0c4-7a9e-c753-2e8a-b2cdcd1d05f0@blastwave.org \
--to=dclarke@blastwave.org \
--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).