Compiler name baked into our packages

[Ryan Schmidt]

We continue to receive bug reports from users on Snow Leopard with Xcode 4.2 (and therefore no /usr/bin/gcc-4.2), who receive a package from our packages server that was built by the Snow Leopard buildbot which has Xcode 3.2.6 (and therefore builds things using /usr/bin/gcc-4.2), specifically for ports that bake the compiler name into themselves, such as perl5.12:

https://trac.macports.org/ticket/36474

A suggestion made in that ticket is that we should disable the use of pre-built packages for such ports as we discover them. That could work, unfortunately one of the ports so affected is qt4-mac, which takes so long to compile that it would be awful to disable binary packages just for this reason.


Another idea would be to encode the compiler name and/or the Xcode version into the package filename. I suggested that six months ago but didn't receive any response:

http://lists.macosforge.org/pipermail/macports-dev/2012-April/018689.html

But if we restrict MacPorts to fetch only packages built of the same compiler and/or Xcode version, then we'd need more buildbots to build those extra packages.