From: Tristan Gingold <gingold@adacore.com>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>,
GCC Patches <gcc-patches@gcc.gnu.org>,
fortran@gcc.gnu.org
Subject: Re: [Patch V2] libgfortran: do not assume libm
Date: Tue, 27 Mar 2012 07:51:00 -0000 [thread overview]
Message-ID: <E897B64E-578C-466F-A1C2-BF75327F3B83@adacore.com> (raw)
In-Reply-To: <CAO9iq9EY51vCwj_BN3z9h7GEVWPm2g7wjgVGmuQuyg_tESx89Q@mail.gmail.com>
On Mar 26, 2012, at 11:43 PM, Janne Blomqvist wrote:
[...]
> On x86_64-unknown-linux-gnu bootstrap I see the following:
>
>
> make[1]: Entering directory
> `/home/janne/src/gfortran/trunk/objdir-git/x86_64-unknown-linux-gnu/libgfortran'
> make check-am
> make[2]: Entering directory
> `/home/janne/src/gfortran/trunk/objdir-git/x86_64-unknown-linux-gnu/libgfortran'
> (CDPATH="${ZSH_VERSION+.}:" && cd ../../../trunk-git/libgfortran &&
> /bin/bash /home/janne/src/gfortran/trunk/trunk-git/missing --run
> autoheader)
> true DO=all multi-do # make
> make[1]: Entering directory `/home/janne/src/gfortran/trunk/objdir-git/gcc'
> Making a new config file...
> echo "set tmpdir
> /home/janne/src/gfortran/trunk/objdir-git/gcc/testsuite" >> ./site.tmp
> autoheader: warning: missing template: HAVE_ACOS
> autoheader: Use AC_DEFINE([HAVE_ACOS], [], [Description])
> autoheader: warning: missing template: HAVE_ACOSF
...
> autoheader: warning: missing template: HAVE_YNF
> autoheader: warning: missing template: HAVE_YNL
> make[2]: *** [../../../trunk-git/libgfortran/config.h.in] Error 1
> make[2]: Leaving directory
> `/home/janne/src/gfortran/trunk/objdir-git/x86_64-unknown-linux-gnu/libgfortran'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory
> `/home/janne/src/gfortran/trunk/objdir-git/x86_64-unknown-linux-gnu/libgfortran'
> make: *** [check-target-libgfortran] Error 2
> make: *** Waiting for unfinished jobs....
>
>
> Anybody else seeing something similar? The strange thing is that even
> though there is an error the bootstrapping continues just fine. Though
> I haven't had time to look into it deeper.
Yes, I can reproduce that. Autoheader returns 1 as exit status even for warnings.
I am investigating (I suppose that adding a description will fix the issue).
Tristan.
next prev parent reply other threads:[~2012-03-27 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 9:49 [Patch] " Tobias Burnus
2012-03-20 9:57 ` Tristan Gingold
2012-03-22 8:30 ` [Patch V2] " Tristan Gingold
2012-03-22 10:07 ` Paolo Bonzini
2012-03-22 20:57 ` Tobias Burnus
2012-03-26 8:44 ` Tristan Gingold
2012-03-26 21:43 ` Janne Blomqvist
2012-03-27 7:51 ` Tristan Gingold [this message]
2012-03-27 8:01 ` Tristan Gingold
2012-03-27 8:39 ` Janne Blomqvist
2012-03-27 9:29 ` Tristan Gingold
2012-03-30 10:22 ` Tristan Gingold
2012-03-30 12:40 ` Paolo Bonzini
2012-04-02 7:47 ` Tristan Gingold
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=E897B64E-578C-466F-A1C2-BF75327F3B83@adacore.com \
--to=gingold@adacore.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias.burnus@physik.fu-berlin.de \
/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).