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.
It installs gcc 3.4.x alongside (i.e. not overwriting) the gcc 4.x of Slackware 12.0. The original gcc 4.x compiler will still be default but applications that specifically look for a gcc3 compiler (such as QEMU) will find and use the gcc3 compiler.
My notes on how to invoke the gcc3 compiler instead of the default gcc4:
# This is a gcc34 compatibility SlackBuild for use in Slackware > 11.0 ,
# where gcc4 is the default compiler suite.
# This gcc34 build installs to /usr/gcc34 and will not interfere with gcc4.
# *** Use gcc34 in your scripts, as follows ***
# * By using environment variables:
# Most softwares support the CC and CXX environment variables.
# First assign them, then run configure and/or make. Example:
# CC=gcc34 CXX=g++34 ./configure
# * Using configure support:
# If the software is using the standard GNU automake and configure,
# then there is a chance it supports other compilers by passing in
# a setting to the configure script.
# First run configure --help to see if it mentions anything.
# The following example is from MPlayer:
# ./configure --help
# ./configure --cc=gcc34