Re: [jamboost] [V2] problems with build-project

From: Jürgen Hunold (hunold_at_[hidden])
Date: 2004-06-18 07:28:08

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Volodya !

On Friday 18 June 2004 10:27, Vladimir Prus wrote:
> Hi Jürgen,

> Ok, I've tried to improve that I getting the following on one
> testcase:
>
> error: Duplicate name of actual target: <pd>hello
> error: previous virtual target { gcc%gcc.link-hello.STAGED_EXE
> { gcc%gcc.compile.c++-hello.OBJ { hello.CPP } } }
> error: created from Jamfile:2
> error: another virtual target { gcc%gcc.link-hello.STAGED_EXE
> { gcc%gcc.compile.c++-hello.OBJ { hello.CPP } } }
> error: created from Jamfile:2
> error: added properties: <debug-symbols>on <inlining>off
> <optimization>off <runtime-debugging>on <variant>debug
> error: removed properties: <debug-symbols>off <define>NDEBUG
> <inlining>full <optimization>speed <runtime-debugging>off
> <variant>release
>
> Which maybe could be formatted better, but at least have move
> information. I've comitted the change just now, and would appreciate
> if you show me the new error message.

It's the same.

/ive/hunold/packages/boost/tools/build/v2/build/virtual-target.jam:830: 
in virtual-target.register-actual-name from module virtual-target
error: Duplicate name of actual target: <pbin>lm_new.o
error: previous virtual target { common%common.copy-lm_new.OBJ 
{ /usr/local/flexlm/v9.2/i86_r9/lm_new.OBJ } }
error: another virtual target { common%common.copy-lm_new.OBJ 
{ /usr/local/flexlm/v9.2/i86_r9/lm_new.OBJ } }
/ive/hunold/packages/boost/tools/build/v2/build/virtual-target.jam:175: 
in actualize-no-scanner from module object(file-target)@13515
/ive/hunold/packages/boost/tools/build/v2/build/virtual-target.jam:110: 
in object(file-target)@13515.actualize from module 
object(file-target)@13515
/ive/hunold/packages/boost/tools/build/v2/build-system.jam:169: in load 
from module build-system
/ive/hunold/src/../packages/boost/tools/build/v2/kernel/modules.jam:259: 
in import from module modules
/ive/hunold/src/../packages/boost/tools/build/v2/kernel/bootstrap.jam:120: 
in boost-build from module
/ive/hunold/src/boost-build.jam:1: in module scope from module

So, I think the the same target is pulled from two sub-projects and then 
bjam fails to recognise that they are identical. Your new test + 
message at line 816 does definitely not trigger.

Happy Weekend !

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA0t/bljbJ/LLrxrYRAjPDAJ4mtNXw9pd7i48nacQjYG+Dp79CSACfcWV+
c4oRc4rVE3OlHUCeUcNGff0=
=zoyu
-----END PGP SIGNATURE-----