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.

I have found on the internet through "google" that this was going on in version 0.8.4.0 and was due to amd64. I read through a bunch of stuff that says it should be fixed on later updates and I don't see much of a work around or fix. Can anyone point me in the right direction, and this wouldn't be because I am operating 64bit would it?

I assume you're using -current? You'll have this problem with a few SlackBuilds until the source is fixed upstream. In the time being, add this to your SlackBuild for network-manager-applet (easy to do in sbopkg through the "Custom" selection):

Code:

sed -ie 's/-Werror//' configure

Put it right above the ./configure line, so that the whole section looks like this:

Please note that SlackBuild scripts hosted in SBo are designed to work on certain -Stable releases (currently 13.37), so it's natural if it breaks on -Current due to the nature of -Current which introduces new toolchain and libraries which might cause some incompatibilities

Well I appreciate all the help guys. But once I finished my outdated updates in -current, I tried apeitheo's advice and was unsuccessful still. Only this time I got a new error. I did realize with the -current updates my NetworkManager was updated to 0.9.2.0, but I was trying to install the 0.8.6.0 nm-applet. Knowing this is what is on the SBopkg tool and from slackbuilds, I went gnome's ftp and downloaded the corresponding nm-applet. I then used Workman's Slackbuild scripts to build with only two exceptions. 1st I had to change the info file and the slackbuild script to reflect the correct build, 0.9.2.0. 2nd I had to comment out his one line the set NM to group NetDev, and it works just fine after build. Thanks again for the help.