While editing the Jamfile to narrow the scope of error, I noticed that this was because no --home option was given. Once I gave that option it compiled like charm.
It was foolish of me not to give the option when README said so. Actually initially I had downloaded the zip file from bgl website which is out-of-date. They should really remove that. It was trying to make that project work that muddled up things.


Anyways I really do appreciate your time and thanks for helping.


-Sandeep


2008/5/15 Jurko Gospodnetiæ <jurko.gospodnetic@docte.hr>:
  Hi Sandeep.

>   My bad..its python.jam and it is imported  in   Jamfile.v2.
>
> Although I am not all that new to boost I still don't know enough to
> create a minimal project from bgl to reproduce error.

  Hmmm... since this seems to be a problem in the Jamfile parsing
phase, simply remove all the targets and leave only your call to the
python.get-python-interpreter rule :-)) (together with any necessary
imports).


> But hopefully this should give some idea.
>
> bjam fails with following additional message
> $(BOOST_ROOT)tools/build/v2/build/project.jam:313: in load-jamfile
> $(BOOST_ROOT)tools/build/v2/build/project.jam:63: in load
> ...
> ...
> $(BOOST_ROOT)tools/build/v2//boost-build.jam:8: in module scope
>
> This seems to be list of jam files that bjam searched for while looking
> for python.get-python-interpreter rule.
My guess is that this is simply the current stack dump from where the
error was detected.


> However python.jam is in directory $(BOOST_ROOT)/tools/build/v2/tools/.
> So my guess is that bjam is unable to locate jam files in tools
> subdirectory.

  It should definitely finds files there... simply add your own file
aaa.jam there and write 'import aaa ;' in your Jamfile to test.

  Best regards,
    Jurko Gospodnetiæ

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build