David Edelsohn <dje....@gmail.com> writes:
> On Wed, Jul 20, 2011 at 4:25 PM, Ian Lance Taylor <i...@google.com> wrote:
>
>> Presumably the fix will be to use -frandom-seed. Does this patch fix
>> the problem? (The only real change is to fragment.am, the other changes
>> are all generated by automake).
>
> This patch gets the build past the compiler and runtime, although the
> build time now is much longer on AIX.
I have bootstrapped with the patch and run the libstdc++ testsuite on
x86_64-unknown-linux-gnu.
OK for mainline?
Ian
2011-07-21 Ian Lance Taylor <i...@google.com>
* fragment.am (CONFIG_CXXFLAGS): Add -frandom-seed.
* Makefile.in: Rebuild.
* doc/Makefile.in: Rebuild.
* include/Makefile.in: Rebuild.
* libsupc++/Makefile.in: Rebuild.
* po/Makefile.in: Rebuild.
* python/Makefile.in: Rebuild.
* src/Makefile.in: Rebuild.
* testsuite/Makefile.in: Rebuild.
Index: fragment.am
===================================================================
--- fragment.am (revision 176515)
+++ fragment.am (working copy)
@@ -16,7 +16,7 @@ toolexeclibdir = $(glibcxx_toolexeclibdi
# These bits are all figured out from configure. Look in acinclude.m4
# or configure.ac to see how they are set. See GLIBCXX_EXPORT_FLAGS.
CONFIG_CXXFLAGS = \
- $(SECTION_FLAGS) $(EXTRA_CXX_FLAGS)
+ $(SECTION_FLAGS) $(EXTRA_CXX_FLAGS) -frandom-seed=$@
WARN_CXXFLAGS = \
$(WARN_FLAGS) $(WERROR) -fdiagnostics-show-location=once
