• 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
Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)


  • Subject: Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)
  • From: Greg Guerin <email@hidden>
  • Date: Mon, 21 Jul 2008 22:44:12 -0700

Jim Fridlund wrote:

PATH=${PATH}:/opt/local/bin:/opt/local/sbin

Suppose that the 'iconv' in one of those /opt/local bin dirs is causing the problem for some reason. However, that value of PATH implies that /usr/bin/iconv will be found first, if PATH initially contain /usr/bin. Therefore, any 'iconv' in a /opt/local bin dir can't be causing the problem, because it won't be executed. Unless, of course, /usr/bin/iconv isn't executable, or /usr/bin isn't initially in PATH. E.g.: there's no /usr/bin/iconv at all, or it exists but isn't executable, or the initial PATH has already been modified from its default, such as by a pre-existing ~/.MacOSX/ environment.plist you don't know about.


You really need to see what Xcode is actually using for PATH and iconv when it does a build. One way to do that is to add a shell script build phase as the first build phase of the malfunctioning target. Add the build phase, then drag it to the top position under the target. In that phase, put these commands:

  printenv | sort
  which iconv
  /usr/bin/iconv --list | sort

Do a build, then look in your detailed build log (build transcript) to see exactly what PATH is, and which iconv is being found, and what its conversions are. If there's no /usr/bin/iconv, the last command will fail, and should stop the build.

To see if there's any difference between the double-clicked Xcode and the shell-launched Xcode, you should do a build under both cases, then use 'diff', FileMerge, or another diff-viewer to see the exact differences. It's possible there's some other env-var difference that's indirectly causing /usr/bin/iconv to fail, even though it's the "right" iconv.

This is just theoretical speculation: I'm not running Xcode 3.1.

  -- GG

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)
  • Next by Date: Problems attaching debugger
  • Previous by thread: Re: Xcode 3.1 builds fails for OS X Cocoa apps (copystrings)
  • Next by thread: C++ question: dynamic_cast
  • Index(es):
    • Date
    • Thread