Richard Hadsell wrote:

Is there anyone who can look at this? Is bjam just unusable on tru64cxx? If so, take it out of the docs (for Boost, too).

Richard Hadsell wrote:

...

I am trying to upgrade from Boost 1.30.0 to 1.31.0. I am unable to build bjam from the source in tools/build/jam_src:

67% build.sh tru64cxx ### ### Using 'tru64cxx' toolset. ### rm -rf bootstrap.tru64cxx mkdir bootstrap.tru64cxx cc -o bootstrap.tru64cxx/jam0 command.c compile.c execnt.c execunix.c execvms.c expand.c filent.c fileos2.c fileunix.c filevms.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c command.c: compile.c: [snip] modules/sequence.c: ./bootstrap.tru64cxx/jam0 -f build.jam --toolset=tru64cxx --toolset-root= clean ...found 1 target... ...updating 1 target... ...updated 1 target... ./bootstrap.tru64cxx/jam0 -f build.jam --toolset=tru64cxx --toolset-root= don't know how to make ...found 1 target... ...can't find 1 target...

I know someone had it working once upon a time. I would like to see it working. But the above is insufficient information for figuring out what is going wrong :-( Could you try running the last command manually and add a "-d5" option to get some debug output... ./bootstrap.tru64cxx/jam0 -f build.jam --toolset=tru64cxx -d5 -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq

Richard Hadsell wrote:

Rene Rivera wrote:

...

I know someone had it working once upon a time. I would like to see it working. But the above is insufficient information for figuring out what is going wrong :-(

Could you try running the last command manually and add a "-d5" option to get some debug output...

./bootstrap.tru64cxx/jam0 -f build.jam --toolset=tru64cxx -d5

Actually, this command seems to have built bjam correctly. Although build.sh echoed the line './bootstrap.tru64cxx/jam0 -f build.jam --toolset=tru64cxx --toolset-root=', it apparently didn't execute it. When I run that command after build.sh quits, it finishes the build.

Do you still want me to send the debug output from this command?

No. Given what you just said I have a good idea what could be going wrong. Specifically there's an extra argument that is passed in which normally is empty but is passed as "". SO either the shell or bjam itself is failing to handle that. The shell is the likelier culprit. I'll make some changes to the build.sh to account for this. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq