Do "make install" on different Linux sytem than the one used for "make bpy"
This is not really an answer, not my knowledge either.
Wanted to add this as a comment, but I don't have enough reputation to do so.
I asked Campbell Barton several years ago about how to build blender so I could share my builds with people that used a different distro than I did, and this is what he replied:

There are a few issues here, First is with general libraries - if the
users doesnt have those exact libraries, blender wont start. To find
the libraries blender depends on do...
objdump -x blender.bin | grep NEEDED
You can do this too, it will show all indirect dependencies too.
ldd blender.bin
There are 2 ways to go about this,
*) statically link all libraries
*) include the libraries and use LD_PRELOAD_PATH to ensure they get found, this requires a wrapper script. to set the environment
variable.
Statically linking libs is best if you can, but for that you will need
&quot;.a&quot; files, so not libpython3.2.so --&gt; libpython3.2.a
however not all libraries come with static versions by default... it
can be a hassle to get them all.
There are docs on static linking libs, you can check online for more
info.
Also be sure to static link libgcc_s.so.1 and libstdc++, gcc has some
options for this.
once you have this sorted out the main remaining problem is linking
against libc, since you cant run blender on and older linux distro if
you linked with a newer glibc (normally called libc.so.6).
To workaround this you need to link against an older glibc, This can
be done by setting up a chroot environment that uses an older libc. or
simply by using a VM with an older linux distro installed, both are a
hassle :S.
Try google: linux link against older glibc
It comes up with some useful links.
Note that for our official linux builds we have a chroot with some
older libs installed so blender loads on older linux installs too.

Hope that helps!