Build instructions (on Ubuntu 16.04)

[jcward]

Using the apt-get from the readme, I get:

sudo apt-get install libpng16-dev libturbojpeg-dev libvorbis-dev libopenal-dev libsdl2-dev libmbedtls-dev libuv1-dev
E: Unable to locate package libturbojpeg-dev

The package is not libturbojpeg-dev, it's called libjpeg-turbo8-dev

But joy upon joy, that package's install is missing a symlink, which causes hl build to break with:

/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libturbojpeg.a(libturbojpeg_la-turbojpeg.o): relocation R_X86_64_32 against `.data' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libturbojpeg.a: error adding symbols: Bad value

(Same problem and solution is mentioned here.)

It shouldn't pick up the .a file, it should pick up the .so file. The solution is to create the missing symlink:

sudo ln -s /usr/lib/x86_64-linux-gnu/libturbojpeg.so.0 /usr/lib/x86_64-linux-gnu/libturbojpeg.so

Then hl build completes successfully!

We could update the readme with the above, or point folks to this issue.

[andyli]

As you've found out, the libjpeg-turbo8-dev package on Ubuntu 16.04 provides a static library that was not compiled with -fPIC, which it should. The problem has been fixed in later version of the package, which was renamed to libturbojpeg-dev. The libturojpeg-dev package also provides libturbojpeg.so.

If you use Ubuntu 18.04, the current instruction is all good. For Ubuntu 16.04, I will try to figure what is the best instruction.

It shouldn't pick up the .a file, it should pick up the .so file.

I wouldn't say it should pick up which one, since there are reasons for choosing either of those. However, it should be possible to use either. It's just the 16.04 package being faulty.

[ncannasse]

@jcward yes the instructions could be updated for Ubuntu 16.x, they are valid for Ubuntu 18.x

[sonygod]

Try libpng-dev instead of libpng16-dev

[hsandt]

So, I built libjpeg-turbo myself from the GitHub repository (I picked version 2.0.0). Building is easy on Linux, you can just follow the instructions at https://github.com/libjpeg-turbo/libjpeg-turbo/blob/master/BUILDING.md. The only special requirement is that you need NASM or YASM; I don't know anything about them, so I just installed the first one:

sudo apt install nasm
cd {libjpeg-turbo-root}
mkdir build
cd build
cmake -G"Unix Makefiles" ..
make
sudo make install

If you look at the CMakeLists.txt, you'll see CMAKE_POSITION_INDEPENDENT_CODE mentioned. Basically, if you set no extra option for cmake you should get position-independent code (-fPIC) which is what we want.

Now just try to make hashlink again.

P.S.: I managed to build hashlink this way but couldn't test it due to compatibility issues with haxe (1.7 is too advanced, I need to go back to 1.1 or get a nightly build of haxe). I didn't manage to make that work, so maybe I'll post another issue later.

[ikoryakovskiy]

I had exactly same issue on Ubuntu 16.04 but with caffe. A workaround that worked for me:

sudo apt-get install libturbojpeg
sudo ln -s /usr/lib/x86_64-linux-gnu/libturbojpeg.so.0.1.0 /usr/lib/x86_64-linux-gnu/libturbojpeg.so

If I understand it correctly, the libturbojpeg package is a workaround for the -fPIC, however, for other libraries to pick a new libturbojpeg, the new link has to be created.

[jingkang99]

!!! for libjpeg-turbo and turbovnc, specify -fPIC when create make file !!!

cmake -G "Unix Makefiles" -DCMAKE_C_FLAGS=-fPIC -DCMAKE_BUILD_TYPE=Release ..

otherwise, link error when build turbovnc