Odd, BleuScorer.cpp is listed both in mert_lib and this thing:

lib bleu_lib : BleuScorer.cpp mert_lib : : : <include>. ;

So bjam was getting angry because it was being compiled twice into the 
same shared library.  Looks like somebody was trying to export the 
<include>. dependency for only that file.  But all of mert appears to 
have this requirement, so I've just added the <include>. to the mert_lib 
target.

Also there were some dependencies that gcc likes to have explicitly, so 
I have added those.

Now works for me.

Kenneth

On 11/07/12 19:51, Wilker Aziz wrote:
> Hello,
>
> I am not yet familiar with bjam, so please excuse me if I am missing
> something obvious.
> I am trying to compile Moses with *link=shared* and I am getting the
> error below.
> In case it matters, I managed to compile with the very same command line
> some revisions ago.
>
> ./bjam -a -j4 link=shared
> warning: No toolsets are configured.
> warning: Configuring default toolset "gcc".
> warning: If the default is wrong, your build may not work correctly.
> warning: Use the "toolset=xxxxx" option to override our guess.
> warning: For more configuration options, please consult
> warning:
> http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
> /usr/share/boost-build/build/virtual-target.jam:1079: in
> virtual-target.register-actual-name from module virtual-target
> error: Duplicate name of actual target:
> <pmert/bin/gcc-4.6/release/debug-symbols-on/threading-multi>BleuScorer.o
> error: previous virtual target { gcc%gcc.compile.c++-BleuScorer.o.OBJ {
> BleuScorer.cpp.CPP } }
> error: created from mert/mert_lib
> error: another virtual target { gcc%gcc.compile.c++-BleuScorer.o.OBJ {
> BleuScorer.cpp.CPP } }
> error: created from mert/bleu_lib
> error: added properties:
> <xdll-path>/media/Data/tools/moses/mosesdecoder/mert/bin/gcc-4.6/release/debug-symbols-on/threading-multi
> error: removed properties: none
> /usr/share/boost-build/build/virtual-target.jam:490: in
> actualize-no-scanner from module object(file-target)@2120
> /usr/share/boost-build/build/virtual-target.jam:135: in
> object(file-target)@2120.actualize from module object(file-target)@2120
> /usr/share/boost-build/build/virtual-target.jam:811: in
> actualize-source-type from module object(action)@2123
> /usr/share/boost-build/build/virtual-target.jam:832: in
> actualize-sources from module object(action)@2123
> /usr/share/boost-build/build/virtual-target.jam:759: in
> object(action)@2123.actualize from module object(action)@2123
> /usr/share/boost-build/build/virtual-target.jam:311: in actualize-action
> from module object(file-target)@2124
> /usr/share/boost-build/build/virtual-target.jam:499: in
> actualize-no-scanner from module object(file-target)@2124
> /usr/share/boost-build/build/virtual-target.jam:135: in
> object(file-target)@2124.actualize from module object(file-target)@2124
> /usr/share/boost-build/build-system.jam:748: in load from module
> build-system
> /usr/share/boost-build/kernel/modules.jam:283: in import from module modules
> /usr/share/boost-build/kernel/bootstrap.jam:142: in boost-build from module
> /usr/share/boost-build/boost-build.jam:8: in module scope from module
>
> Regards,
>
> Wilker.
>
>
> _______________________________________________
> Moses-support mailing list
> [email protected]
> http://mailman.mit.edu/mailman/listinfo/moses-support
_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to