Maybe this can help to solve the issue
I also noted that XMLRPC libraries is not statically link
this is what I got running ldd on moses first and mosesserve
ldd moses
linux-vdso.so.1 => (0x7fff3f3a1000)
librt.so.1 => /lib64/librt.so.1 (0x003620a0)
Hi,
Ugh sorry something was weird with bjam. I've put a kludge in that
forces static linkage unless link=shared appears on the command line.
Kenneth
On 08/26/13 21:59, Lane Schwartz wrote:
> I'm attempting to compile Moses in such a way that at least the boost
> libraries are statically
1 and 2: Sadly the build system is a bit stupid when you change
configuration behind its back. You need to recompile with -a.
For points 3 and 4:
- Try installing Boost 1.50.0 in /usr and /usr/lib64.
- Check that the symlinks are in /usr/lib64 and point to your
installation.
- Make sure the he
Thanks Kenneth and Tom, for the updates and confirmation.
I think I've missed something in these threads. I pulled from Git and did
the following:
1. ./bjam --without-libsegfault
2. ldd `which moses` to determine which libs are dynamically linked
Output:
ldd `which moses`
linux-vd
Just confirmed the update:
bjam --without-libsegfault
tahoar@library1:~$ ldd `which moses`
linux-vdso.so.1 => (0x7fff0d7ff000)
librt.so.1 => /lib/librt.so.1 (0x7f43de73)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f43de41c000)
libm.so.6 => /li
Ok, committed. Here's how the build system now behaves:
link=shared: Everything linked dynamically.
Default: internal libraries are statically linked. Boost and zlib
statically linked if possible. libSegFault dynamically linked.
Dynamically linked executable.
--without-libsegfault: Same as
D'oh, it's a feature, not a bug. Add runtime-link=static and you'll get
a fully-static executable.
Plan to add this to the Moses build system. Testing now.
Kenneth
On 08/06/2012 11:31 AM, Tom Hoar wrote:
> FYI, this build is on U-10.04.4 using the bjam shipped with Moses. I can
> send you the
FYI, this build is on U-10.04.4 using the bjam shipped with Moses. I
can send you the complete log if it helps. Let me know if you need
anything else.
Tom
On Mon, 06 Aug 2012 11:27:27 -0400, Kenneth Heafield
wrote:
> Hi,
>
> There appears to be a bug in boost-build that prevents it fro
Hi,
There appears to be a bug in boost-build that prevents it from making
fully-static binaries with g++. This might take a while to sort out.
Kenneth
On 08/06/2012 10:48 AM, Tom Hoar wrote:
> Thanks, Ken. I think this is easier than adding another option to Moses
> if we can understan
Thanks, Ken. I think this is easier than adding another option to Moses
if we can understand the output. The ldd manpage says "ldd prints the
shared libraries required by each program or shared library specified on
the command line." I assume "shared libraries" means not statically
linked?
Dear Officemate Sitting Behind Me:
I added --static. And --nosegfault has been renamed to
--without-libsegfault.
Kenneth
On 08/06/2012 10:06 AM, Jonathan Clark wrote:
> Kenneth,
>
> Would it be possible to add a "--static" flag to the build to explicitly
> request "static linking or fa
On linux,
ldd bin/moses
On 08/06/2012 10:03 AM, Tom Hoar wrote:
> Thanks Ken. I downloaded/compiled with the latest changes up to
> BOOST_CHECK_CLOSE. The exit code 1 disappeared and everything seems okay.
>
> One more question. Other than the log output at compile time, is there
> any way to que
Kenneth,
Would it be possible to add a "--static" flag to the build to explicitly
request "static linking or fail" behavior? If static linking is truly
desired, having to read lots of debug messages is a painful way of
verifying that you have a static binary.
Jon
On Mon, Aug 6, 2012 at 10:03 AM
Thanks Ken. I downloaded/compiled with the latest changes up to
BOOST_CHECK_CLOSE. The exit code 1 disappeared and everything seems
okay.
One more question. Other than the log output at compile time, is there
any way to query the Moses binary to see which libraries are statically
vs dyna
Hi,
You're correct. There doesn't seem to be a static version of this
library. I've added the --nosegfault option (which isn't as cool as it
sounds) to skip this library.
Kenneth
On 08/06/2012 02:08 AM, Tom Hoar wrote:
> I read the comment "In order to obtain a fully static Moses, ev
I read the comment "In order to obtain a fully static Moses, every g++
command line that includes "-static" must pass with exit code 0." with
interest.
When we compile moses, this log output line shows an exit code 1. All
the others are 0.
bash -c "g++ -static -lSegFault -x c++ - <<<'in
Hi,
Moses attempts to link statically by default but falls back to dynamic
links. You must have static versions of all the dependencies installed
as well. Run
bjam --debug-configuration
and, near the top, it will show you some command lines followed by their
exit code. In order to
Hello,
I’m trying to build Moses with statically linked libraries, but it doesn’t
seem to be working. Here’s what I’ve tried so far:
./bjam --clean-all
Then
./bjam -j8 link=static
I've also tried
./bjam -j8 --build-type=complete
The output file continues to be only dynamically li
18 matches
Mail list logo
