From: Jonathan Wakely <jwakely@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: "Luke Allardyce" <lukeallardyce@gmail.com>,
libstdc++ <libstdc++@gcc.gnu.org>,
gcc-patches@gcc.gnu.org,
"Daniel Krügler" <daniel.kruegler@gmail.com>
Subject: Re: [patch] Implement ISO/IEC TS 18822 C++ File system TS
Date: Wed, 13 May 2015 10:56:00 -0000 [thread overview]
Message-ID: <20150513105437.GD30202@redhat.com> (raw)
In-Reply-To: <yddr3qrcn10.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On 08/05/15 13:43 +0200, Rainer Orth wrote:
>Jonathan Wakely <jwakely@redhat.com> writes:
>
>> I've committed the two changes attached (only tested on linux again).
>>
>> patch2.txt should fix the mingw-w64 errors above, as well as the
>> issues Daniel reported, and should fix the error on Solaris 10
>>
>> Rainer, would you be able to test with
>> --enable-libstdcxx-filesystem-ts before we re-enable it to build by
>> default on solaris* ?
>
>I just did: a bootstrap on i386-pc-solaris2.10 completed successfully
>and the experimental/filesystem tests all PASSed. Given that Solaris 11
>was fine even before, I think it's safe to re-enable it by default on
>Solaris again.
Thanks. Re-enabled with this patch, committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1159 bytes --]
commit 38715a0b0a5afcb980570dfb65c591e3a7eb8cb9
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Sun May 10 19:46:25 2015 +0100
* acinclude.m4 (GLIBCXX_ENABLE_FILESYSTEM_TS): Re-enable on solaris.
* configure: Regenerate.
diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4
index 07b5bd7..6f67774 100644
--- a/libstdc++-v3/acinclude.m4
+++ b/libstdc++-v3/acinclude.m4
@@ -3926,7 +3926,7 @@ AC_DEFUN([GLIBCXX_ENABLE_FILESYSTEM_TS], [
enable_libstdcxx_filesystem_ts=yes
;;
solaris*)
- enable_libstdcxx_filesystem_ts=no
+ enable_libstdcxx_filesystem_ts=yes
;;
*)
enable_libstdcxx_filesystem_ts=no
diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure
index 90a5192..39fc28c 100755
--- a/libstdc++-v3/configure
+++ b/libstdc++-v3/configure
@@ -79166,7 +79166,7 @@ $as_echo_n "checking whether to build Filesystem TS support... " >&6; }
enable_libstdcxx_filesystem_ts=yes
;;
solaris*)
- enable_libstdcxx_filesystem_ts=no
+ enable_libstdcxx_filesystem_ts=yes
;;
*)
enable_libstdcxx_filesystem_ts=no
next prev parent reply other threads:[~2015-05-13 10:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 17:42 Jonathan Wakely
2015-04-30 19:33 ` Jonathan Wakely
[not found] ` <CAFW6PZB9WvskzrKCsNKK4s-5oXWjcwkuZGMrWbrfgJ7fpJiCXQ@mail.gmail.com>
[not found] ` <20150501105351.GY3618@redhat.com>
2015-05-01 19:49 ` Jonathan Wakely
2015-05-02 9:52 ` Jonathan Wakely
2015-05-08 11:43 ` Rainer Orth
2015-05-13 10:56 ` Jonathan Wakely [this message]
2015-05-01 12:45 ` Rainer Orth
2015-05-01 15:11 ` Jonathan Wakely
2015-05-01 15:14 ` Rainer Orth
2015-05-01 17:03 ` Daniel Krügler
2015-05-01 17:55 ` Jonathan Wakely
2015-05-01 18:22 ` Jonathan Wakely
2015-05-01 19:28 ` Daniel Krügler
2015-05-01 19:38 ` Jonathan Wakely
2015-05-01 20:05 ` Jonathan Wakely
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=20150513105437.GD30202@redhat.com \
--to=jwakely@redhat.com \
--cc=daniel.kruegler@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=lukeallardyce@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.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).