Moses-support Digest, Vol 164, Issue 2

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. Re: [EXT] Re: Error when compiling Moses with xmlrpc-c
support (Hank Kuo)


----------------------------------------------------------------------

Message: 1
Date: Tue, 2 Jun 2020 19:48:18 +0000
From: Hank Kuo <whkuo@mitre.org>
Subject: Re: [Moses-support] [EXT] Re: Error when compiling Moses with
xmlrpc-c support
To: Hieu Hoang <hieuhoang@gmail.com>
Cc: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<MN2PR09MB5482087BA64FE8028AA16B56A78B0@MN2PR09MB5482.namprd09.prod.outlook.com>

Content-Type: text/plain; charset="utf-8"

To answer your questions:

1. Both openssl and libssl-dev have already been installed prior to me building Moses and generating the build.log.gz output.
2. That was a typo on my part, I was already specifying --with-cmph in my bjam command.

Within the bjam build system for Moses, is there a way to explicitly link ssl during the g++ linking stage? This is the linking command that is erroring out during build (extracted from the build.log):

"g++" -L"/usr/include/lib" -L"/usr/include/lib64" -L"/usr/local/lib" -Wl,-rpath-link -Wl,"/usr/include/lib" -Wl,-rpath-link -Wl,"/usr/include/lib64" -Wl,-rpath-link -Wl,"/usr/local/lib" -o "/home/whkuo/mosesdecoder/bin/moses" -Wl,--start-group "moses-cmd/bin/gcc-5.5.0/release/link-static/threading-multi/Main.o" "moses/bin/gcc-5.5.0/release/link-static/threading-multi/libmoses.a" "probingpt/bin/gcc-5.5.0/release/link-static/threading-multi/libprobingpt.a" -Wl,-Bstatic -lboost_filesystem -lboost_iostreams -lz -lbz2 -llzma -lcmph -lxmlrpc_xmltok -lxmlrpc_xmlparse -lxmlrpc_util++ -lxmlrpc_util -lxmlrpc_server_abyss++ -lxmlrpc_server_abyss -lxmlrpc_server++ -lxmlrpc_server -lxmlrpc_abyss++ -lboost_program_options -lboost_serialization -lboost_thread -lboost_system -ltcmalloc_minimal -lxmlrpc -lxmlrpc++ -lxmlrpc_abyss -Wl,-Bdynamic -lSegFault -lrt -Wl,--end-group -pthread

...failed gcc.link /home/whkuo/mosesdecoder/bin/moses...

Basically I?m looking for a way to add ?-lssl? into the g++ command above?

Hank

From: Hieu Hoang <hieuhoang@gmail.com>
Sent: Friday, May 29, 2020 3:31 PM
To: Hank Kuo <whkuo@mitre.org>
Cc: moses-support@mit.edu
Subject: [EXT] Re: [Moses-support] Error when compiling Moses with xmlrpc-c support

2 things:
1. From the error message, it seems to need the open ssl library. So I guess you have to install openssl libssl-dev
2. it's --with-cmph not --withcmph

Hieu Hoang
http://statmt.org/hieu


On Fri, 29 May 2020 at 12:03, Hank Kuo <whkuo@mitre.org<mailto:whkuo@mitre.org>> wrote:
Hello,

I am encountering a compile error when building Moses with xmlrpc-c support.

I downloaded, compiled, and installed xmlrpc-c-1.51.06 into a Ubuntu 18.04 LTS VM.

After installing xmlrpc-c-1.51.06, the command that I executed to compile Moses is:

cd ~/mosesdecoder/
./bjam -a -j4 -withcmph=/usr/include

See attached build.log.gz for the build output.

Any help greatly appreciated.

Thanks,

Hank Kuo
MITRE Corporation
McLean, VA
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu<mailto:Moses-support@mit.edu>
http://mailman.mit.edu/mailman/listinfo/moses-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20200602/fa40def2/attachment.html

------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 164, Issue 2
*********************************************

Tweet