Some timely tips on Slackware and libraries
First of all, the people who wrote Qt wrote it for the general Linux crowe (well, the Linux version anyhow) so that means Red-Hat-based. Us Slackers have to do things differently than the rest of the world. If there is no configure option for the libpng path, you might have to find out where it is looking for the libpng. I haven't tried building Qt recently on Slackware, but if you can't find the Slackbuild script for it, you will have to do symbolic links for the libraries. This is an ugly and messy solution, and should be avoided at all costs, but sometimes it must be done. For example, when there was still a version of Borland Delphi available for Linux, it required glibc-2.so.3.0.6 I believe, and I had version 3.0.8.5 or something. Anyhow, I just symbolically linked the files as I needed them, and had to create new and more creative links to the same version with three or four different names.3.0.6, 3.0, and no extension were some of them. It is a messy solution, and it only works until you update your package, then you have to create the same links over again. If you can find a SlackBuild file - look in Slackware 12.2 I think - you will probably be better off.
|