Opened 18 months ago

Closed 18 months ago

Last modified 18 months ago

#65984 closed defect (fixed)

py310-libxml2 @2.10.2: Build fails on G4/PPC 10.5.8: libxml2-py.c:196: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘PyObject’

Reported by: xanda-escuyer (xanda) Owned by: kencu (Ken)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc:
Port: py310-libxml2

Description 

:info:build libxml2-py.c:196: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘PyObject’

Build fails with the above error message.

Attachments (1)

py310-libxml2-main.log​ (62.0 KB) - added by xanda-escuyer (xanda) 18 months ago.
Build main.log

Download all attachments as: .zip

Change History (5)

Changed 18 months ago by xanda-escuyer (xanda)

Attachment: py310-libxml2-main.log​ added

Build main.log

comment:1 Changed 18 months ago by kencu (Ken)

this worked -- just a typo I think: 

$ cat patch-py-libxml-deprecation-typo.diff
--- libxml_wrap.h.orig	2022-10-12 17:40:56.000000000 -0700
+++ libxml_wrap.h	2022-10-12 17:41:04.000000000 -0700
@@ -71,7 +71,7 @@
 #define XML_POP_WARNINGS \
     _Pragma("GCC diagnostic pop")
 #else
-#define XML_IGNORE_PEDANTIC_WARNINGS
+#define XML_IGNORE_DEPRECATION_WARNINGS
 #define XML_POP_WARNINGS
 #endif
Last edited 18 months ago by kencu (Ken) (previous) (diff)

comment:2 Changed 18 months ago by kencu (Ken)

Summary: Build fails on G4/PPC 10.5.8: libxml2-py.c:196: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘PyObject’ → py310-libxml2 @2.10.2: Build fails on G4/PPC 10.5.8: libxml2-py.c:196: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘PyObject’

comment:3 Changed 18 months ago by kencu (Ken)

Owner: set to kencu
Resolution: → fixed
Status: new → closed

In 3a29566610b022445114eec74cd1092df982a7d9/macports-ports (master):

py-libxml2: fix build with older gcc compilers

closes: #65984

comment:4 Changed 18 months ago by kencu (Ken)

this issue has already been fixed upstream by ​https://gitlab.gnome.org/GNOME/libxml2/-/commit/0d9012585926d6dc0f9bf563b8302c0f2e54876c which will come out in the next version update

Note: See TracTickets for help on using tickets.