Re: V2 testing

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-09-09 06:53:27

J?rgen Hunold wrote:

>> That's great. That platform is troublesome, but never was regularly
>> tested.
> 
> Yes, I know. I'd like to use cygwin shell instead of cmd.exe, so I'll
> keep testing ;-)

Do you use cmd.exe at the moment?

>> > Please find the output of jam_src/build.sh and the output of
>> > test/test_all.py attached.
>> >
>> > The problem seems that the tests look for bin.posix directory
>> > whereas build.sh generates bin.win32x86 directory.
> 
>> Could you run
>>
>> ./bootstrap.gcc/jam0 -f-
>>
>> then type
>>
>> ECHO $(OS) ;
>> ECHO $(OSPLAT) ;
>>
>> and then type "Ctrl-Z". It looks like OS is set to win32 and I can't
>> understand how it can be.
> 
> I don't get any output from jam0 when doing this. What should I expect ?

I expected something like

win32
x86

If you did it from cygwin shell, you probably should use "Ctrl-D" instead of
"Ctrl-Z".

>> Also, make sure that OS is not set in
>> environment, by running:
>>
>> echo $(OS) ;
> 
> But when doing a "set | grep OS" I get
> 
> BOOST_BUILD_PATH='e:\libraries\boost_cvs\tools\build\v2\kernel'
> BOOST_ROOT='e:\libraries\boost_cvs'
> HOSTNAME=railsys
> HOSTTYPE=i686
> OS=win32
> OS2LIBPATH='C:\WINNT\system32\os2\dll;'
> OSTYPE=cygwin
> 
> so it seems my cygwin installation sets OS=win32.

Could you try unsetting this variable? If the tests work OK in the case,
I'll swap the order of calls in

/*
* Jam defined variables OS, OSPLAT
*/
var_defines( othersyms );

var_defines( use_environ );

so that env vars don't clobber 'OS' and 'OSPLAT'.

- Volodya