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.
I am getting this error trying to configure splashy
Quote:
checking for splashy... configure: error: The pkg-config script could not be found or is too old. Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.
Alternatively, you may set the environment variables splashy_CFLAGS
and splashy_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
To get pkg-config, see <http://pkg-config.freedesktop.org/>.
See `config.log' for more details.
If I try ./configure PKG_CONFIG=/usr/lib/pkgconfig
Quote:
checking for splashy... configure: error: The pkg-config script could not be found or is too old. Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.
Alternatively, you may set the environment variables splashy_CFLAGS
and splashy_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
To get pkg-config, see <http://pkg-config.freedesktop.org/>.
See `config.log' for more details.
alan@LavanKossot:~/packages/splashy-0.3.5$
So where is the pkg-config script? There is a /usr/lib/pkgconfig directory full of *.pc files.
Hm, I built splashy on my Slackware 12.0 last week, and did not see this error.
What you do need is - directfb >= 0.9.22 (but I saw you built 1.0.0 already), glib2, freetype and all of those with static libraries (my freetype package has this and I can upload a modified glib2 package with SlackBuild and static libs if you want).
You need to build a static binary of splashy so that it can be used inside a initrd (if you want that).
I have just gone into my Slackware 12 installation and it configured fine.
It did not make because of
Quote:
gcc: /usr/lib/libfreetype.a: No such file or directory
gcc: /usr/lib/libglib-2.0.a: No such file or directory
So presumably I need to sort out glib2 and freetype there (though I thought I had them installed)
Anyway I am still using Slackware 11 as my working distro and would like to get it sorted there. It seems that there is a file /usr/bin/pkg-config which I have in 12 but not in 11. Is it possible that pkgconfig needs upgrading?
I am wondering if this is more trouble than it is worth. I have glib2-2-10.3 - presumably the original slackware 11 package. Do I have to replace this with a different glib2? Does this have any downside?
You will have to recompile glib2 and freetype, and recompile directfb, to generate static libraries (*.a files).
This does not harm your Slackware installation at all. Pat does not inlude static libraries because they mean additional MB's on the CD and on your hard disk, and Slackware uses dynamic libraries wherever possible to save space (and RAM!).
Programs that operate in an initrd and in the early stages of boot often are statically compiled because you can never be sure that all the libraries in /usr/lib are already available to the program (for instance if /usr is on a separate partition and not yet mounted).
Well in that case I would appreciate your glib2 slackpackage.
Can I assume that I do not need to recompile directfb if I did it using your slackbuild?
Here's a funny thing. When I downloaded your slackbuild files by right-clicking and 'Save as' in Firefox the slack-desc file was saved as slack-desc.htm which broke the build. I had to rename the file.
You will have to add commands for splashy to show anything during boot-up.
You will need to edit rc.S and rc.M at least to show the initial splash screen and to add progress indicators.
If you want a bootsplash very early in the boot you will have to add commands to an initrd as well, as well as add the splashy binary into the initrd image.
There is another thread from last week which describes the process if I remember correctly.
Well I do not think I even have it configured yet.
Quote:
root@LavanKossot:/home/alan/packages/splashy-0.3.5# splashy test
Splashy ERROR: Cannot read XML File <</etc/splashy/config.xml>>. Exiting...
Splashy ERROR: Error occured while starting Splashy
Make sure that you can read Splashy's configuration file
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.