Compile under Arch Linux not working

[grisu48]

Under Arch Linux using gcc 6.3.1 20170306 the compilation of version 2 using "./compile_linux_gcc.sh" didn't work. Error message is "cannot find -lgomp"

Solution: Removing the -static flag from the compilation.
I don't know if this has performance related consequences but was able to compile it to a working binary with this bugfix.

Creating a pull request

[Mysticial]

It's not a performance issue. It's just for universally compatible binaries. But static-linking sucks more and more nowadays.

I'm planning to do a version 3 at some point which will use raw threads instead of OpenMP. That will hopefully solve this problem.

[grisu48]

That's great news! I appreciate your project, you're doing a great work!

[Mysticial]

See if this reproduces on version 3. I got rid of the OpenMP dependency. But there's also an ugly hack to statically link pthreads.

[travisdowns]

For what it's worth, the compile didn't work for me on CentOS using gcc-7 (devtoolset-7), with errors like:

/opt/rh/devtoolset-7/root/usr/libexec/gcc/x86_64-redhat-linux/7/ld: cannot find -lpthread
/opt/rh/devtoolset-7/root/usr/libexec/gcc/x86_64-redhat-linux/7/ld: cannot find -lm
/opt/rh/devtoolset-7/root/usr/libexec/gcc/x86_64-redhat-linux/7/ld: cannot find -lc

The root cause again is -static. After I did:

sudo yum install glibc-static.x86_64

it worked, but you might want to reconsider your use of -static (is it necessary?) or include a blurb in the readme.

[Mysticial]

Those are the flags that I used to compile the binaries that are checked into this repo. Since I'm distributing binaries, static-linking was the easy way out of the dynamic linking problem on Linux.

But yeah, that's not necessary if you're building from source yourself.

[travisdowns]

@Mysticial - right, I get it now - -static is for the distributed binaries. You might consider putting them in a separate place or at least changing the default away from -static (with another flag to enable it when you want to build the static binaries) since probably everyone running the script wants to build them for the local machine, not to push back a change in the static binaries (as another minor annoyance as soon as you build git will tell you that all your binary files are modified, so you have to carefully avoid them if you want to commit changes elsewhere).