Actually pretty old: https://trac.macports.org/attachment/ticket/44288/issue10910-workaround.txt That patch is 3 years old.
I suggest we follow suite. Not sure what triggered it in sum.cpp. François > On 7/01/2017, at 20:50, Francois Bissey <francois.bis...@canterbury.ac.nz> > wrote: > > I think that may be python 2.7.12 related… We have the following in > local/include/python2.7/pyport.h > > #if defined(__APPLE__) > # define _PY_PORT_CTYPE_UTF8_ISSUE > #endif > > #ifdef _PY_PORT_CTYPE_UTF8_ISSUE > #include <ctype.h> > #include <wctype.h> > #undef isalnum > #define isalnum(c) iswalnum(btowc(c)) > #undef isalpha > #define isalpha(c) iswalpha(btowc(c)) > #undef islower > #define islower(c) iswlower(btowc(c)) > #undef isspace > #define isspace(c) iswspace(btowc(c)) > #undef isupper > #define isupper(c) iswupper(btowc(c)) > #undef tolower > #define tolower(c) towlower(btowc(c)) > #undef toupper > #define toupper(c) towupper(btowc(c)) > #endif > > I haven’t checked if it is new in 2.7.12 but that’s possible. > Commenting that section out enable sum.cpp to be compiled > and the whole of pynac 0.7.3 to be installed on OS X. > > François > > >> On 7/01/2017, at 20:08, Francois Bissey <francois.bis...@canterbury.ac.nz> >> wrote: >> >> OK the bug from bugzilla is orthogonal to the toupper/tolower issue >> at hand which seems to be a clash between C++ methods and libc symbols. >> May be a macro is throwing confusion. I’ll see if I can find something >> before >> signing off for the next week. >> >>> On 7/01/2017, at 19:34, Francois Bissey <francois.bis...@canterbury.ac.nz> >>> wrote: >>> >>> Right! I said Justin but it was your log I inspected. >>> >>>> On 7/01/2017, at 19:30, John H Palmieri <jhpalmier...@gmail.com> wrote: >>>> >>>> In case anyone has time to look at it, I posted a link to my pynac log at >>>> #22136. >>> >>> >>> This email may be confidential and subject to legal privilege, it may >>> not reflect the views of the University of Canterbury, and it is not >>> guaranteed to be virus free. If you are not an intended recipient, >>> please notify the sender immediately and erase all copies of the message >>> and any attachments. >>> >>> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more >>> information. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "sage-release" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to sage-release+unsubscr...@googlegroups.com. >>> To post to this group, send email to sage-release@googlegroups.com. >>> Visit this group at https://groups.google.com/group/sage-release. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-release" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-release+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-release@googlegroups.com. >> Visit this group at https://groups.google.com/group/sage-release. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
