Opened 9 years ago

Closed 8 years ago

#49167 closed defect (wontfix)

py27-gobject3 @3.18.0 does not build on PPC

Reported by: udbraumann Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: py-gobject3

Description

Since clang-3.4 is not functional on PPC systems, for py27-gobject3 (and similar packages, e.g. py34-gobject3) building fails:

...
:info:configure checking whether the /opt/local/bin/clang-mp-3.4 linker (/opt/local/libexec/llvm-3.4/bin/ld) supports shared libraries... yes
:info:configure checking dynamic linker characteristics... clang(74630) malloc: *** error for object 0xa082a708: Non-aligned pointer being freed
...

I will test if a different compiler is working.

Attachments (1)

main.log.gz (37.9 KB) - added by udbraumann 9 years ago.

Download all attachments as: .zip

Change History (10)

Changed 9 years ago by udbraumann

Attachment: main.log.gz added

comment:1 in reply to:  description Changed 9 years ago by udbraumann

This call

sudo port upgrade py27-gobject3 configure.compiler=macports-gcc-5

works! So I wonder, if macports-gcc-5 could be used as standard compiler for py27-gobject3 (and all similar py??-gobject3) instead of macports-clang-3.4?

comment:2 Changed 9 years ago by mf2k (Frank Schima)

Cc: cal@… removed
Owner: changed from macports-tickets@… to cal@…
Port: py-gobject3 added; py27-gobject3 removed

comment:3 Changed 9 years ago by neverpanic (Clemens Lang)

MacPorts GCC should probably be used as standard compiler on all PPC machines… clang doesn't really support them very well.

I'm willing to accept a patch that fixes this, but I don't have a PPC machine and cannot test, so I'm not going to spend time on figuring out what needs to be done myself.

My assumption would be that something along the lines of setting compiler.blacklist to *clang* and adding macports-gcc-5 to compiler.fallback would be the right way to go.

comment:4 in reply to:  3 ; Changed 8 years ago by udbraumann

Replying to cal@…:

MacPorts GCC should probably be used as standard compiler on all PPC machines… clang doesn't really support them very well.

Well, there is no macports clang working on PPC at all! And as gcc-5 works both on PPC and Intel machines, why not taking it?

So my proposition was to replace clang-3.4 with gcc-5 for all platforms, rather than making a ppc-related case distinction.

Thanks!

comment:5 in reply to:  4 Changed 8 years ago by udbraumann

To further clarify my proposition, you might have a look how other python related ports are using gcc5 for building:

$ sudo port deps py27-numpy
Full Name: py27-numpy @1.10.1_1+gfortran
Build Dependencies:   gcc5
Library Dependencies: python27, fftw-3, py27-nose, py27-cython, libgcc

Instead, your preset for building is clang-3.4:

$ sudo port deps py27-gobject3
Full Name: py27-gobject3 @3.18.2_0
Extract Dependencies: xz
Build Dependencies:   pkgconfig, clang-3.4
Library Dependencies: python27, glib2, libffi, py27-cairo, gobject-introspection

According to my tests on 10.5.8 and 10.6.8, macports-gcc-5 is doing the same job for py*-gobject3, and has full PPC support.

comment:6 Changed 8 years ago by neverpanic (Clemens Lang)

Numpy is a special case because it tries very hard to produce optimized code.

GCC 5 is not a suitable compiler choice for modern OS X, but we could certainly change it on older OS X releases. Changing the default across the complete MacPorts system should be discussed at our macports-dev MailingLists first, though.

I'm willing to take a patch that blacklists clang and adds a GCC compiler to compiler.fallback on platforms affected by this issue, but I don't support 10.5.x anymore so I will not work on making these changes.

comment:7 Changed 8 years ago by neverpanic (Clemens Lang)

Owner: changed from cal@… to macports-tickets@…

Unassigning because I no longer maintain py-gobject3.

comment:8 in reply to:  6 Changed 8 years ago by dbevans (David B. Evans)

Replying to cal@…:

Numpy is a special case because it tries very hard to produce optimized code.

GCC 5 is not a suitable compiler choice for modern OS X, but we could certainly change it on older OS X releases. Changing the default across the complete MacPorts system should be discussed at our macports-dev MailingLists first, though.

I'm willing to take a patch that blacklists clang and adds a GCC compiler to compiler.fallback on platforms affected by this issue, but I don't support 10.5.x anymore so I will not work on making these changes.

Closing as won't fix for now but please feel free to reopen if you can provide a patch as specified and agree to maintain it on the effected platforms.

Last edited 8 years ago by dbevans (David B. Evans) (previous) (diff)

comment:9 Changed 8 years ago by dbevans (David B. Evans)

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.