On 2019/06/10 15:04, Charlene Wendling wrote:
> 
> > http://build-failures.rhaalovely.net//sparc64/last/x11/libhandy.log
> > http://build-failures.rhaalovely.net//powerpc/last/x11/libhandy.log
> 
> It's just a COMPILER line missing because it's C11, right? Well it's
> more than this, as once provided it yells: 
> 
> > (more of them)
> > /usr/local/lib/libgtk-3.so.2201.0: undefined reference to 
> > `epoxy_glXQueryExtension'
> > /usr/local/lib/libgdk-3.so.2201.1: undefined reference to 
> > `XcursorImageCreate'
> > /usr/local/lib/libgdk-3.so.2201.1: undefined reference to 
> > `epoxy_glDrawArrays'
> > /usr/local/lib/libpangocairo-1.0.so.3800.1: undefined reference to 
> > `FcDefaultSubstitute'
> > collect2: error: ld returned 1 exit status
> > linking of temporary binary failed: Command '['cc', '-o', 
> > '/usr/ports/pobj/libhandy-0.0.9.1/build-powerpc/tmp-introspectxopgayge/Handy-0.0',
> >  '-O2', '-pipe', 
> > '/usr/ports/pobj/libhandy-0.0.9.1/build-powerpc/tmp-introspectxopgayge/Handy-0.0.o',
> >  '-L.', '-Wl,-rpath,.', '-Wl,--no-as-needed', 
> > '-L/usr/ports/pobj/libhandy-0.0.9.1/build-powerpc/src', 
> > '-Wl,-rpath,/usr/ports/pobj/libhandy-0.0.9.1/build-powerpc/src', 
> > '-L/usr/ports/pobj/libhandy-0.0.9.1/build-powerpc/src', 
> > '-Wl,-rpath,/usr/ports/pobj/libhandy-0.0.9.1/build-powerpc/src', 
> > '-L/usr/local/lib', '-Wl,-rpath,/usr/local/lib', '-lhandy-0.0', 
> > '-lhandy-0.0', '-lintl', '-lglib-2.0', '-lgio-2.0', '-lgobject-2.0', 
> > '-lgmodule-2.0', '-lgtk-3', '-lgdk-3', '-lpangocairo-1.0', '-lpango-1.0', 
> > '-latk-1.0', '-lcairo-gobject', '-lcairo', '-lgdk_pixbuf-2.0', '-lm', 
> > '-L/usr/local/lib', '-Wl,--export-dynamic', '-pthread', '-lgio-2.0', 
> > '-lgobject-2.0', '-lgmodule-2.0', '-lintl', '-lglib-2.0']' returned 
> > non-zero exit status 1
> 
> 
> They're either fontconfig, xcb or other X11-related references, 
> as it lacks X11BASE/lib as a LDFLAG, so i added it. It seems fishy
> to me, but i guess it's yet another base-gcc arch quirk that i don't
> know about ;)

This one doesn't feel all that likely to be a compiler quirk, perhaps
it'sactually related to ld.bfd rather than gcc ... No easy way to test
that theory though, meson + libraries + ld.bfd doesn't work on amd64
and at the moment CLANG_ARCHS == LLD_ARCHS.

Reply via email to