Re: next problem
Re: next problem
- Subject: Re: next problem
- From: Greg Guerin <email@hidden>
- Date: Tue, 19 Jun 2007 18:23:09 -0700
David Goldsmith wrote:
>Hi! I'm getting the following compiler error:
What is the compiler command-line that causes the error?
What exported or environment variables have been set or changed prior to
invoking the command-line?
To print env vars, nicely sorted:
printenv | sort
I suggest pasting the failing command-line and the sorted env-vars into an
email and sending it to the list.
In general, seeing the command-line that caused the failure is just about
as important as seeing what the error itself is. For complex commands (and
g++ certainly qualifies), it provides the all-important context in which
the error occurs. Without knowing the context, all anyone can do is
randomly guess what caused the error, and then randomly guess about what
might fix it.
>I googled stray '\202' in program and found a site indicating that this
>error crops up when the file in question isn't ascii. Sure enough, less
>says the file /usr/bin/locale is binary. What gives?
It's an executable. Specifically, a Mach-O binary (probably fat Mach-O,
unless you're on a PPC Mac). The command itself is described via:
man 1 locale
You may find the 'file' command useful:
file /usr/bin/locale
It's a little more informative than viewing the bytes with 'less'.
-- 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