public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/96661] New: configure:16984: error: unsupported system, cannot find Fortran int kind=16 Date: Mon, 17 Aug 2020 16:58:24 +0000 [thread overview] Message-ID: <bug-96661-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96661 Bug ID: 96661 Summary: configure:16984: error: unsupported system, cannot find Fortran int kind=16 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: danglin at gcc dot gnu.org CC: burnus at gcc dot gnu.org, jakub at gcc dot gnu.org Target Milestone: --- Host: hppa64-hp-hpux11.11 Target: hppa64-hp-hpux11.11 Build: hppa64-hp-hpux11.11 Whiling configuring libgomp, the following error occurs: configure:16984: error: unsupported system, cannot find Fortran int kind=16, nee ded for omp_depend_kind ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_build=hppa64-hp-hpux11.11 ac_cv_c_compiler_gnu=yes Looks like this was introduced by: 2020-07-23 Tobias Burnus <tobias@codesourcery.com> * configure.ac: Add OMP_DEPEND_KIND and OMP_INT128_SIZE. * libgomp_f.h.in (omp_check_defines): Check whether sizeof of determined Fortran kind and C typedef match. * omp_lib.f90.in: Add omp_depened_kind. * omp_lib.h.in: Likewise; fix omp_alloctrait_key_kind. * configure: Regenerate. * Makefile.in: Regenerate. * testsuite/Makefile.in: Regenerate. Guess this is because target doesn't support int128. For the most part, libgomp used to work on this target.
next reply other threads:[~2020-08-17 16:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-17 16:58 danglin at gcc dot gnu.org [this message] 2020-08-17 18:10 ` [Bug libgomp/96661] " burnus at gcc dot gnu.org 2020-08-17 18:28 ` dave.anglin at bell dot net 2021-09-08 22:46 ` pinskia at gcc dot gnu.org 2021-09-28 13:16 ` cvs-commit at gcc dot gnu.org 2021-09-28 13:26 ` burnus at gcc dot gnu.org 2021-09-28 13:26 ` cvs-commit at gcc dot gnu.org 2021-11-05 16:08 ` cvs-commit at gcc dot gnu.org 2021-11-05 16:44 ` cvs-commit at gcc dot gnu.org
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=bug-96661-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).