macports 2.0.4 breaks the usage of clang on Xcode 4.3.2

[Jack Howarth]

On Sun, Apr 08, 2012 at 12:11:32PM -0400, Jeremy Lavergne wrote:
> > Perhaps MacPorts should consider separate binary repos for 10.4/10.5 and 10.7/10.8. If all
> > of the binaries are built on Snow Leopard, this prevents those binary MacPorts packages from
> > being built against the fortified 10.7 SDK and linked with -pie so that those executables won't
> > leverage ASLR on Lion. This really does represent a security regression introduced by MacPorts
> > 2.0.4.
> 
> The file URLs contain darwin_X to avoid the issue of cross-contamination, and there are separate buildbots for each OS (Snow Leopard builds Snow Leopard, Lion builds Lion).
> 
> I don't understand the issue you're pointing out.
> 

The fact that, on Lion, MacPorts 2.0.4 installs perl/python that defaults to llvm-gcc-4.2 made me
suspect that the binary packages installed on Lion were built with SL. If not, this brings up the
question of why the Lion build bots are on such an old Xcode that they don't default all of the
package builds to clang. Perhaps they should be updated to Xcode 4.3.2 and a bulk rebuild of the
MacPorts package set started.
         Jack