We should upgrade trunk 10.5 tinderboxes to Xcode 3.1.3 to pick up compiler changes. I'd like to see this in support of bug 501436.
Can we safely build 1.9.1 off of Xcode 3.1.3? If not, we have to split our Mac pool...which would be bad.
I don't think they even mention gcc 4.0 in their release notes: http://www.cocoabuilder.com/archive/message/xcode/2009/6/18/29103 I would be surprised if there were any changes to it.
I don't know of any reason all branches can't build with Xcode 3.1.3. If there are any changes to gcc-4.0 they are almost certainly conservative.
I was informed that this was done already, marked in an "upgrade" section on the wiki. Excellent!
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
Just to be clear: we have Xcode 3.1 on the machines, not 3.1.3: bm-xserve18:Contents cltbld$ cat /Developer/Applications/Xcode.app/Contents/version.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>BuildVersion</key> <string>1</string> <key>CFBundleShortVersionString</key> <string>3.1</string> <key>CFBundleVersion</key> <string>1099</string> <key>ProjectName</key> <string>DevToolsIDE</string> <key>SourceVersion</key> <string>10990000</string> </dict> </plist> bm-xserve18:Contents cltbld$ gcc --version i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5484) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. bm-xserve18:Contents cltbld$ gcc-4.2 --version i686-apple-darwin9-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5564) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.