From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Andy Bowery <abowery@yahoo.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Need to build libgfortran.a and libquadmath.a
Date: Mon, 28 Mar 2022 20:52:43 +0100 [thread overview]
Message-ID: <CAH6eHdRfzZQJxEjO2EqetoVjE=U0yX+edFU04dHTcaSUm0x5tg@mail.gmail.com> (raw)
In-Reply-To: <222147991.846192.1648491515241@mail.yahoo.com>
On Mon, 28 Mar 2022 at 19:19, Andy Bowery via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Help! I need to build both libgfortran.a and libquadmath.a for an embedded ARM-based environment. These libraries are currently not available for this environment, so I going to have to build them myself. Both need to be static libraries. I have downloaded the GNU GCC project and I am currently running 'make' (in the top level gcc folder) on this in this environment, but it is taking days on this limited environment! And I am not even sure it will produce the files I need. Is there a quicker way of building these files?
Don't build on the ARM system, build a cross compiler that runs on a
much more powerful multicore system.
> Will this make process produce these particular files?
It depends how you configured GCC.
next prev parent reply other threads:[~2022-03-28 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <222147991.846192.1648491515241.ref@mail.yahoo.com>
2022-03-28 18:18 ` Andy Bowery
2022-03-28 19:52 ` Jonathan Wakely [this message]
2022-03-29 15:29 ` Andy Bowery
2022-03-29 15:57 ` Xi Ruoyao
2022-03-31 13:20 ` Andy Bowery
2022-03-31 14:21 ` Richard Earnshaw
2022-03-31 14:21 ` Jonathan Wakely
2022-03-31 14:22 ` Jonathan Wakely
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='CAH6eHdRfzZQJxEjO2EqetoVjE=U0yX+edFU04dHTcaSUm0x5tg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=abowery@yahoo.com \
--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).