public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/96661] configure:16984: error: unsupported system, cannot find Fortran int kind=16 Date: Tue, 28 Sep 2021 13:26:08 +0000 [thread overview] Message-ID: <bug-96661-4-OvCTiZrjJl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96661-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96661 --- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- Note the commit in comment 4 does not solve the problem that the hppa64-hp-hpux11.11 target in does not support TImode alias __int128 (yet) However, when building libgomp without Fortran support, it now should build again.
next prev parent reply other threads:[~2021-09-28 13:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-17 16:58 [Bug libgomp/96661] New: " danglin at gcc dot gnu.org 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 [this message] 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-OvCTiZrjJl@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).