From: Andreas Schwab <schwab@suse.de>
To: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
Cc: "François-Xavier Coudert" <fxcoudert@gmail.com>,
bonzini@gnu.org, dj@redhat.com, neroden@gcc.gnu.org,
aoliva@redhat.com, gcc-patches <gcc-patches@gcc.gnu.org>,
GFortran <fortran@gcc.gnu.org>
Subject: Re: [libgfortran,patch] New autoconf test
Date: Tue, 09 Jan 2007 09:44:00 -0000 [thread overview]
Message-ID: <jetzz0k005.fsf@sykes.suse.de> (raw)
In-Reply-To: <45A34B7E.8050900@lu.unisi.ch> (Paolo Bonzini's message of "Tue, 09 Jan 2007 08:59:58 +0100")
Paolo Bonzini <paolo.bonzini@lu.unisi.ch> writes:
> I think something like this should work too. Autoconf provides macros for
> compile tests:
>
> AC_MSG_CHECKING([whether the GNU Fortran compiler is working])
> AC_COMPILE_IFELSE([[
> program foo
> real, parameter :: bar = sin(12.34)
> end program foo]], ,
> [AC_MSG_RESULT([yes])],
> [AC_MSG_RESULT([no])
> AC_MSG_ERROR([GNU Fortran is not working; please report a bug in
> http://gcc.gnu.org/bugzilla, attaching `pwd`/config.log])
Except that you have to switch the language to Fortran, by putting it
between AC_LANG_PUSH(Fortran) and AC_LANG_POP(Fortran).
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-01-09 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 7:55 François-Xavier Coudert
2007-01-09 8:00 ` Paolo Bonzini
2007-01-09 9:44 ` Andreas Schwab [this message]
[not found] ` <19c433eb0701090147l4f311893w2d429aec4c616d6f@mail.gmail.com>
2007-01-09 10:40 ` Andreas Schwab
2007-01-09 10:44 ` Paolo Bonzini
2007-01-09 11:41 ` François-Xavier Coudert
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=jetzz0k005.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=aoliva@redhat.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=neroden@gcc.gnu.org \
--cc=paolo.bonzini@lu.unisi.ch \
/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).