[SOLVED] Difficulty re-building qgis after -current64 update
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Difficulty re-building qgis after -current64 update
QGIS failed to run after the latest "near-beta" updates on -current64 due to a library incompatibility. No great surprise there - I assumed that a re-build using the slackbuild would fix it. I used the awesome sqg queue file generator which resulted in a queue of 13 packages. All of them build fine except gdal and packages that require gdal (qgis itself and postgis). The gdal build fails after a good deal of compilation with the following error messages:
I would first try contacting the upstream developers to see if they have any noted problems with the latest gcc, glibc, make, and other compile-time packages.
Usually when I've had those recipe errors it's a problem with something related to GCC or glibc. And usually only a patch is the only help. Start with upstream and even check other distributions like Arch and Gentoo yo see if they have patches.
That definitely looks like a gdal build problem. It would be helpful if you could find the actual error message instead of just where it crapped out. The number of packages failing to build with -current since the 29 October update is into the hundreds. I started a build of the whole repo yesterday; it'll be on gis/ maybe Wednesday, and finish possibly Thursday or Friday. I've also got a day job, and this is radio show week, so it'll maybe be as late as the weekend -- sorry. Your existing packages should still run ok afaik.
gdal issue solved and all other packages now build correctly including qgis itself.
The issue seems to be that as I was using ponce's unofficial -current repository as the source of packages for sbopkg, I got gdal version 1.11.2 and this version would not build with errors as reported in my original post. However when I checked on slackbuilds.org I found that they were providing gdal version 1.11.3 as the Slackware 14.1 package. I downloaded this and it built with no problems, after which postgis and qgis were also built fine.
Thanks to those who offered help. Hope this solution helps others.
I think you most probably have an old version of my repository as I pushed the new gdal build script just hours after it has been merged on SBo on sep 26th: to verify which version of my repo you got, just check the output of
Code:
cd /var/lib/sbopkg/SBo-git/
git log | head -4
as you can see here it has been updated other 7 times since.
if you have problem downloading the new version use this procedure
For some reason (maybe the "this can confuse git a little" issue which you mention here ) my re-syncing in sbopkg was clearly not working. I followed your advice and deleted the local copy completely and the re-sync then worked fine and I have an SBo-current repository which contains gdal version 1.11.3.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.