Re: Building Boost on OS/2 with Boost Build V2

From: krda79 (krda79_at_[hidden])
Date: 2004-10-01 08:24:49

--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> 
> It means that Jamfile.v2 at libs/filesystem/build refers to a file
called 
> 'exception.cpp', which can't be found. Do you have that file in the 
> libs/filesystem/src directory? 

Yes, it's there.

> If yes, then I think something wrong in path.jam for OS/2. I'd
suggest two 
> ideas:

I copied the two rules make-OS2 and native-OS2 in path.jam just from
*-NT. I think this is the right way because OS/2 uses the same model
of naming paths.

> 1. Try current Boost CVS. We did not added support for OS/2, but it
would be 
> simpler to find the bug

I got it.

> 2. Run "bjam --v2 -d+5". That will produce a long output. Find the last 
> invocation of the GLOB function, and tell me the parameters. The
question is 
> whether V2 passes wrong argument to GLOB, or GLOB is broken on OS/2.

The last invocation of GLOB has the parameter
'libs\filesystem\build\convenience.cpp'.
Here I copied the part of exception.cpp which fails with the
resolvation of the target-id.

>>>>
/CD/BackupCD/Programming/boost_cvs/boost/tools/build/v2/util\path.jam:198:>>>>|>
>>>|>>>>|>>>>|>>>>|>>>>|>> GLOB libs\filesystem\build\exception.cpp :
[Jj]amfile
.v2
/CD/BackupCD/Programming/boost_cvs/boost/tools/build/v2/util\path.jam:198:>>>>|>
>>>|>>>>|>>>>|>>>>|>>>>|>> sequence.transform make :
/CD/BackupCD/Programming/boost_cvs/boost/tools/build/v2/util\sequence.jam:38:>>>
>|>>>>|>>>>|>>>>|>>>>|>>>>|>>>> CALLER_MODULE
/CD/BackupCD/Programming/boost_cvs/boost/tools/build/v2/util\sequence.jam:38:>>>
>|>>>>|>>>>|>>>>|>>>>|>>>>|>>>> local caller = path
/CD/BackupCD/Programming/boost_cvs/boost/tools/build/v2/util\sequence.jam:39:>>>
>|>>>>|>>>>|>>>>|>>>>|>>>>|>>>> local result =
/CD/BackupCD/Programming/boost_cvs/boost/tools/build/v2/util\path.jam:198:>>>>|>
>>>|>>>>|>>>>|>>>>|>>>>|>> set result +=
<<<<<

What does the GLOB function?

The idea of working behind (B)JAM is just a little bit opaque to me.
It's a very complex but powerful utility.

While compiling BJAM.EXE again I found a problem which maybe is the
cause. JAM0.exe says: 'don't know how to make modules/set.c'. As a
work-around I replaced the slashs in 'jam.source = [...] modules/set.c
[...]' in build.jam with backslashs.

In addition I have to use fileunix.c instead of fileos2.c.

Thank you for your help.

cu
Daniel