Re: jam fails with exit status 1.
Re: jam fails with exit status 1.
- Subject: Re: jam fails with exit status 1.
- From: Rosyna <email@hidden>
- Date: Mon, 24 Oct 2005 11:28:41 -0700
Ack, at 10/24/05, Rick Ballard said:
On Oct 23, 2005, at 9:48 PM, Rosyna wrote:
I'm trying to compile a project I haven't compiled in about a month
and I'm getting an error:
Command jam failed with exit code 1
But the build log shows no information about the failure other than
the command passed to jam. Is there any way to find out more
information on the failure? Using the "latest" Xcode.
The -d# switch to jam controls the debug output level, where # is a
number from 1-9. If you're not getting any useful debugging info in
the build log, you could try running the same jam invocation from
the command line that Xcode runs but with a higher -d level.
Depending on what level you choose, this could give you a very large
amount of output, but it should give you a good idea of what's going
wrong.
It seems the log about jam was spurious. It was appearing when the
regular build failed because Xcode couldn't find the header (for some
odd reason, I had to explicitly add the header search paths to the
project if they weren't in the same folder as the project, even
though this was never necessary before).
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
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