Feature redefinition problem

From: abingham2 (abingham_at_[hidden])
Date: 2003-10-13 09:05:37

I've noticed what seems to be a bug related to the creation of
features. I declare a feature in one Jamfile. When I then execute bjam
from my project root directory, everything seems to go OK. 

However, if I execute bjam from the directory containing the Jamfile
in which the feature is defined, bjam tells me that:

/usr/local/boost-build/new/feature.jam:125: in feature from module
feature
error: feature already defined:
in feature declaration:
feature "enable-my-feature" : "off" "on" : "propagated"
"link-incompatible"
Jamfile:6: in modules.load from module Jamfile<.>
/usr/local/boost-build/new/project.jam:285: in load-jamfile from
module project
/usr/local/boost-build/new/project.jam:69: in project.load from
module project
/usr/local/boost-build/build-system.jam:74: in load from module
build-system
/usr/local/boost-build/kernel/modules.jam:259: in import from
module modules
/usr/local/boost-build/kernel/bootstrap.jam:122: in boost-build
from module
/proj/jam/boost-build.jam:1: in module scope from module

So, it seems that bjam gets confused when it is executed on a non-root
directory. It doesn't seem to matter how I initiate the build; that
is, I can request the target via its 'use-project' name or its fully
qualified name...it's doesn't seem to matter.

Is this a known bug? Or am I perhaps doing something wrong?

Austin