From: Piotr Kubaj <pkubaj@freebsd.org>
To: David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd
Date: Sun, 20 Mar 2022 13:07:15 +0100 [thread overview]
Message-ID: <YjcY8xgRtHtzTraz@KGPE-D16> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 176 bytes --]
fpu-glibc name is a bit incorrect, since it also works on other systems.
I have verified that it builds and can also build other packages
correctly (that were failing before).
[-- Attachment #1.2: 0001-fortran-on-powerpc-unknown-freebsd-also-use-fpu-glib.patch --]
[-- Type: text/x-diff, Size: 955 bytes --]
From 0feb83fae30070cf250781449670638d7addd947 Mon Sep 17 00:00:00 2001
From: Piotr Kubaj <pkubaj@FreeBSD.org>
Date: Sun, 20 Mar 2022 13:03:13 +0100
Subject: [PATCH] fortran: on powerpc*-unknown-freebsd*, also use fpu-glibc
It builds fine and correctly bulds packages on FreeBSD.
It looks like "fpu-glibc" name is a bit misleading since it also works
on FreeBSD.
Signed-off-by: Piotr Kubaj <pkubaj@FreeBSD.org>
---
libgfortran/configure.host | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/libgfortran/configure.host b/libgfortran/configure.host
index 3d6c2db7772..0f8bc7e0459 100644
--- a/libgfortran/configure.host
+++ b/libgfortran/configure.host
@@ -61,6 +61,14 @@ case "${host_cpu}" in
ieee_support='yes'
;;
esac
+ ;;
+ powerpc*)
+ case "${host_os}" in
+ freebsd*)
+ fpu_host='fpu-glibc'
+ ieee_support='yes'
+ ;;
+ esac
esac
--
2.35.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-03-20 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 12:07 Piotr Kubaj [this message]
2022-03-20 12:19 ` Segher Boessenkool
2022-03-20 15:30 FX
2022-04-13 14:56 ` Piotr Kubaj
2022-04-13 15:27 ` FX
2022-04-14 0:49 ` Piotr Kubaj
2022-04-14 7:05 ` FX
2022-04-14 14:09 ` Piotr Kubaj
2022-04-28 17:09 ` Piotr Kubaj
2022-04-28 18:55 ` FX
2022-04-30 18:28 ` Piotr Kubaj
2022-04-30 19:17 ` FX
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=YjcY8xgRtHtzTraz@KGPE-D16 \
--to=pkubaj@freebsd.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).