public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@gmail.com>
To: GCC <gcc@gcc.gnu.org>
Subject: Building Single Tree for a Specific Set of CFLAGS
Date: Tue, 26 Mar 2024 16:52:28 -0500	[thread overview]
Message-ID: <CAF9ehCUCZcBkqRF62F4fBZ6VWGxSxX5qWEZqZQWXROXKbhMEYg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 489 bytes --]

Hi

For RTEMS, we normally build a multilib'ed gcc+newlib, but I have a case
where the CPU model is something not covered by our multilibs and not one
we are keen to add. I've looked around but not found anything that makes me
feel confident.

What's the magic for building a gcc+newlib with a single set of libraries
that are built for a specific CPU CFLAGS?

I am trying --disable-multlibs on the gcc configure and adding
CFLAGS_FOR_TARGET to make.

Advice appreciated.

Thanks.

--joel

             reply	other threads:[~2024-03-26 21:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 21:52 Joel Sherrill [this message]
2024-03-27  8:52 ` Christophe Lyon
2024-03-27 10:35   ` Kai Ruottu
2024-03-27 19:07   ` Joel Sherrill
2024-03-28  9:17     ` Christophe Lyon

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=CAF9ehCUCZcBkqRF62F4fBZ6VWGxSxX5qWEZqZQWXROXKbhMEYg@mail.gmail.com \
    --to=joel.sherrill@gmail.com \
    --cc=gcc@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).