public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54419] [4.8 Regression] Compiling libstdc++-v3/src/c++11/random.cc fails on platforms not knowing rdrand
Date: Thu, 06 Sep 2012 14:33:00 -0000	[thread overview]
Message-ID: <bug-54419-4-npLs17Loak@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54419-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54419

--- Comment #43 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-09-06 14:31:53 UTC ---
(In reply to comment #42)
> Sorry if I'm saying something naive - I didn't follow the whole discussion -
> but I don't understand why - assuming indeed we want to do something at
> configure time - are being attached patches directly touching
> libstdc++-v3/configure* files, instead of acinclude.m4 (to be processed by
> autoreconf), which is the normal way we write this kind of code in the
> libraries.

Probably because...

  AC_TRY_COMPILE(, [
#if !defined __LONG_DOUBLE_128__ || (defined(__sparc__) && defined(__arch64__))
#error no need for long double compatibility
#endif
  ], [ac_ldbl_compat=yes], [ac_ldbl_compat=no])
  if test "$ac_ldbl_compat" = yes; then
    AC_DEFINE([_GLIBCXX_LONG_DOUBLE_COMPAT],1,
              [Define if compatibility should be provided for
-mlong-double-64.])
   
port_specific_symbol_files="\$(top_srcdir)/config/os/gnu-linux/ldbl-extra.ver"
  fi

already existed immediately above the new test in configure.ac.


  parent reply	other threads:[~2012-09-06 14:33 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 14:07 [Bug bootstrap/54419] New: [4.8 Regression] Compiling libstdc++-v3/src/c++11/random.cc fails on x86_64-apple-darwin10 dominiq at lps dot ens.fr
2012-08-30 19:41 ` [Bug bootstrap/54419] [4.8 Regression] Compiling libstdc++-v3/src/c++11/random.cc fails on platforms not knowing rdrand dominiq at lps dot ens.fr
2012-08-30 20:20 ` drepper.fsp at gmail dot com
2012-08-30 20:38 ` dominiq at lps dot ens.fr
2012-08-31 12:55 ` dominiq at lps dot ens.fr
2012-08-31 14:00 ` dominiq at lps dot ens.fr
2012-08-31 14:49 ` howarth at nitro dot med.uc.edu
2012-08-31 15:40 ` howarth at nitro dot med.uc.edu
2012-08-31 17:17 ` paolo.carlini at oracle dot com
2012-08-31 17:47 ` drepper.fsp at gmail dot com
2012-09-01 19:21 ` tkoenig at gcc dot gnu.org
2012-09-01 19:31 ` tkoenig at gcc dot gnu.org
2012-09-02 17:46 ` pault at gcc dot gnu.org
2012-09-02 17:54 ` polacek at redhat dot com
2012-09-02 18:04 ` hjl.tools at gmail dot com
2012-09-02 20:06 ` drepper.fsp at gmail dot com
2012-09-03  8:32 ` jakub at gcc dot gnu.org
2012-09-03  9:44 ` glisse at gcc dot gnu.org
2012-09-03  9:49 ` jakub at gcc dot gnu.org
2012-09-03 10:13 ` glisse at gcc dot gnu.org
2012-09-04  1:08 ` drepper.fsp at gmail dot com
2012-09-04 10:29 ` dominiq at lps dot ens.fr
2012-09-04 14:21 ` howarth at nitro dot med.uc.edu
2012-09-04 15:54 ` jakub at gcc dot gnu.org
2012-09-04 15:57 ` dominiq at lps dot ens.fr
2012-09-04 16:15 ` dominiq at lps dot ens.fr
2012-09-04 16:38 ` howarth at nitro dot med.uc.edu
2012-09-04 16:49 ` howarth at nitro dot med.uc.edu
2012-09-04 17:26 ` howarth at nitro dot med.uc.edu
2012-09-04 18:26 ` glisse at gcc dot gnu.org
2012-09-05  9:40 ` dominiq at lps dot ens.fr
2012-09-05  9:46 ` dominiq at lps dot ens.fr
2012-09-05 10:48 ` glisse at gcc dot gnu.org
2012-09-05 12:32 ` dominiq at lps dot ens.fr
2012-09-05 12:42 ` jakub at gcc dot gnu.org
2012-09-05 13:00 ` dominiq at lps dot ens.fr
2012-09-05 13:26 ` drepper.fsp at gmail dot com
2012-09-05 13:59 ` drepper.fsp at gmail dot com
2012-09-06 14:05 ` howarth at nitro dot med.uc.edu
2012-09-06 14:13 ` howarth at nitro dot med.uc.edu
2012-09-06 14:17 ` jakub at gcc dot gnu.org
2012-09-06 14:19 ` jakub at gcc dot gnu.org
2012-09-06 14:22 ` paolo.carlini at oracle dot com
2012-09-06 14:33 ` howarth at nitro dot med.uc.edu [this message]
2012-09-06 14:49 ` paolo.carlini at oracle dot com
2012-09-06 15:00 ` jakub at gcc dot gnu.org
2012-09-06 15:33 ` paolo.carlini at oracle dot com
2012-09-06 16:02 ` dominiq at lps dot ens.fr
2012-09-06 16:16 ` howarth at nitro dot med.uc.edu
2012-09-06 16:48 ` dominiq at lps dot ens.fr
2012-09-07 13:52 ` howarth at nitro dot med.uc.edu
2012-09-08  0:28 ` howarth at nitro dot med.uc.edu
2012-09-08 10:43 ` redi at gcc dot gnu.org
2012-09-08 11:03 ` redi at gcc dot gnu.org
2012-09-09 15:24 ` dominiq at lps dot ens.fr
2012-09-09 16:17 ` paolo.carlini at oracle dot com
2012-09-09 16:21 ` redi at gcc dot gnu.org
2012-09-09 16:24 ` redi at gcc dot gnu.org
2012-09-09 17:23 ` redi at gcc dot gnu.org
2012-09-09 17:33 ` redi at gcc dot gnu.org
2012-09-09 18:19 ` dominiq at lps dot ens.fr
2012-09-09 19:49 ` redi at gcc dot gnu.org
2012-09-09 20:47 ` redi at gcc dot gnu.org
2012-09-10 10:02 ` paul.richard.thomas at gmail dot com

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-54419-4-npLs17Loak@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).