[V2] problems with nearly empty Jamfiles

From: Jürgen Hunold (hunold+lists.Boost_at_[hidden])
Date: 2003-02-26 14:23:10

Hi !

I've encountered a strange problem with "empty" Jamfiles.
Please find a simple test case attached.
Extract, "cd bjam/main" and run bjam --v2. Works as expected.
Then try to run
bjam --v2 release debug-symbols=on stdlib=stlport threading=multi hardcode-dll-paths=true
This should result in:

hunold_at_stofi:~/tests/bjam/main> bjam --v2 release debug-symbols=on stdlib=stlport threading=multi hardcode-dll-paths=true
/home/hunold/packages/boost/tools/build/new/project.jam:532: in project.attribute
warning: rulename $($(project).attributes).get expands to empty string
/home/hunold/packages/boost/tools/build/new/targets.jam:151: in object(project-target)@4.direct-build-request
/home/hunold/packages/boost/tools/build/new/targets.jam:152: in object(project-target)@3.direct-build-request
/home/hunold/packages/boost/tools/build/new/build-system.jam:123: in load
/home/hunold/packages/boost/tools/build/new/modules.jam:171: in import
/home/hunold/packages/boost/tools/build/new/bootstrap.jam:41: in boost-build
/home/hunold/tests/bjam/main/boost-build.jam:10: in module scope
/home/hunold/packages/boost/tools/build/new/targets.jam:151: in object(project-target)@4.direct-build-request
*** argument error
* rule project.target ( location )
* called with: ( )
* missing argument location
/home/hunold/packages/boost/tools/build/new/project.jam:538:see definition of rule 'project.target' being called
/home/hunold/packages/boost/tools/build/new/targets.jam:152: in object(project-target)@3.direct-build-request
/home/hunold/packages/boost/tools/build/new/build-system.jam:123: in load
/home/hunold/packages/boost/tools/build/new/modules.jam:171: in import
/home/hunold/packages/boost/tools/build/new/bootstrap.jam:41: in boost-build
/home/hunold/tests/bjam/main/boost-build.jam:10: in module scope

The Jamfile in directory "empty" simply declares a project empty and tells 
bjam to build-project "real-dir". 

If I "cd bjam/main/empty" and run the full bjam command, everything works as expected: 
The release version with debug-symbols is build.

Can someone take a look at this strange behaviour ?
Or drop me note on how to read the error message. 
The problem I had is that the error message does not even mention the offending Jamfile...

Yours,

Jürgen

-- 
* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] ! www.ive.uni-hannover.de
 --Boundary-00=_eQRX+/JmNoIWqra Content-Type: application/x-tgz;
name="bjam.tar.gz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bjam.tar.gz"
[Attachment content not displayed.] --Boundary-00=_eQRX+/JmNoIWqra--