Re: [Boost-build] Anyone know what's up with bug #7212?

Subject: Re: [Boost-build] Anyone know what's up with bug #7212?
From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2012-08-24 12:26:14

   Hi.

> https://svn.boost.org/trac/boost/ticket/7212
>
> Someone is getting an error out of bjam on Linux:
> 	/tools/build/v2/kernel/modules.jam:326: in boost-build import error: length of source and target rule name lists don't match!

   I remember someone once asking me about something like this - here's 
a response I gave them in a personal e-mail message (never got any 
response back nor did I see him post a question to any of the Boost 
mailing lists):

>> I have used the following commands to install Boost  but i am
>> getting the following error :-
>>
>> [priyanka_at_NGS boost_1_50_0]$ ./bootstrap.sh
>> Building Boost.Build engine with toolset gcc...
>> tools/build/v2/engine/bin.linuxx86_64/b2
>> Detecting Python version... 2.7
>> Detecting Python root... /usr
>> ...
>>
>> [priyanka_at_NGS boost_1_50_0]$ ./bjam --prefix= /~/Downloads
>> link=static runtime-link=static stage install
>> /home/priyanka/Downloads/boost_1_50_0/tools/build/v2/kernel/modules.jam:326:
>> in boost-build
>> import error: length of source and target rule name lists don't
 >> match!
>>      source: peek poke record-binding
>>      target: modules.peek
>> /home/priyanka/Downloads/boost_1_50_0/boost-build.jam:17: in
>> module scope
>
>   And I really do not know how this happened at your site. I checked
> the source code lines listed in your error report and in modules.jam
> there is the following:
>
> local globalize = peek poke record-binding ;
> IMPORT modules : $(globalize) : : modules.$(globalize) ;
>
> which expands to:
>
> IMPORT modules : peek poke record-binding : : modules.peek
> modules.poke modules.record-binding ;
>
> In your case something seems to cause this to expand to:
>
> IMPORT modules : peek poke record-binding : : modules.peek ;
>
> Try adding some ECHO statements there like:
>
> ECHO /$(globalize)/ ;
> ECHO /modules.$(globalize)/ ;
>
> and see what you get.

   Hopefully someone that can reproduce this issue can report back here 
with some more information, otherwise, I do not see what to do about 
this. I just added a comment to that effect to ticket #7212 as well.

   Hope this helps.

   Best regards,
     Jurko Gospodnetić