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.
Having just upgraded from Slackware64-13.37 to 14.0, I've had to re-install some of my software, and one or two of them are proving problematic - specifically mjpegtools and vobcopy!
I have a standard slackbuild script for mjpegtools-2.0.0 which worked fine under 13.37. However, under 14, gcc produces an error whilst compiling: "Your gcc does not even support i386 for -march and -mtune"
This isn't surprising, as I'm building for x86_64! What is surprising is that gcc then interprets this error message as an instruction to search for a file or directory, and then crashes:
"gcc: error: Your: No such file or directory
gcc: error: gcc: No such file or directory
gcc: error: does: No such file or directory
gcc: error: not: No such file or directory"
and so on!!!
I've never seen anything like this before, and I've been a Slack user for over ten years!
I found a new slackbuild script on Slacky and tried that - it worked instantly!
At a quick glance, I can't see anything significantly different in the way its configured, but there's obviously some subtle change in there! I'll have to have a closer look at it later, but for the moment, problem solved!
Many thanks for your help, guys! Just knowing that you all managed to build it persuaded me that it was something unique to the way I was doing things, rather than a generic issue! And that led me to a solution, even if I'm not quite sure why, yet!!!