From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH v3 0/1] Fix glibc fortran header conflict for arm
Date: Tue, 25 Jun 2024 10:02:48 +0800 [thread overview]
Message-ID: <20240625020249.767760-1-kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
Tested for qemuarm64 with multilib enabled:
1. set machine and enable multilib
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
MACHINE = "qemuarm64"
DEFAULTTUNE:virtclass-multilib-lib32 = "armv7vethf-neon"
2. enable fortran and install to image
FORTRAN:forcevariable = ",fortran"
IMAGE_INSTALL:append = " gfortran lib32-gfortran"
3. build image and boot, run gfortran with option '-v' to verify
math-vector-fortran.h has been pre-included
for aarch64:
/usr/libexec/gcc/aarch64-poky-linux/14.1.0/f951 hello.f95 -quiet
-dumpdir a- -dumpbase hello.f95 -dumpbase-ext .f95 -mlittle-endian
-mabi=lp64 -version -fintrinsic-modules-path /usr/lib/gcc/aarch64-poky-linux/14.1.0/finclude
-fpre-include=/usr/lib/gcc/aarch64-poky-linux/14.1.0/finclude/math-vector-fortran.h
-o /tmp/ccuPIzQY.s
for arm:
/usr/libexec/gcc/arm-pokymllib32-linux-gnueabi/14.1.0/f951 hello.f95
-quiet -dumpdir a- -dumpbase hello.f95 -dumpbase-ext .f95
-mfloat-abi=hard -mtls-dialect=gnu -marm -mlibarch=armv7ve+fp
-march=armv7ve+fp -version -fintrinsic-modules-path /usr/lib/gcc/arm-pokymllib32-linux-gnueabi/14.1.0/finclude
-fpre-include=/usr/lib/gcc/arm-pokymllib32-linux-gnueabi/14.1.0/finclude/math-vector-fortran.h
-o /tmp/cc5pikK8.s
Kai Kang (1):
glibc: fix fortran header file conflict for arm
meta/recipes-core/glibc/glibc-package.inc | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2024-06-25 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 2:02 kai.kang [this message]
2024-06-25 2:02 ` [PATCH v3 1/1] glibc: fix fortran header file conflict for arm kai.kang
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=20240625020249.767760-1-kai.kang@windriver.com \
--to=kai.kang@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.