public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/47145] configure test for docbook-xsl-ns stylesheets uses hardcoded path
Date: Tue, 08 Mar 2011 00:04:00 -0000 [thread overview]
Message-ID: <bug-47145-4-znx1Lsh5pH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47145-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47145
--- Comment #24 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2011-03-08 00:04:10 UTC ---
Author: bkoz
Date: Tue Mar 8 00:04:05 2011
New Revision: 170763
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170763
Log:
2011-03-07 Benjamin Kosnik <bkoz@redhat.com>
Matthias Klose <doko@ubuntu.com>
Jonathan Wakely <redi@gcc.gnu.org>
PR libstdc++/47145
* acinclude.m4 (GLIBCXX_CONFIGURE_DOCBOOK): Define.
* configure.ac: Use it.
* doc/Makefile.am (XSL_STYLE_DIR): Set at configure time.
* configure: Regenerate.
* doc/Makefile.in: Regenerate.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/Makefile.in
trunk/libstdc++-v3/acinclude.m4
trunk/libstdc++-v3/configure
trunk/libstdc++-v3/configure.ac
trunk/libstdc++-v3/doc/Makefile.am
trunk/libstdc++-v3/doc/Makefile.in
trunk/libstdc++-v3/include/Makefile.in
trunk/libstdc++-v3/libsupc++/Makefile.in
trunk/libstdc++-v3/po/Makefile.in
trunk/libstdc++-v3/python/Makefile.in
trunk/libstdc++-v3/src/Makefile.in
trunk/libstdc++-v3/testsuite/Makefile.in
next prev parent reply other threads:[~2011-03-08 0:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 15:23 [Bug libstdc++/47145] New: cross-compilation fails with "cannot check for file existence when cross compiling" John.Tytgat at aaug dot net
2011-01-02 0:32 ` [Bug libstdc++/47145] [4.6 Regression] " jsm28 at gcc dot gnu.org
2011-01-03 13:33 ` ktietz at gcc dot gnu.org
2011-01-03 14:19 ` ktietz at gcc dot gnu.org
2011-01-03 14:46 ` ktietz at gcc dot gnu.org
2011-01-03 15:15 ` paolo.carlini at oracle dot com
2011-01-03 16:12 ` joseph at codesourcery dot com
2011-01-03 16:37 ` paolo.carlini at oracle dot com
2011-01-03 18:04 ` redi at gcc dot gnu.org
2011-01-03 21:44 ` rguenth at gcc dot gnu.org
2011-01-04 13:03 ` paolo.carlini at oracle dot com
2011-01-04 13:28 ` ktietz at gcc dot gnu.org
2011-01-04 17:27 ` bkoz at gcc dot gnu.org
2011-01-04 17:43 ` redi at gcc dot gnu.org
2011-01-04 18:00 ` ktietz at gcc dot gnu.org
2011-01-04 18:23 ` paolo.carlini at oracle dot com
2011-01-04 18:57 ` jakub at gcc dot gnu.org
2011-01-04 20:10 ` doko at ubuntu dot com
2011-01-05 5:09 ` dongsheng.song at gmail dot com
2011-01-05 5:31 ` dongsheng.song at gmail dot com
2011-01-05 10:08 ` redi at gcc dot gnu.org
2011-01-05 11:46 ` ramana at gcc dot gnu.org
2011-01-05 11:50 ` paolo.carlini at oracle dot com
2011-01-05 12:23 ` [Bug libstdc++/47145] configure test for docbook-xsl-ns stylesheets uses hardcoded path redi at gcc dot gnu.org
2011-03-01 21:32 ` bkoz at gcc dot gnu.org
2011-03-02 17:44 ` bkoz at gcc dot gnu.org
2011-03-08 0:04 ` bkoz at gcc dot gnu.org [this message]
2011-03-17 22:01 ` doko at ubuntu dot com
2011-03-22 9:38 ` bkoz at gcc dot gnu.org
2011-03-22 9:50 ` doko at ubuntu dot com
2011-03-25 19:59 ` jakub at gcc dot gnu.org
2011-04-28 17:22 ` rguenth at gcc dot gnu.org
2012-02-02 20:25 ` bkoz at gcc dot gnu.org
2012-02-16 20:09 ` bkoz 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-47145-4-znx1Lsh5pH@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).