#35982: qt4-mac & Qt4 portgroup: clang spec for qmake -------------------------------------+-------------------------------- Reporter: mojca.miklavec.lists@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: qt4-mac | -------------------------------------+-------------------------------- Comment (by mojca@…): The main "problem" is that programs using qmake don't respect MacPorts' compiler settings. There is no special need to actually provide the spec file, but I thought that this would be the easiest solution. The file {{{/opt/local/share/qt4/mkspecs/macx-llvm/qmake.conf}}} is very short and simple (ok, I don't understand what all those compiler flags mean). It includes a couple of other conf files (like {{{common/llvm.conf}}}), but all of them are relatively straightforward. I just checked the sources though (see r97316). It seems that Ryan added {{{reinplace}}} on the generated Makefile to fix the choice of the compiler: {{{ post-configure { # For some reason the Makefile qmake generates hardcodes the compiler # that qt4-mac was made with as the one used to build lionsupport.o. # Replace it with $(CC) which we set up for the correct compiler and # -arch flags with the build.args below. reinplace -E "/-o build\\/lionsupport.o/s/^(\[\[:space:\]\]+)\[^\[:space:\]\]+/\\1\\$\\(CC\\)/" ${worksrcpath}/Makefile } }}} (To explain the ''For some reason'': qmake always hardcodes the compiler. Compiler can be switched by using a different spec file, but there might be other options I'm not aware of.) Given that a workaround has been found, that version 5 with a fix is out and if no other ports have a problem with this, maybe you could close the ticket as "won't fix". -- Ticket URL: <https://trac.macports.org/ticket/35982#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS