Re: [Boost-build] Library_status

Subject: Re: [Boost-build] Library_status
From: Robert Ramey (ramey_at_[hidden])
Date: 2016-01-25 14:16:23

On 1/25/16 10:55 AM, Vladimir Prus wrote:
> On 25-Jan-16 7:58 AM, Robert Ramey wrote:
>> Having trouble getting visibility just right for the serialization
>> library by following the online testing matrix, I
>> resolved to fire up my ancient xp machine with msvc 8.0 in order to
>> run the serialization library tests locally.
>>
>> a) use git to clone boost to the laptop OK
>> b) use git to clone boost/regression into the appropriate place in the
>> modular-boost directory. OK
>> c) build regression/build b2 - OK
>> d) run b2  ... >b2.log - seemed to work OK
>> e) try to run process_jam_log got unexpected message:
>>
>> process_jam_log [options ...] and a help message.
>>
>> f) So I checked the index.html page under library status.  Now I
>> realized it changed alot lately in that it runs b2 |
>> process_jam_long library_status.  That is i combines the functionaly
>> of b2, process_jam_log and library_status into one
>> (large?) program.  Leaving aside the question of the merit of this
>> idea - I just soldered on an invoked library_status
>> to display the help message.
>>
>> I get the same message I get above - that is:
>>
>> process_jam_log [options ...] and a help message.
>>
>> What do I have to do to make this work?
>
> Robert,
>
> whatever changes to process_jam_log were not done by me, so I can't be
> very helpful, but maybe it would help if
> you report what command line you have used in step (e)?

Note I'm using cygwin bash shell.  I don't know if it makes a difference 
but BOOST_ROOT=/cygdrive/c/modular-boost

I tried the following:

process_jam_log --input-file b2.log

the program seems to wait for standard input as it response to the 
terminal.  When I hit ^D it ends without a message.

process_jam_log <b2.log

I get the help message.

So it seems that something is amiss as to hookup to the standard input 
or something.  I did test a number of re-direction commands on my shell 
like cat <b2.log and this seems to work OK so I'm thinking it's 
something in the build of of the process_jam_log and library_status.

FWIW invoking library_status produces the same behavior.  For some 
reason these programs have been rolled into one.

Robert Ramey