From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: pawel.osmialowski@foss.arm.com
Subject: Re: Support for Flang and ARM HPC compiler
Date: Wed, 27 Feb 2019 22:37:05 +0100 [thread overview]
Message-ID: <1900721.igzjKCEPDk@omega> (raw)
In-Reply-To: <20190227134730.33545-1-pawel.osmialowski@foss.arm.com>
Hi Pul,
> This patch is a part of the cross-project set of patches
> that soon will be sent to all of the relevant GNU Autotools
> components: gnulib, autoconf, automake and libtool.
>
> The purpose of this is to add awareness of the new LLVM Fortran
> compiler (Flang) along with LLVM-derived ARM HPC Compilers.
>
> These new compilers are recognized by their executable binary
> names: flang, armflang, armclang, armclang++
>
> Without those patches 'configure' script generates wrong set
> of command-line flags.
While the patches in principle look harmless, I stand by what I said in [1]:
* The patch to gnulib/m4/std-gnu11.m4 is interesting to us *once* the
corresponding Autoconf patch [2] has been accepted.
* The patch to gnulib/build-aux/config.rpath is interesting to us *once* the
corresponding Libtool patch [3] has been accepted.
Yes, I know, maintenance on the Autoconf and Libtool side is slow these days.
Bruno
[1] https://lists.gnu.org/archive/html/bug-gnulib/2017-09/msg00174.html
[2] https://lists.gnu.org/archive/html/autoconf-patches/2017-08/msg00013.html
[3] https://lists.gnu.org/archive/html/libtool-patches/2017-08/msg00002.html
next prev parent reply other threads:[~2019-02-27 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 13:47 Support for Flang and ARM HPC compiler pawel.osmialowski
2019-02-27 13:47 ` [PATCH] " pawel.osmialowski
2019-02-27 21:37 ` Bruno Haible [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-30 12:01 pawel.osmialowski
2017-08-30 11:43 pawel.osmialowski
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1900721.igzjKCEPDk@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=pawel.osmialowski@foss.arm.com \
/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).