Opened 7 years ago

Last modified 5 years ago

#39780 new defect

py3{2,3}-shiboken: build failure, members of libapiextractor.a have no symbols

Reported by: watsodw Owned by: mamoll (Mark Moll)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: petrrr
Port: py-shiboken

Description

libapiextractor.a has no symbols

Attachments (2)

py33-shiboken_log.log (1.6 MB) - added by watsodw 7 years ago.
py32-shiboken_log.log (1.6 MB) - added by watsodw 7 years ago.

Change History (10)

Changed 7 years ago by watsodw

Attachment: py33-shiboken_log.log added

Changed 7 years ago by watsodw

Attachment: py32-shiboken_log.log added

comment:1 Changed 7 years ago by larryv (Lawrence Velázquez)

Cc: mmoll@… removed
Owner: changed from macports-tickets@… to mmoll@…
Port: py-shiboken added; shiboken removed
Summary: py32-,py33-shiboken fail upgrade or installpy3{2,3}-shiboken: build failure, members of libapiextractor.a have no symbols

comment:2 Changed 7 years ago by mamoll (Mark Moll)

The python include dir is wrong. It should be /opt/macports/Library/Frameworks/Python.framework/Versions/3.3/include/python3.3m instead of /opt/macports/Library/Frameworks/Python.framework/Versions/3.3/include/python3.3. Does the latter directory exist? If so, that will confuse the python port group.

comment:3 Changed 7 years ago by mamoll (Mark Moll)

It's also curious that the pre-built port isn't just downloaded from http://packages.macports.org/py33-shiboken/.

comment:4 Changed 7 years ago by watsodw

Both of those directories exit, both for py32 and py33. In the /opt/macports/Library/Frameworks/Python.framework/Versions/3.*/include/python3.* directory is only one file, sip.h. If I move that file to the */python3.*m directory, the build still fails.

comment:5 Changed 7 years ago by mamoll (Mark Moll)

Did you remove the directory /opt/macports/Library/Frameworks/Python.framework/Versions/3.3/include/python3.3?

comment:6 Changed 7 years ago by watsodw

I moved it out of the way and moved the file sip.h to the */python3.*m directory, but the build still failed with the same error.

comment:7 Changed 7 years ago by mamoll (Mark Moll)

Can you try this and attach the main.log file if it still fails:

sudo port clean py33-shiboken
sudo port install py33-shiboken

comment:8 Changed 5 years ago by petrrr

Cc: petr@… added

Cc Me!

Note: See TracTickets for help on using tickets.