From: Hugo Duncan (hugoduncan_at_[hidden])
Date: 2008-03-07 15:52:05
On Fri, 07 Mar 2008, Vladimir Prus wrote:
> Uhm, I don't know what that means, yet. Can you add --debug-loading
> --debug-building
> to bjam command line, see what is done before this error, and report
> that?
OK, that located the problem - thanks - I'll have to remember those
switches...
> (Incidentally, Python port has a much better error reporting, and should
> always report the line in Jamfile that is responsible for an error).
Excellent news. I haven't been following the python port - how would I run
it?
> You go to 'test' directory, copy test-config-example.jam to
> test-config.jam,
> configure your toolset there, and run "python test_all.py"
Patch attached to discriminate between intel and ppc mac. (not tested on
ppc)
I get numerous failures complaining that the test-config.jam file does not
exist (it obviously does). Attached the output if you want to follow this
up.
Thanks,
Hugo
Index: BoostBuild.py
===================================================================
--- BoostBuild.py (revision 43539)
+++ BoostBuild.py (working copy)
@@ -186,7 +186,10 @@
elif os.uname()[0] == 'SunOS':
jam_build_dir = "bin.solaris"
elif os.uname()[0] == 'Darwin':
- jam_build_dir = "bin.macosxppc"
+ if os.uname()[4] == 'i386':
+ jam_build_dir = "bin.macosxx86"
+ else:
+ jam_build_dir = "bin.macosxppc"
elif os.uname()[0] == "AIX":
jam_build_dir = "bin.aix"
elif os.uname()[0] == "IRIX64":