Home > Articles > Operating Systems, Server > Linux/UNIX/Open Source

But I Downloaded Source Code!

Good for you! With no offense intended toward those who take the binary route—compiling KDE2 does take some time—if you can build it yourself, you can optimize it for your machine, you will be more likely to repair any problems that might arise, and you will have exhibited a familiarity with Linux that will make some of the things in KDE2 that aren't working yet a little easier to swallow.

What you do with the source depends largely on the drive space that is available; a lot of space can uncomplicate things, especially if you use CVSUP and plan to use it again and again as KDE2 moves closer to release. Whatever the case, exit KDE (if it's running) so that you're at a pure console session. The first issue is our old friend QT.

The qt-copy package should be copied someplace[md]/usr is fine. Then use tar xvfz to unpack it. If you currently have a /usr/lib/qt that is a symbolic link to, say, /usr/qt144, delete it. However, if qt-1.44 itself actually resides at /usr/qt, you'll need to move it to, say, /usr/qt144, in the same way your KDE-1.1.2 got moved from /opt/kde to /opt/kde112 earlier in the article. Now, make a symbolic link from qt-copy to /usr/lib/qt:

ln -s /usr/qt-copy /usr/lib/qt 

If you're already running a version of KDE, you won't need to change the environment variable for QT because you're putting the new version, via the symbolic link, in the same place where the old one resided. But if this is your first KDE experience, you'll need to set the environment variable as specified in the /usr/qt-copy/INSTALL; you will need to alter the specified paths to point the $QTDIR to /usr/lib. Now you're prepared to build the new QT. If you're not there already, change to the QT directory. Then do this:

make -f Makefile.cvs
./configure -sm -gif -system-libpng -system-jpeg

You will need to await the return of the command prompt between each of these. The -gif option for the configure command is used because of copyright issues: QT may not enable .gif file support by default, but you may do it manually.

The make process takes quite a while. It might be done in minutes on the best-of-all-possible machines, but for the rest of us it may take up to an hour. When it's done, you're almost ready to build KDE2; however, you do have a decision or two to make first.

With unlimited drive space, you can copy all of the KDE2 source tarballs to /usr/local/src/kde; you can do likewise if you have used CVSUP to copy all of your /home/kde (or whatever directory name you chose) to /usr/local/src/.

KDE2 (in fact, all KDE) source tarballs are compressed using bzip2, which is more efficient than other popular compression methods. So, for the tarball folks, it's a good idea now to change to /usr/local/src and do the following:

bzip2 -d kde*

This uses the bzip2 program to decompress all files in the directory that begins with the letters "kde." This doesn't take long, but it does take long enough (a few minutes) to make you wonder if something has gone wrong. If you don't get error messages echoed to the screen, everything is okay. To unarchive each package in turn, you use this line:

tar xvf [packagename] 

There are a lot of packages; it's useful to untar them one at a time as you compile them. Then, if you get distracted, you'll be able to easily tell which ones you've built and which ones you haven't. In any case, kde-common is the first one to do because all the others rely on it.

CVSUP users don't have to worry about unpacking the files, whose compression was brief and during the download only. They're ready to go. What you do have to worry about is whether you have an additional 100-plus MB of space in /usr/local/src for a copy of the whole source tree. If not, it can be built in situ in the directory into which it was downloaded. (This involves a little complication, which we'll discuss shortly.)

Wherever the source is located, the first package to deal with is kdesupport. Change to that directory; snapshot users should untar it and then change to it. Then do this: ln -s ../kde-common/admin ./

This creates a symbolic link between the /admin subdirectory of /kde-common and the current directory. You will need to do this for each KDE2 package you build. Then comes this line:

make -f Makefile.cvs 

This prepares the files that are necessary for the configure command to do something useful. This will need to be done for each package. As with creating the symbolic link to kde-admin, this is not something that happens in release versions of KDE or in other source packages, so it's easy for even experienced compilers to overlook. Next, unsurprisingly comes this line:


But don't stop with just ./configure—here is where you specify not only where your KDE2 will end up, but also how well it will run when it gets there. You can even specify the size of the code, which affects both the storage space required and the time that is necessary to load the files created. The command accepts not just a number of options, but compiler flags as well. For instance, you probably have a Pentium-class machine (this includes AMD K6-2s). Unless you would like to become actively involved in development, creating lots of debug code won't do anything but slow you down. Additionally, you'd like to specify where your newly compiled programs will ultimately reside. To bring about these things, rather than using plain old ./configure, enter this at the command line:

CXXFLAGS=' -mpentium'./configure --prefix=/opt/KDE2 

With this, you've told your C++ compiler that it should compile Pentium-optimized code; you've also determined that configure should plan on the results of compiling into the specified directory, and you've specified that configure need not bother with all that debug code. Yes, the single quote goes immediately after the equals sign and is followed by a space. (If you are experienced and have other favorite compilation flags, you can use them here, too.) The ./configure process will take a minute or two for kdesupport; for some packages, it can take 10 minutes or more. When it's done, enter this line:

make all

Now the code is actually compiled. It will take approximately 10 minutes for kdesupport; for the more elaborate packages, such as kdebase or koffice, it will take a lot longer. But in due course, you are returned to the command prompt, which you treat to:

make install 

The binaries you've compiled will now be installed into /opt/KDE2.

Next, you do the same thing—the same thing, no changes[md]to other packages, in this order: kdelibs, kdebase, and then others—the order is up to you. The whole process takes several hours and can be rather tedious, unless you happen to enjoy watching it (and if your heart doesn't flutter when you see a warning message, because at this stage there are many). Fortunately, you don't have to hover over your machine during this process—the KDE developers put a useful bell into the code so that when it's done, your computer's speaker will beep. (This is a good time to clean up the office or go through those boxes and boxes of floppies you've been meaning to do something—what?—with.) But before the seasons change, it will all be done and installed[md]even koffice.

If you have been using KDE, now you need to delete the symbolic link that points to /kde112 and create a new one:

rm /opt/kde
ln -s /opt/KDE2 /opt/kde 

Now you can exit root, become yourself again, type whatever command you're accustomed to typing to start KDE, and look at KDE2.

Those who haven't used KDE before should back up their /home.xinitrc or /home/.xsession file, as the case may be, and replace it with one that says, simply, startkde. Having done that, the startx command will start KDE2.

A Note for CVSUP Users

If you had the disk space to copy the whole tree over to /usr/local/src/kde, great. Remember to delete it before you build a new CVSUP version of KDE2. But if you built KDE2 using the actual downloaded source and not a copy of it, make sure to enter each package directory before you run CVSUP again, and enter this line:

make clean

The binaries you built are now deleted, as are the makefiles and other things. The source is restored to pristine condition.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020