• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Mail Thread Index

Mail Thread Index

  • Date Index
[Prev Page][Next Page]
  • Re: default window arrangement for IB?, Laurence Harris
  • creating bookmarks bar....., Kathryn Tate
  • Re: Guidelines for talking about Xcode 2.5 on this list, Michael Wild
  • Re: [OT} Packaging systems [was: Guidelines for talking about Xcode 2.5 on this list], Michael Wild
    • Re: [OT} Packaging systems [was: Guidelines for talking about Xcode 2.5 on this list], Kyle Sluder
      • Re: [OT} Packaging systems [was: Guidelines for talking about Xcode 2.5 on this list], Shawn Erickson
    • Re: [OT} Packaging systems [was: Guidelines for talking about Xcode 2.5 on this list], Kyle Sluder
  • Re: Distributed build problems - unknown compiler error and not building locally..., Bill Bumgarner
  • err = noErr; // Intel binary (only) crashes here, Robert Purves
    • Re: err = noErr; // Intel binary (only) crashes here, Kyle Sluder
    • <Possible follow-ups>
    • Re: err = noErr; // Intel binary (only) crashes here, Greg Guerin
  • .#_XCSCM_ files?, David Dunham
    • Re: .#_XCSCM_ files?, Tom Naughton
      • Re: .#_XCSCM_ files?, Jack Repenning
        • Re: .#_XCSCM_ files?, David Dunham
  • Oddity when zipping my build folder, Laurence Harris
    • Re: Oddity when zipping my build folder, Fritz Anderson
      • Re: Oddity when zipping my build folder, Laurence Harris
    • <Possible follow-ups>
    • Re: Oddity when zipping my build folder, Matt Neuburg
      • Re: Oddity when zipping my build folder, Laurence Harris
      • Re: Oddity when zipping my build folder, Markus Hitter
  • Help with type_id and fstream, Dale Satterfield
    • Re: Help with type_id and fstream, Rua Haszard Morris
    • Re: Help with type_id and fstream, Jonathan Prescott
    • RE: Help with type_id and fstream, Luca Ciciriello
    • RE: Help with type_id and fstream, Luca Ciciriello
  • Adding Help, Barry
    • Re: Adding Help, Jonathon Mah
      • Re: Adding Help, Barry
        • Re: Adding Help, Laurence Harris
    • Re: Adding Help, Jeff Johnson
      • Re: Adding Help, Laurence Harris
        • Re: Adding Help, Jeff Johnson
          • Re: Adding Help, Laurence Harris
        • Re: Adding Help, Fritz Anderson
  • Re: Using llvm with Xcode, Devang Patel
  • Re: Tricky "inline-assembly/C++ template" issue, Alastair Houghton
  • warning: local declaration hides instance variable, Tron Thomas
    • Re: warning: local declaration hides instance variable, Shawn Erickson
      • Re: warning: local declaration hides instance variable, Tron Thomas
        • Re: warning: local declaration hides instance variable, Shawn Erickson
          • Re: warning: local declaration hides instance variable, Tron Thomas
    • Re: warning: local declaration hides instance variable, Wincent Colaiuta
      • Re: warning: local declaration hides instance variable, Laurence Harris
        • Re: warning: local declaration hides instance variable, Wincent Colaiuta
          • Re: warning: local declaration hides instance variable, Laurence Harris
            • Re: warning: local declaration hides instance variable, Wincent Colaiuta
        • Re: warning: local declaration hides instance variable, Tron Thomas
          • Re: warning: local declaration hides instance variable, Laurence Harris
        • Re: warning: local declaration hides instance variable, Chris Hanson
    • <Possible follow-ups>
    • RE: warning: local declaration hides instance variable, Jeff Laing
      • Re: warning: local declaration hides instance variable, David Dunham
    • RE: warning: local declaration hides instance variable, Jeff Laing
      • Re: warning: local declaration hides instance variable, glenn andreas
  • Getting rid of Obj-C "may not respond to" warning, David Dunham
    • Re: Getting rid of Obj-C "may not respond to" warning, Thomas Engelmeier
    • Re: Getting rid of Obj-C "may not respond to" warning, Rosyna
      • Re: Getting rid of Obj-C "may not respond to" warning, Jayson Adams
    • Re: Getting rid of Obj-C "may not respond to" warning, Alastair Houghton
      • Re: Getting rid of Obj-C "may not respond to" warning, Chris Suter
        • Re: Getting rid of Obj-C "may not respond to" warning, Alastair Houghton
        • Re: Getting rid of Obj-C "may not respond to" warning, David Dunham
  • Re: Distributed build problems - unknown compiler error and not building locally... On Sep 1, 2007, at 11:25 AM, Bill Bumgarner wrote: On Aug 31, 2007, at 4:12 PM, Dave Thorup wrote: On Aug 31, 2007, at 8:26 AM, Ken Worley wrote: On Aug 30, 2007, at 7:08 PM, Dave Thorup wrote: Now, for my second problem, when doing distributed builds only the remote machine is being sent files to compile, my local machine isn't compiling anything. This is verified by checking the DISTCC_HOSTS variable in the Xcode build log. If I turn off distributed builds on the remote machine then it will use the local machine to compile, but that seems to be the only way I can get compiles working on the local machine. The remote machine is a Core Duo iMac while the local Machine is a Quad Mac Pro, so naturally I'd like to be utilizing the local machine as well. From what I understand, this "problem" is actually by design. It's a real pain too if you happen to be working on the fastest mach ine available for building. I hope this will change in later versions. I haven't tried 2.5 yet. distcc requires the source files to effectively be precompiled prior to compilation. This puts a huge amount of potential I/O load and a bit of CPU load on the local system. As a result, the # of local jobs was turned down so that the machine could distribute jobs more efficiently. It sounds like it was turned down too much or a bug has come into play. Please file a bug capturing the symptoms and configuration. From what I gather in the list archives, this was an intentional change between 2.3 and 2.4. Someone complained to DTS and was told that engineering had determined that was the correct behavior. Hopefully, their notion of correct behavior has changed for 2.5...perhaps filing bugs will nudge them in the right direction. Ken -- Ken Worley Software Engineer, Tiberius, Inc., Ken Worley
  • SOLVED: Using Xcode debugger without Xcode project, Dieter Oberkofler
  • -mlong-branch, spsaxena
    • Re: -mlong-branch, Jens Ayton
      • Re: -mlong-branch, spsaxena
        • Re: -mlong-branch, Dave Dribin
    • <Possible follow-ups>
    • Re: -mlong-branch, Greg Guerin
  • printf functions fail with non-ascii characters, William H. Schultz
    • Re: printf functions fail with non-ascii characters, Shawn Erickson
      • Re: printf functions fail with non-ascii characters, William H. Schultz
        • Re: printf functions fail with non-ascii characters, Kyle Sluder
    • Re: printf functions fail with non-ascii characters, Kyle Sluder
    • Re: printf functions fail with non-ascii characters, Fritz Anderson
      • Re: printf functions fail with non-ascii characters, Sean McBride
    • Re: printf functions fail with non-ascii characters, Peter Mulholland
      • Re: printf functions fail with non-ascii characters, Alastair Houghton
        • Re: printf functions fail with non-ascii characters, Shawn Erickson
        • Re[2]: printf functions fail with non-ascii characters, Peter Mulholland
          • Re: printf functions fail with non-ascii characters, Alastair Houghton
            • Re: printf functions fail with non-ascii characters, John H. Jenkins
  • command-line test for 64-bit hardware?, John Reppy
    • Re: command-line test for 64-bit hardware?, Fritz Anderson
      • Re: command-line test for 64-bit hardware?, Fritz Anderson
        • Re: command-line test for 64-bit hardware?, John Reppy
          • Re: command-line test for 64-bit hardware?, Kyle Sluder
            • Re: command-line test for 64-bit hardware?, Shawn Erickson
            • Re: command-line test for 64-bit hardware?, Steven Fisher
            • Re: command-line test for 64-bit hardware?, Jonas Maebe
              • Re: command-line test for 64-bit hardware?, Kyle Sluder
    • <Possible follow-ups>
    • Re: command-line test for 64-bit hardware?, Greg Guerin
    • Re: command-line test for 64-bit hardware?, Kyle Sluder
      • Re: command-line test for 64-bit hardware?, Steve Checkoway
        • Re: command-line test for 64-bit hardware?, Kyle Sluder
          • Re: command-line test for 64-bit hardware?, Steve Checkoway
  • Re: -mlong-branch SOLVED, spsaxena
  • Re: command-line test for 64-bit hardware, Brian Arnold
  • Timestamps, yakov . zaytsev
    • Re: Timestamps, Kyle Sluder