watchman: Binaries seem broken on linux

Thanks for trying these!

Np! I really appreciate the work on them, as it’ll make watchman much easier to get.

I’m not an expert on C/C++ native things, but FWIW my vote would be (if possible) to have 100% static binaries.

I.e. given my level of native-tool-chain expertise is “okay, I can technically run make and kind of debug shared lib issues by leaning heavily on stackoverflow each time” (which I imagine is common among watchman users), the 100% static approach of “just put watchman in /usr/local/bin and you’re done” would be pretty great.

I have the same issue, while trying to use binary downloads for Ubuntu 18.04

$ watchman 
watchman: error while loading shared libraries: _artifacts/linux/lib/libgflags.so.2.2: cannot open shared object file: No such file or directory

Info:

$ ls /usr/local/bin/ | grep watchman
watchman

Where is correct path for putting these two static lib files:

libgflags.so.2.2 
libglog.so.0

I put them here:

ls /usr/local/lib/ | grep libg
libgflags.so.2.2
libglog.so.0

I also try something like this:

$ ls /usr/local/bin/_artifacts/linux/lib/
libgflags.so.2.2  libglog.so.0

And this:

$ export LD_LIBRARY_PATH=/usr/local/lib/

But no ones worked for me.

We’re still far from what I’d consider “done” here, but things are a bit better right now if you’re on ubuntu.

https://github.com/facebook/watchman/actions/runs/91748642 has a zip that extracts to:

$ tree linux
linux
├── bin
│   └── watchman
└── lib
    ├── libgflags.so.2.2
    └── libglog.so.0

2 directories, 3 files

Those object files are built to be installed to /usr/local/bin (you’ll need to chmod +x /usr/local/bin/watchman) and /usr/local/lib with no requirement to mess with the LD_LIBRARY_PATH.

You’ll also need to setup the state dir:

sudo mkdir -p /usr/local/var/run/watchman
sudo chmod 2777 /usr/local/var/run/watchman

This particular build requires the ubuntu boost package(s) to be installed.

We’re working towards at least getting this documented in the main docs, but also to make this a bit easier to install and use as well as publishing these things to a github release automatically.

Starting today, we have weekly tags with binaries uploaded to them: https://github.com/facebook/watchman/releases/latest I’d appreciate your feedback on how well the linux binaries work in practice!

can you add a fully static linked version (musl not glib)?

watchman-v2022.01.03.00-linux.zip

ubuntu 16:

• missing libcrypto.so.1.1 fix

watchman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

• missing GLIBC_2.25

watchman: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by watchman)

$ ldd --version
ldd (Ubuntu GLIBC 2.23-0ubuntu11.3) 2.23

Just did a fresh install on a CentOS 7 VPS, following the official instructions exactly. I tried to initialize my first watch but was greeted with:

watchman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

Any suggestions/directions?

Thanks @wez Worked fine first go on Fedora release 32 (Thirty Two) 5.7.7-200.fc32.x86_64

@wez worked on the 1st try! Amazing, thanks!!

@DhruvDh Sorry my mistake, my comment above is wrong … the only way I got that working is following exactly the steps @omidraha mentioned but running watchman from the LD_LIBRARY_PATH (/usr/local/lib)