OK, first post.
CentOS-6.8, university setting and don't have root.
--> I'm getting missing "liblass-1-7-0.so.0" error.

And I want to download and install "liblass-1-7-0.so.0" into my
personal "LD_LIBRARY_PATH" directory, in order to continue working,
while I wait for Linux support to do a proper install.

So I search "Available Repositories for CentOS" for
"liblass",(at wiki.centos.org) and don't find anything like liblass.

My guess, "liblass" is part of some larger collection of .so files
that I can't figure out.

Is this correct ? (if yes, how would I determine this ?)

If it is part of a larger set of library files, can I download this
larger set, and gcc on our CentOS-6.8, and then put the compiled
"liblass-1-7-0.so.0" into my "LD_LIBRARY_PATH" directory ?

Do I have to gcc everything ? Can I just gcc the source for liblass ?

And where do I find the source for "liblass-1-7-0" ?
Or if there are precompiled binaries, that would be better.

thanks, -steve

Hi Steve, and welcome to LQ.

I don't know CentOS - hopefully someone will be along soon who does - but do you mean libLAS (without the second 's'), the C/C++ library for LAS LiDAR data?

If so, you can download a copy from here:

http://rpm.pbone.net/index.php3/stat...86_64.rpm.html

I found this link from searching on the internet for rpm liblass 1.7

LibLAS home page:

https://www.liblas.org/

1 members found this post helpful.

CentOS uses yum as the package management utility, and as such, can provide searching capabilities.
https://wiki.centos.org/TipsAndTrick...3bf51763a5cb3e

You could do "yum provides liblass-1-7-0.so.0", and it will tell you what package contains it. However, I bolded a part of your post above; without root, you cannot do any meaningful installation, and may not even be able to use yum. That said, putting the missing file name into Google tells us that it's part of libLAS. You can download that from the CentOS mirrors (just find the package), but even then, you're not going to be able to do much. Putting libraries in your home directory isn't a good thing..and it's not just ONE file that's missing.

You don't say anything about what you're doing that requires this package, but it is HIGHLY LIKELY that if you get that one dependency resolved, another will pop up.

1 members found this post helpful.