Re: Compiler name baked into our packages

2012-10-05 Thread Ryan Schmidt
On Oct 5, 2012, at 07:03, Jeremy Lavergne wrote: > We don't really need more than one buildbot per OS: we simply restrict what > we build to the most current free version of Xcode for each OS. That would be another good thing to do, but we don't do it currently. Our Lion buildbot has not been

Re: Compiler name baked into our packages

2012-10-05 Thread Bradley Giesbrecht
On Oct 5, 2012, at 6:38 AM, Jeremy Lavergne wrote: >> Umm, I thought XCode 4.2, specifically, was generally considered to be >> less-than-optimal (aka buggy)? > > That too. > > Xcode 4.2 isn't available for Snow Leopard except for paid accounts--it > really shouldn't even be considered. I be

Re: Compiler name baked into our packages

2012-10-05 Thread Blair Zajac
Regards, Blair On Oct 5, 2012, at 2:46 AM, Ryan Schmidt wrote: > 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.

Re: Compiler name baked into our packages

2012-10-05 Thread Joshua Root
On 2012-10-5 19:46 , Ryan Schmidt wrote: > 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 build

Re: Compiler name baked into our packages

2012-10-05 Thread Jeremy Lavergne
> Umm, I thought XCode 4.2, specifically, was generally considered to be > less-than-optimal (aka buggy)? That too. Xcode 4.2 isn't available for Snow Leopard except for paid accounts--it really shouldn't even be considered. ___ macports-dev mailing

Re: Compiler name baked into our packages

2012-10-05 Thread Craig Treleaven
At 8:03 AM -0400 10/5/12, Jeremy Lavergne wrote: > 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. We don't really need more than one buildbot per OS: we simply restrict what we b

Re: Compiler name baked into our packages

2012-10-05 Thread Jeremy Lavergne
> 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. We don't really need more than one buildbot per OS: we simply restrict what we build to the most current free version of Xcode f

Compiler name baked into our packages

2012-10-05 Thread 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 fo