From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH 2/2] libgcc-initial: Do not build fp128 to decimal ppc functions
Date: Tue, 30 Mar 2021 14:30:19 -0700 [thread overview]
Message-ID: <20210330213019.2300696-3-raj.khem@gmail.com> (raw)
In-Reply-To: <20210330213019.2300696-1-raj.khem@gmail.com>
These functions depend on glibc headers e.g.
stdlib.h/fenv.h/string.h/stdio.h which do not exist when building
lbgcc-initial, and these functions are not needed during glibc build
so we are fine to disable them
introdcued with [1]
[1] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=781183595acba67a37c66f59a0c1d9b5fee7e248
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta/recipes-devtools/gcc/libgcc-initial.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/gcc/libgcc-initial.inc b/meta/recipes-devtools/gcc/libgcc-initial.inc
index 06bf224f73..f7d8041226 100644
--- a/meta/recipes-devtools/gcc/libgcc-initial.inc
+++ b/meta/recipes-devtools/gcc/libgcc-initial.inc
@@ -51,6 +51,8 @@ do_configure_prepend () {
do_configure_append () {
sed -i -e 's#thread_header = .*#thread_header = gthr-single.h#' ${B}/${BPN}/Makefile
+ sed -i -e '/^libgcc_tm_defines = $/a fp128_dec_funcs =' ${B}/${BPN}/Makefile
+ sed -i -e '/^libgcc_tm_defines = $/a fp128_decstr_funcs =' ${B}/${BPN}/Makefile
}
do_install_append () {
--
2.31.1
next prev parent reply other threads:[~2021-03-30 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 21:30 [RFT][PATCH 0/2] GCC 11 Pre-release Khem Raj
2021-03-30 21:30 ` [PATCH 1/2] gcc: Upgrade to GCC 11 Khem Raj
2021-03-30 21:30 ` Khem Raj [this message]
2021-04-10 15:13 ` [OE-core] [RFT][PATCH 0/2] GCC 11 Pre-release Richard Purdie
2021-04-10 17:58 ` Khem Raj
2021-04-12 7:08 ` Naveen Saini
2021-04-12 9:45 ` Richard Purdie
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=20210330213019.2300696-3-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.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