GDAL install fails due to missing shared library libIlmImf
I did an system update via
Code:
slackpkg upgrade-all Later I used R and one of the libraries I needed indicated a problem with GDAL. I exit R. I use Code:
gdalinfo Quote:
Code:
slackpkg search openex* Quote:
Code:
less /var/lib/pkgtools/packages/openexr-3.1.5-x86_64-1 I'm trying to get the GDAL version on sbopkg, 3.5. It installs, but that's when I get the error. I don't know how to repair this issue. |
Did you try just rebuilding GDAL after the upgrade-all? I have found that when a previously running program fails after an update with the missing .so version error, rebuilding the app often fixes it.
|
Quote:
Code:
/var/log/packages/openexr-2.2.0-x86_64-2_slack14.2:usr/lib64/libIlmImf-2_2.so.22.0.0 regards Henrik |
What henca said is also true for Slackware64 15.0 + Multilib:
Code:
# whatprovides libIlmImf HTH -- kjh |
Hi,
I assume from the issue you are having and the discussion in the thread that you have upgraded your slackware install to -current from 15.0. After doing such an upgrade you will have to rebuild all your sbo packages. sbo (and therefore tools such as sbopkg) do to track slackware library changes and so you have to do that yourself. This is especially relevant with current since .so lib version bumps are very frequent. Remember that slackbuilds.org only provide scripts to build the packages and not the packages themselves. Also, don't forget that slackbuilds.org does not officially support -current, however in this case I do happen to also use current so I test my packages on both -stable and -current. As @3rensho said in the forum, you need to rebuild gdal against the new versions of the dependent libraries (in your case, at least openexr and poppler). Note that poppler is one of these that tends to bump the .so lib version on a very regular basis so you will need to rebuild gdal (and any open packages you have that rely on it) every time it is updated. Hope this helps |
lol. I thought I was on 15. I honestly didn't realize that using upgrade-all would change the OS version. I thought it just updated packages, not the OS. ArTourter's explanation explains why QGIS isn't working now too. Oy vey. Thanks, everyone, for your help! :)
I got the GDAL to work, but after changing the libproj.so with a "ln -s" call from the version now installed (25) to the version that GDAL was looking for (22). |
Quote:
As for proj, please don't do this. Proj was updated and bumped the so lib version. Please rebuild the gdal package, do not simply install the old one! Same goes for qgis. Once these packages are rebuilt you will no longer have the missing lib/wrong lib version problems. Greg |
Sorry. What does "rebuild" mean? Does that mean to get the sbopkg package and just let it build that way? Or get the source from https://trac.osgeo.org/gdal/wiki/DownloadSource and build that?
|
Rebuild is just redo the sbopkg process : it will fetch source code of theprogram, build it and install the package.
|
Thanks, Tonus.
|
I got my sbopkg package problem fixed and sbopkg is synced with remote repo again.
I used Code:
sqg -a Code:
sbopkg -i GDAL Code:
gdalinfo Quote:
|
I just tried to build geos, proj and gdal on a clean system and everything went fine, also when I run gdalinfo
Code:
$ gdalinfo this is one of the reasons why, whenever you have to build something from SBo, it's advisable to do it, together with all of its dependencies, on a full and clean (no other packages installed) operating system (usually virtual machines and/or chroots are used for the scope). |
Okay. Thanks again, Ponce. I don't know why this is happening. Everything was working fine. Last week sometime, I ran
Code:
slackpkg update |
Quote:
Slackware current is not a rolling release like archlinux, it's where development of the newer release of Slackware happen, it's not meant for general use. if you need stability use the latest stable release, 15.0: in your case, if you have set a mirror for current in /etc/slackpkg/mirrors, instead of a downgrade to 15.0, maybe a reinstall is cleaner. |
Quote:
You can use tools like ldd or grep to find which dependencies different binaries or libraries has. The below example is from a Slackware 14.2 system (sometimes life really gets a lot easier when running a stable version of Slacwkare) Code:
ldd /usr/bin/gdalinfo Code:
grep libproj /usr/bin/gdalinfo So, has the binary really recently been rebuilt from source? Code:
ls -al /usr/bin/gdalinfo regards Henrik |
All times are GMT -5. The time now is 12:33 PM. |