#18240: fix MPIR's compliance with c++
-------------------------------------+-------------------------------------
       Reporter:  dimpase            |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.7
      Component:  packages:          |   Resolution:
  standard                           |    Merged in:
       Keywords:                     |    Reviewers:
        Authors:  Dima Pasechnik     |  Work issues:
Report Upstream:  Reported           |       Commit:
  upstream. Developers acknowledge   |  d358636766bf0abae69bb07f154053180bd14a8a
  bug.                               |     Stopgaps:
         Branch:  u/dimpase/18240    |
   Dependencies:                     |
-------------------------------------+-------------------------------------

Old description:

> with gcc 4.9.2, we hit this bug:
>
> [https://gcc.gnu.org/gcc-4.9/porting_to.html Header <cstddef> changes]
> The <cstddef> header was updated for C++11 support and this breaks some
> libraries which misuse macros meant for internal use by GCC only. For
> instance with GMP versions up to 5.1.3, you may see:
> {{{
> /usr/include/c++/4.9.0/cstddef:51:11: error: ‘::max_align_t’ has not been
> declared
>    using ::max_align_t;
> }}}
>
> This has hit here: #18198, see also
> [https://gcc.gnu.org/gcc-4.9/porting_to.html sage-devel thread]
>
> The workaround suggested by the gcc people appears to work.

New description:

 with gcc 4.9.2, we hit this bug:

 [https://gcc.gnu.org/gcc-4.9/porting_to.html Header <cstddef> changes]
 The <cstddef> header was updated for C++11 support and this breaks some
 libraries which misuse macros meant for internal use by GCC only. For
 instance with GMP versions up to 5.1.3, you may see:
 {{{
 /usr/include/c++/4.9.0/cstddef:51:11: error: ‘::max_align_t’ has not been
 declared
    using ::max_align_t;
 }}}

 This has hit here: #18198, see also [https://groups.google.com/d/msg/sage-
 devel/Tu-egDn-zLw/0S5ouau2J1AJ sage-devel thread]

 The workaround suggested by the gcc people appears to work.

--

Comment (by dimpase):

 (fixed the link to sage-devel)

 my understanding is that upstream is not in hurry to fix this properly, as
 it's not easy.

--
Ticket URL: <http://trac.sagemath.org/ticket/18240#comment:9>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to