SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
indeed the webkitgkt slackbuild does not compile anymore.
the problem is not a loop, as you describe it - it just looks like a loop, as the same warning is displayed again and again (caused by a often used function). when you pause the compile from time to time, you will see that the caller function changes.
my build fails in an xpath module, later in the build. i did some investigation on that. that was when i compiled webkitgtk for crux linux, causing the same error and finally i got it running by patching the source.
to make it really, really worse, the build process nowadays depends on python and ruby. i don't know the reason and i actually don't care anymore - for me this software and it's build process is a pile of shit. but as there is no sane alternative i still use it (in conjunction with the surf browser of the suckless people.).
to make it short: if this package will be updated, i am afraid it will take a lot of work.