[SOLVED] sqlite3

modim · 05-17-2020, 01:52 PM

Slack64, 14.2, package sqlite-3.13.0-x86_64-1.txz has usr/lib64/libsqlite3.la

But Slack64-current, package sqlite-3.31.1-x86_64-1.txz doesn't have this file. It's not in any other package either.

I had to upgrade to sqlite-3.31 because I needed the window function support. Just did upgradepkg using the -current package. Everything worked fine.

But later, I tried building something that needed the .la file in the build.

I haven't examined the -current build script but could it be that some build option needed to be invoked to generate the .la file?

Yes, I know I'm lucky it works at all because the -current packages are linked against different versions of various libraries than my 14.2 system. But I'm certain it's the missing libsqlite3.la that was the issue with the other build I was attempting because I copied in the .la file from the old package and the build succeeded. But that's probably not the right answer. Anyway, curious what's going on.

thanks!

M.

modim · 05-17-2020, 02:02 PM

PS, I should probably mention that the other package I was trying to build was graphviz (v. graphviz-2.40.1), using the slackbuilds.org script.

upnort · 05-17-2020, 02:09 PM

Quote:

I haven't examined the -current build script but could it be that some build option needed to be invoked to generate the .la file?

Look in the Current build script for this:

Code:

# Don't ship .la files:
rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la

Comment out or delete those lines.

modim · 05-17-2020, 02:19 PM

OK thanks ... should have looked at the script

Just for my education, why wouldn't we want to include the .la files in the package?

mralk3 · 05-17-2020, 02:38 PM

Quote:

Originally Posted by modim

OK thanks ... should have looked at the script

Just for my education, why wouldn't we want to include the .la files in the package?

It was announced in the Slackware-current change log a while back.

Quote:

+--------------------------+
Thu Apr 19 01:04:06 UTC 2018
Hi folks, and welcome to the third ever Slackware Mass Rebuild (and the
longest ChangeLog entry in project history). There were two primary
motivations for rebuilding everything in the main tree. The first was to
switch to the new C++ ABI. The second was to get rid of all the .la files
in the LD_LIBRARY_PATH. Really, having .la files installed has been mostly
obsolete since things began to use pkg-config instead, but it's not easy
to get rid of them unless you do it all at once. If you just take them out
of one package, any other packages containing .la files that refer to the
removed ones will be broken. We've removed a few here and there before
(and then handled any packages that had referred to them with a rebuild),
but it was time to finally remove all the ones in /lib{,64} and
/usr/lib{,64}. One of the reasons that this really needed to happen is that
many projects are starting to migrate to build systems other than autotools,
and those systems do not generate .la files. So if we didn't get rid of them
now, we might end up in a situation later on where they are being removed
by upstream and then we would have to chase down the dependency breakage and
recompile (possibly many) other packages. The .la files that are outside of
the LD_LIBRARY_PATH were not removed (and shouldn't be) - those ones are
often used by the lt_dlopen() function to load plugins and removing those
ones can break things. But those ones don't cause problems... they aren't
likely to try to infect .la files produced by other packages.
IMPORTANT NOTE: If you have any third party or other packages installed on
your system that don't come with Slackware, and those packages have installed
any .la files, it is very likely that they refer to some .la files which we
have just removed, and that trying to compile against these packages will no
longer work. Luckily, the solution is simple: remove them. This command will
remove any stale .la files from the LD_LIBRARY_PATH:
rm /{,usr/}lib{,64}/*.la
Moving forward, nothing shipped in Slackware will contain any .la files in
those directories, and any SlackBuilds intended to be used with Slackware 15.0
should contain this bit of script:
# Don't ship .la files:
rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la
In addition to those goals, the opportunity was taken to clean up slack-desc
files and make many trivial fixes to build scripts. We've also made it easy
to recompile everything again should there be a good reason to do so.
You'll also find various updates scattered throughout this long list.
Enjoy, and sorry about the bandwidth. ;-)

modim · 05-17-2020, 02:41 PM

Well OK then, all is clear.

Thanks again.
M.

bassmadrigal · 05-17-2020, 06:13 PM

Quote:

Originally Posted by modim

I had to upgrade to sqlite-3.31 because I needed the window function support. Just did upgradepkg using the -current package. Everything worked fine.

This is never a good idea. That sqlite could've been built against specific versions of libraries in -current that don't exist in 14.2. The fact the package actually worked is just luck.

If you ever need to upgrade a package with a version that exists in -current, it is much better to download the source folder for that package and run the SlackBuild, as then it will be compiled against packages on your system. (You may need to comment out the lines that remove the .la files if you pull SlackBuilds from -current.)

modim · 05-17-2020, 06:20 PM

Yes, I can confirm this - I've had just this sort of bad luck in the past. I guess it's not too late to go back and do it right.

thanks.
Modim

mralk3 · 05-26-2020, 04:17 PM

Sorry for the slight necro post, but I do not get on LQ as often as I used to.

Quote:

Originally Posted by modim

Yes, I can confirm this - I've had just this sort of bad luck in the past. I guess it's not too late to go back and do it right.

thanks.
Modim

All you need to do is fix the mirror url in your /etc/slackpkg/mirrors to point to the right release (14.2). Assuming slackpkg still works, run

Code:

slackpkg update gpg && slackpkg update
slackpkg install slackware64

That should restore all the packages to 64-14.2 you upgraded using Slackware64-current packages.

modim · 05-26-2020, 10:04 PM

Thanks - hadn't thought about the pattern matching feature.

In this case, it was just one package and I didn't want to restore it to 14.2 status since I needed the newer sqlite. I did it as bassmadrigal suggested: rebuilt the package from source on my 14.2 system, using the -current script and source, and commenting out the line that removes the .la file. Then upgradepkg and blacklisted sqlite in /etc/slackpkg/blacklists so it wouldn't try to revert. Seems to be working fine.