#32395: gst-plugins-gl 0.10.2 i386 build fail w/ possible solution --------------------------------------+------------------------------------- Reporter: reid@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: duplicate | Keywords: Port: gst-plugins-gl | --------------------------------------+------------------------------------- Changes (by ryandesign@…): * cc: ryandesign@…, rmstonecipher@… (added) * status: new => closed * resolution: => duplicate * port: => gst-plugins-gl Old description:

It was gstglwindow_cocoa.m -> libgstgl_0.10_la-gstglwindow_cocoa.o (x86_64) that was causing problems. Adding this did I think:

if { $build_arch == "i386" } { #configure.env-append "GST_CFLAGS=-arch ${build_arch}" configure.cflags-append "-arch ${build_arch}" configure.cppflags-append "-arch ${build_arch}" configure.cxxflags-append "-arch ${build_arch}" }

New description: It was gstglwindow_cocoa.m -> libgstgl_0.10_la-gstglwindow_cocoa.o (x86_64) that was causing problems. Adding this did I think: {{{ if { $build_arch == "i386" } { #configure.env-append "GST_CFLAGS=-arch ${build_arch}" configure.cflags-append "-arch ${build_arch}" configure.cppflags-append "-arch ${build_arch}" configure.cxxflags-append "-arch ${build_arch}" } }}} -- Comment: Please use WikiFormatting, fill in the Port field, and Cc the maintainer of that port. This "solution" seems strange. Why would adding the `-arch` flag only be needed for i386? Why not for the three other archs we support? MacPorts already adds `-arch` flags to CFLAGS, CXXFLAGS, LDFLAGS for you, for all archs, and they shouldn't be necessary in CPPFLAGS. This looks like a duplicate of #27898. -- Ticket URL: <https://trac.macports.org/ticket/32395#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS