OpenSSL error building Erlang OTP from source

Question

Trying to build a completely self-contained OTP that can be moved around independently of libs installed on a system.

Build OpenSSL 1.0.0d from source as follows:

./config --prefix=<open-ssl-dir>
make
make install

Then OTP R14B03:

./configure --prefix=<erlang-dir> --with-ssl=<open-ssl-dir> --without-termcap

Make of Erlang then fails as follows:

relocation R_X86_64_32 against `OPENSSL_ia32cap_P' can not be used when making a shared object; recompile with -fPIC

We're talking Ubuntu 10.04. Any help greatly appreciated - thanks!

What happens if you try to build Erlang with `CFLAGS=-fPIC make`? — sarnold, Jul 07 '11 at 23:34

score 5 · Accepted Answer · answered Jul 11 '11 at 06:05

5

The "can not be used when making a shared object; recompile with -fPIC" would mean SSL is not build with the Position Independent Code flag. This is needed for building it as a Dynamic Shared Object (DSO). This is probably needed by Erlang build process. Example build:

$ tar zxvf openssl-0.x.tar.gz
$ cd openssl-x
$ sh config shared -fPIC
$ make
$ sudo make install

answered Jul 11 '11 at 06:05

Ward Bekker

6,316
9
38
61

This solution helped me when trying to build Apache using an old openssl version! Thank you! – Thomas K Jul 16 '14 at 12:47

score 1 · Answer 2 · edited Jan 28 '16 at 09:25

1

For ppc64le:

./configure --prefix=/home/huaxin/huaxin/toolsInstalled/ --build=ppc64le CFLAGS="-D_GNU_SOURCE -DOPENSSL_NO_EC=1"

edited Jan 28 '16 at 09:25

Robert

5,278
43
65
115

answered Jan 28 '16 at 09:19

user5851149

11
1

score 0 · Answer 3 · edited May 23 '17 at 11:44

I suggest that you build on a VM where you have sudo permissions. Then build libraries like OpenSSL using --prefix=/usr so that make install puts them in the usual system library.

Then build your tool, in this case Erlang, using -rpath. Then use ldd to find all library dependencies for Erlang and any ports (C extensions) and copy those into Erlangs lib directory. Check all binaries and libraries with readelf -d to make sure that RPATH is set to $ORIGIN or $ORIGIN/../lib as needed. Use patchelf to fix these things if the linking process is not quite right (or you copied in secondary dependencies of system libraries).

Then use patchelf to set the interpreter for your binaries (not libraries) to point to ld-linux.so.2 in Erlang's lib directory. And then run a test suite using

strace -e open erl ... to make sure that your build is not opening anything in /lib or /usr/lib.

At this point tar it up and it will run on any Linux.

See this question Compiling Python 2.6.6 and need for external packages wxPython, setuptools, etc... in Ubuntu for far more detail on how I built Python in this fashion.

OpenSSL error building Erlang OTP from source

3 Answers3