public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/46720] [4.6 Regression] missing quadmath_weak.h with --enable-maintainer-mode
Date: Thu, 02 Dec 2010 10:24:00 -0000 [thread overview]
Message-ID: <bug-46720-4-0TEH653FFk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46720-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46720
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2010-12-02 10:24:07 UTC ---
The issue seems to be fixed after upgrading to automake 1.11.1
from 1.11, so I am ready to resolve this as invalid.
However, two points:
- The build process complains about the automake 1.11, but this warning
scrolls past really fast, and if automake 1.11 really causes issues,
this should be addressed.
- The timestamps on the generated files should be set so that no
unneeded regeneration takes place. How do you do that in svn?
Any ideas on either point?
next prev parent reply other threads:[~2010-12-02 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 7:40 [Bug libfortran/46720] New: " tkoenig at gcc dot gnu.org
2010-11-30 7:41 ` [Bug libfortran/46720] " tkoenig at gcc dot gnu.org
2010-12-02 10:24 ` tkoenig at gcc dot gnu.org [this message]
2010-12-02 10:33 ` burnus at gcc dot gnu.org
2010-12-07 10:10 ` burnus at gcc dot gnu.org
2010-12-09 13:16 ` jakub at gcc dot gnu.org
2010-12-09 13:34 ` burnus at gcc dot gnu.org
2010-12-13 17:17 ` rwild at gcc dot gnu.org
2010-12-20 8:52 ` burnus at gcc dot gnu.org
2010-12-23 9:41 ` tkoenig at gcc dot gnu.org
2010-12-23 9:43 ` jakub 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-46720-4-0TEH653FFk@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: 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).