How to hate free software in 3 easy steps

Short URL:


It’s this:

  1. Download some software that isn’t pre-packaged with your distribution, and try to build it.
  2. Er.
  3. That’s it!

Software development is hard. I don’t think that any of us that have written more than 20 lines of Perl will disagree with that. So why is it impossible for the same, obviously smart, programmers to provide tar balls, zips, archives or code that will actually compile? At all. On any system. Ever.

When developing software you start with a blank canvas, old libraries, and new code. That’s it! New code should compile anywhere since cross-platform development is a well understood field, and we’re mostly using gcc, anyway. So that’s a moot point. Libraries are simply enough, surely? Just make a note of which ones you’ve used, their versions and download URLs and everything should be easy. Hell—there are tools, like the automake suite, that provide all this functionality for free. So why aren’t people using it?

So, I after trying to compile [insert embarrassment of a package here] I give up and choose another. After all, free software has so many different implementations of [insert obscure niche market sub-genre here] there’s usually always an alternative. I try that too. Same issues, different problems. That is, it won’t compile without hours of faffing. Time to try another package?

The reason we have so many different packages for the same thing is probably because the author couldn’t get any other similar code to compile!

At the end of the day (because it takes at least a day to work all through the various packages) I’m left with 20 half-built projects, a problem that still needs solving, and a 16 hour hole in my life. It’s not too much to ask for code to compile is it? Have I become so impatient in my old age that anything that takes more than 2 hours to do, isn’t worth doing?

Binaries, for all their non-accessible, non-editable, non-free faults, generally work much simpler. Especially under non-free operating systems such as Windows. Ironic? Stupid? Or good design?

Does it matter if I can’t change binary code? Not initially! I either just want to evaluate it, or I can write a plug-in. And most larger packages provide plug-in support since “extensibility" became the winning buzz-word bingo phrase of 2004.

Scripting languages often come with their own in-built package management tools to download and install their own libraries. The CPAN module from Perl is a very good working example of this. Okay—it breaks and messes up occasionally, but probably less than C code of similar complexity. The future’s probably in scripting languages and Java byte code as they have a working packaging system for their respective source code.

Unless the entire OS, and all its associated libraries and tools, have been built from source, it’s unlikely that user applications can be distributed effectively from source code. Gentoo was right, after all!

Alas, Gentoo is not as friendly as, say, Ubuntu.

Alas, Ubuntu is not as friendly to the compilation process as, say, Gentoo.

So unless (until?) a common packaging format is created, and every distribution and developer adopts it (and I do mean every one) we’re never gone win this battle. Makes you wonder if it’s worth winning...



Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

There are tens of thousands of Linux aficionados who will dismiss your article as senseless drivel but there are millions of average computer users who could not agree more!

The only problem is they don't read this since they gave up on using a free OS (not on free software entirely).

I installed my first Mandrake about 7 years ago, I bought books and I had all the code. Since then I've used Redhat, Vector Linux, Yellow Dog, Ubuntu, Gentoo, Knoppix - you name it I had it installed. I used parted to create and manipulate my partitions, chatted with an IBM developer and even earned a mention in the Credits section!

And after all that ? I still use Windows 95% of my time. I currently use Vector Linux because it is the only distro that has not fallen apart after I've installed or updated a core library. I've thrown anything at it except for kernel compilation.

You could say I've given up - and I would say you're right. Every distro had failed me (read: became unusable) in some way after I began customizing it to my desires:
- partitions
- sound configuration
- window manager updates
- boot loader configuration
- library installations / updates.

In a sense I didn't give up on Linux - it gave up on me and in the belief that an average Joe Schmoe could start it and use it without any repercussions.

Why all this? Because you have to be a developer to customize Linux - that is why. You have to understand how the computer works - it will never be a blackbox, which is what Windows successfully portrays today.

Some days I like to be a developer and play with it but most of the time I just want to be an average dude.

If I download a new library I want it in binary form, downloaded either with all dependencies (also in binary) because the download process detected they are missing on my system or without them. I do not want to compile it (that is already bad enough) and then get errors because of chain-link of dependencies in a parent-child formation. I usually give up after 3 hours disgusted because I just wanted to ride a bicycle but before I could do that I had make my own parts and build them together!

That is an overkill. The entire set of steps for distribution, code compilation, installation, configuration and updates NEEDS AN OVERHAUL.

There should a standard for everything (maybe some committee or something). All the stupid distros instead trying to be different and think different should be a Linux box first, and a distro second.

Give me SOMETHING that works the same GUARANTEED across the board of all distros. Amen.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

You go on about how you tried to customize things that an "average dude" would never do and then complain that it's too hard for the average dude? Downloading an application with automatic dependency resolution means using something like APT or YUM. Also, some projects actually do provide tar balls that contain their core dependencies. When was the last time that you installed Windows software from source anyway? I've been using Debian or years and haven't had to compile a single application since then. The chances are very high that someone already did that for you.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

There are a very large number of us who are happy Linux users who only use binaries. If I see a program only available as source code I consider it to not exist and ignore it. I don't feel I'm missing out on much, it's probably a beta or something difficult to use if they didn't bother with a package.

Ease of installation (and removal) is, for me, a significant advantage over Windows -- since I only deal with debs and rpms (95% of the time via an apt-get frontend), or the occasional standalone installer (like google earth's) which is merely the same as Windows.

I don't recall ever compiling a program on Windows either. Is it really easier? I wasn't even aware it included the tools to compile.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

You could say I've given up - and I would say you're right. Every distro had failed me (read: became unusable) in some way after I began customizing it to my desires:

In other words, building a stable OS is not trivial thing, so changing core infrastructure in a distribution around on a whim will lead to problems.

I always wondered why I always heard that FOSS is difficult and doesn't offer enough options. Now I know. We have end-users aspiring to do the things you normally leave to professional developers. So why would you freak around with your OS if you don't know the consequences and you are not willing to accept any?

Out of the box most distros are rock solid. Problems usually occur if you mix in third party software in the base system. Hence don't compile libraries from source and don't use untrusted repositories. Stability issues and dependency hell will ensue.

It's funny that when somebody borks his FOSS OS he always brings out the flawed comparison with Windows. "On Windows this never happens!" Well, of course it doesn't happen. Windows doesn't really offer options to break the system core (at least since Windows 2000). All external packages are written with only one (or two) Windows versions in mind. The platform is locked down against user tampering and only MS sanctioned updates appear on Windows Update. An end-user is forbidden to mess up the system.

With FOSS you are not prohibited from messing up the system. Just because you can compile and you have the freedom to replace core system files on your own, doesn't mean you should though. Not if you don't know and aren't willing to accept the consequences. Don't blame user error on GNU/Linux.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Agreed, I hate it in even fewer steps than three. But I take it you've read what Ian Murdock has to say about how software installation on Linux sucks (the LSB initiative etc):

"Software installation on Linux: Tomorrow, it won’t (with some cooperation) (part 2)"

Also, there is also and and stuff like that.

So, is there hope after all?

Hugo Heden

Raghu Kodali's picture

I feel that this is one of the main reasons for GNU/Linux not (yet) to be accepted by a vast majority of users as a desktop replacement for proprietary Operating systems.

After working on GNU/Linux for so many years, I could get most of the packages to compile (after a few hours of hacking Makefiles etc), but I still run into tarballs which just refuse to compile.

apt & yum might have solved this to some extent, but you are again in the open sea if the software you need is not available as a .deb.

./configure, make, make install is also a good way to check for source level dependencies. But this is also limited in its application.

Some standard needs to be created so that users need not worry about source compilation. It just should compile.

Raghu Kodali

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

You want my mother, who knows nothing about compiling software, to build software from source code?

We're talking about average users here, right?

The original author of this piece and those who agree with him are missing out on a huge point here: Average users do not install packages from source.

When I began using Linux in 1995, I had to learn how to build things from source on the system. I'm a programmer by trade, so it wasn't that great of a leap for me to become acquainted with the lay of the filesystem hierarchy, how the linker works, where the appropriate config files are, and the proper use of make and the GNU auto-tool chain.

However, you want to criticize every Linux distribution you've tried for failing to make things easy enough so that my mother, the average user, can install software from source?!?

That's an outlandish claim; show me a single popular program for OS X or XP that is compiled during installation. If you do, I will recant. If you cannot (and I don't believe you can), you need to seriously reconsider being critical of an operating system which gives you the ability to compile from source even if you have to read a manual to do so.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

(Are you moderating the comments? It should say so somewhere. Or did mine just disappear into cyberspace?)

Well, take a look at -- Ian Murdock and a lot of other people seem to agree and are working towards some kind of solution.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

There's autopackage, soon there'll be clicknrun and now there is some work done upon making binaries compatible with all systems :)


PS Please make this site openid compatible :(

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on


Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Someone said "rtfm".

If you're suggesting "rtfm" to Ian, then you need to get a clue, because Ian practically WROTE TFM.

Sometimes I wish people replying "rtfm" would drop dead.

chuck97224's picture

Yeah, I'm tired of hearing that "RTFM" crap too. It is nothing more that a "put down" by someone who hasn't actually RTFM. If they had RTFM, they would have posted a more intelligent reply.

Besides, there are very few "FM" that contain anything current and valuable. Let's face it. No one likes to write documentation. We all know that. We all know that because we are all like that.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Yeah, I'm tired of hearing that "RTFM" crap too. It is nothing more that a "put down" by someone who hasn't actually RTFM. If they had RTFM, they would have posted a more intelligent reply.

Besides, there are very few "FM" that contain anything current and valuable. Let's face it. No one likes to write documentation. We all know that. We all know that because we are all like that.

See solution #28740: OpenBSD, where TFM is up to date. However, I'm sure if you aren't willing to understand it, you will hate it even more than Linux.


Tyler's picture
Submitted by Tyler on

Unless the entire OS, and all its associated libraries and tools, have been built from source, it’s unlikely that user applications can be distributed effectively from source code. Gentoo was right, after all!

I haven't had much trouble with this, so I'm curious what your working on. Is it a problem with the program you want to install not being well written or clearly stating the dependencies? Or is it that your distro doesn't make it easy to get the libraries you need?

The only thing I've had to compile from scratch was the Phylip package. It had one dependency hitch, which required the X11 development libraries. Easily installed on Debian, and I'm off to the races. It was actually in the repos as well, but I need the latest version.

I suspect part of the problem is the new distros that cater to newbies. They focus on easy and quick installation, at the expense of the development support you need if you want to use anything outside of the repositories.


Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

... aren't compiling from source on *any* platform.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I personal feel that a large chunk of that 95% shouldn't be using a computer in the first place. Of course then I would be out of job, but truthfully most people are not able to really use a computer or want to use a computer. They just need a web kiosk or Cell phone. That is basiclly what the new Apple iPhone is, just the features that are most commonly used on a computer except games and that is what a game console is for.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Firstly I don't think that compiling from source is all that difficult,...if the developers have done a good job of packaging the application. I am not a programmer and I really only use Linux as an end user environment and I regularly compile programs from source code with little problems.

There are also attempts at creating a unified packaging system out there, an example is autopackage. It is a fairly easy way to install things, but only limited projects are using it for their applications.

Wouter Verhelst's picture

I can't really agree to this. Writing portable software is hard; it doesn't suffice to just make an attempt, you also have to test it. By definition, testing software for portability requires you to run it on a whole bunch of different platforms.

Usually it helps if you try two or three different platforms, but often even that is not enough...

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Hi, this is my first comment on here, even though I come across the articles via Digg.

Anyway, my suggestion would be GoboLinux.


Because, with its filesystem hierarchy and "Compile" utility (also known as a "poor man's Portage"), you can download and install applications in tar.gz form on the fly from any project website, all of it in GUI form.

Little dependency upon a managed, slow-moving repository of packages is needed.

So yeah, GoboLinux. Try it out.

Have fun.

cantormath's picture

This author is nothing but a microsoft advocate. This is not factual at all. 99% of people can go there entire life without building a single package. Open Source software just gives you the option, if you know how to build a package, to build a package. How does one build a package with non-FOSS (FREE OPEN SOURCE SOFTWARE)? AH!? you if it is not open source, it is have failed to mention that fact. The Open Source part of Open Source is for people that know how to build software....not for the point-click engineers, like yourself.

Face it. We are better then you, I am better, we are all better. You are upset that you know nothing about computing. You spend so much time writing articles about how stupid we are. ie)
You speak poorly about linux, and yet you DO NOT know how to use it at all. You cannot upset us or change us because we do what we do for the love of it. We do this to make the world a better place. Finally, as many will explain to you, there is more money in open source then in the other stuff.....just not for you.

You are only hurting yourself with this FUD ( Fear, uncertainty and doubt).

"As we open our newspapers or watch our television screens, we seem to be continually assaulted by the fruits of Mankind's stupidity."
-Roger Penrose

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I'm a simple computer user and i've tried a lot of distros in the last 2 years and couldn't find one who could be "user friendly" only "eye-candy". As a simple user i don't want to learn everithing about linux and how it works only for watching a movie or watching tv.. simple tings that don't work. A lot of users don't want to spend weeks just to make a program to compile/run... this is bullsh*t. You probably know too much and that blinded you from the truth... this is getting ugly and until someone steps in and say "this is enaugh! we don't need 10000 distros, we don't need to waste weeks of our times just to recompile software for so many distros" thing won't be so good...

Everione is looking for something simple, easy to work with and linux ain't that !

"Open Source is for people that know how to build software....not for the point-click engineers" well... there are a lot more "point-click engineers", than gurus like yourself. This is an excuse for letting linux evolve this way... it must change soon or it will get verry messy...

Steve's picture
Submitted by Steve on

Like another poster above, I've installed and used Red Hat, Yellow Dog, Gentoo, Ubuntu, and a couple others along the way. You'd think I'd have learned not feed trolls, but here I am.

I thought your post was a satire until I saw you had bothered to include a .sig. Of course, you've only had a username for 48 hours, so the jury is still out.

On to my point. If we really think Linux is better for both technological and philosophical reasons, that precludes us from being elitist assholes. Either we want people to use open source, or we don't want people to use open source. To limit it to some people isn't just arrogant, it's self-defeating.

The good news, open source is a whole ecosystem of software. If you want a distro that requires six hours and the sacrifice of a chicken to install an app, and your neighbor wants to be able to install it with one click, you can both have it.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Are you crazy? You're talking about IAN MURDOCK. Do you have a clue about who he is? Does Debian ring a bell to you? Debian is Ian's invention, and it has the single largest package repository on Earth.

Through your first sentence, your ignorance is showing blatantly.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I don´t agree with you. Just your first paragraph is true (and not even the last sentence)

I am a developer, I know how to handle the situations exposed here, and I still believe this author is right.

If you believe you are better than the author, go and demonstrate him that _you_ make things the way he says: I mean, you write your code, test it in several platforms, and make sure it can compile and execute in all of them. Then you can say "I am doing my job. If everyone did the same, things would be much easier, even for myself". That would be constructive.

On the other hand, I also prefer things that work "out of the box". I am willing to "improve" things instead of fixing them. So, if a previous developer does her job, then I can improve her job by doing mine equally well, and everyone benefits from it, even who you call a "point-click engineer", which probably includes yourself under certain circunstances :-)

Probably, even when you face this situation you get discouraged at first, just before going looking for a solution :-)

So, even if this is not a problem for you in the end, it is a field to improve.


PS: BTW, my grandma knows how to cook, do the laundry, iron, make kids grow up happily, and even how to play solitaires in a computer... don't ask her to understand how a computer works! (This can be useful in many other circumstances...)

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I have to agree with the opinions that say that you don't know what your doing. Secondly I have to say, that I don't want you to use linux. I think trying to make a robust environment simpler so that any old joe blow can use it just makes Linux more like Microsoft. We will run into the same problems and issues trying to make Linux easier. Personally I run I a gentoo box with fluxbox WM, I don't care about you Ubuntu noobs running KDE with every GUI app in the world but still can't configure your network card. Learn the system. LINUX IS NOT A DESKTOP ENVIRONMENT! It is a development and server platform.

Linux is not a Microsoft Killer and I don't want it to be, I want all those dumb jacks out there who don't want to learn to use a computer, to not pressure for development to make my platform weaker.

Thats my two cents.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Linux is not a desktop enviroment for you.... For me is the system with most potential to be the best desktop environment. We want it to be a desktop environment becouse it's free (becouse i don't want to pay for a software that cost more than my complicated electronic motherboard), robust and secure, especially secure (which means more money saving). I live in a country where is really hard to get a microsoft license, so I, a Ubuntu n00b (as you say), i want to use every GUI app in the world and still configure my network card.

Linux is about choice... Your choice is to use a distribution destinated for development, my choice is to use a distribution destinated for a nice, beautiful, stable desktop, that doesn't make our platform weaker.

Steve's picture
Submitted by Steve on

Linux has been my primary desktop for eight years now, and I'm not a programmer or a sysadmin.

Where have you been?

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

It's nice how some of you are worried that average users might reject GNU/Linux because of the troubles they have while compiling packages. Er, excuse me, how often do average users compile packages under GNU/Linux???

  1. All applications that average users need come pre-built, at the click of the mouse in their distribution's package manager
  2. Software developers (or those with skills in this area) will try cutting-edge packages from time to time and will have to build from sources. In my experience, for important packages, that's flawless most of the time.
  3. Granted, average Windows users usually don't have to worry about compilation. After all, it's part of the Windows spirit that they won't get the sources in the first place.
  4. Software developers are not gods and not all projects are equal. There are some projects of high quality, some of lower quality and some projects are still immature. If you download version 0.11 of any software--Windows or GNU/Linux or other--don't wonder if there are compilation problems. For stable applications, the build process will be stable too.

In my daytime job I'm a Windows software developer. When I pull up a year-old project from version control, I don't expect it to compile flawlessly. First, I'll have to find the correct version of the required third-party libraries, then I have to fix the drive letters that the previous developer forgot to remove from the build scripts--all under Windows. Software development is software development. Average users are average users. Keep the two separate.

ducttapeBigSexy's picture

I personally am a software engineering student, and I'm interning at a local software company that makes Windows software. And, trust me - compiling Windows software isn't easy either.

And, Steven, what distro have you been using? Most modern, user-friendly distros include a huge repo of software - plus, many times the official web site will include rpms or debs. Heck, if anything, I'd say Linux is easier - unlike Windows, most Linux distros come with additional software preinstalled, such as an office suite, Palm connectors, media players, etc. No having to wade through endless screens of an installation wizard.

And, Windows is pretty nasty, just in other areas. Honestly, is cleaning spyware infections out of the bowels of your registry really that easy? Or, sitting on the phone with Microsoft trying to get your product activated a good use of your time? Or, is that $200 dollars (at least) spent on a Windows license really a good use of your money?

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I fall out with distros too!
I never fall out because a TASK is unacheivable.
Of course the solution I have seen in XXYZ is beautiful but I can't compile the relevant library in XZYZ. Who gives a damn? If the pretty solution is better it will mean enough to someone (perhaps even me) to make it more widely available.
Open Source software is great. FOSS is Wonderful! I'm a c*** programmer an awful packager and an ok bug isolater. Some of my favourite tools have fallen by the wayside BUT the thing I got angry (excited?) enough about is available in every distro I have downloaded this year.
./configure make make install is what we try and hide from users BUT it is what keeps us all moving forwards. So point out those GPLed programs that you like but don't work for you and we'll try and fix them or find something better but be aware my better might be your worse. So ask someone else aswell!

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Where you can actually build everything (including the OS) from source, and it works.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

...this lump of comments has me convinced that vocally active morons should be neutered and their vocal cords excised. By government!

Never seen so many stupid baseless assertions and s*** slinging towards the author of the post (who is absolutely, squarely right).

I, too, refuse to do the make install dance. It's binary or it's nothing. Hopefully the LSB talks produce both a usable deployment API for ISVs, and better package management tools and aids for independent software writers to package their wares.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I've been using linux for almost 8 years and I have never compiled anything
because I never tried to compile anything and never desired to use something that needed compiling. When I was using Mandrake 7.x or 8.x, I would go to plf, add the repositories, then install the software with check boxes. Pretty much all software in existence was on either Mandrake or through the PLF repositories. Now I use Suse, and it is the same thing. I use Red Hat at work and Red Carpet works like a charm. That is 3 distros where the rules are:

1. Add a few repo's
2. Vuala

Maybe people who use Gentoo, Ubuntu and and Debian are masochists. Mandrake and Suse are popular with non-geeks for a reason. If some software doesn't have a repo, don't use it and wait till some masochists compiles it and adds it to the repos. Compiling isn't meant to be an end-user task.

Wouter Verhelst's picture

Compiling isn't meant to be an end-user task.
Exactly; I can only agree with that. Well -- with the above quoted last sentence, that is. Not with the assertion that "people who use Ubuntu and Debian are masochists". I know I use Debian, and I'm not a masochist ;-)

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

You have very succinctly stated a fundamental problem of open source that always seemed to bother me and no one else. I doubt there will ever be a single packaging standard (besides compiling code from a tarball) because every distro thinks its cool to reinvent package management.

If there was ever anything to miss from windows, it would be the binary installs. Sure, who knows what its doing to your system--installing coporate rootkits or wreaking dll hell--but it crams the package somewhere into the depths of "c:\program files" and usually didnt break your system. Can't say the same for my gentoo experience a few years ago.

I truly hope that the ever worshipped community will be infused with more people who just want stuff to work.

yalu_fvd's picture
Submitted by yalu_fvd on

Very true. It's been a complaint of Linux users for years, and the solutions provided up to now don't actually solve the problem, but are adding more complexity. The current system gives users a feeling of LESS controll instead of MORE controll. To quote my significant other "If it's not in Synaptic, I can forget about it". I don't even try to start explaining how to compile stuff.

The brighter side of the medal is that you can actually use package management, which is a safe and reliable way (in most distros) to install software. You are not forced to use dodgy installers which:

  1. don't clean up afted theirselves
  2. refuse to de-install (tried pushing "remove" button in config screen-software under windows on acrobat reader 5 minutes ago, told me that that program allready WAS installed (stupid me!)
  3. require changes to the system (putting stuff in the windows\[system[32]] directory, overriding certain registry keys,...)
  4. have no reliable way to record changes made to the system
  5. are 300 MB in size because everything's statically linked

The problem with the open source world is that there are many good standards but it's hard to choose which one to use (rpm-deb-...). So, we'll never agree on a standard packaging system. What are possible solutions and their respective problems?

Include some program in your distro that will install dependencies of a source package
It's actually not so very hard to write a system that searches for library dependencies during compile time. Actually, something like that exists for Debian: auto-apt. I tried it for a while and found it to be "imperfect":
  1. For most source packages it downloads truckloads of perl modules, whereas the program would also perfectly compile without
  2. You still have to go to the configure, make, make install thing, however there are tools that do this (such as Gnu SourceInstaller or something)
  3. No clean way of removing software, however it's a small step to run "checkinstall" over it to create a package of this
  4. Does only solve the dependency problem, you still have to ./configure --prefix=/usr/local/stow/foo-1.3 etc (don't tell me you install in /usr/local straight away).
  5. Gnu autotools aren't the only build tools available (unserbuild, scons, old-fashioned makefiles,...)
Use installer-builders like autopackage
  1. Autopackage inherits a lot of the problems of "setup.exe" and manages to add a few of his own (this stuff installs in /usr by default!).
  2. Nobody actually uses it
  3. Nobody probably will use some means of resolving dependencies at source level, in the tarbal itsels (besides, how canyou differentiate between dependencies added by soruce installation and dependencies in the distro? What about dependencies on a specific version, like say: xpackage1.2 when 1.2.34 is installed by means of a package,...?

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I feel your pain. I see from the replies it did not take long for "well my distros package manager...." or "xxx distro can build anything" or "why would the average user....." crop up.

Regarding the first. There are times you might want to try some app that isn't in your distro package manager. Duh. And the only thing you can get is a tarball.

Regarding the second, my distro can compile anything is bullshit. Not if the Makefiles or configure for example have a built in check that won't compile because one of your auto tools is to new a version. Sure you can get it to work but not without fangling configure or whatever. Seen that one now 3 times.

Regarding the third. Just what the hell is an average user anyway? Everytime I see that excuse invariably the image of Arthur Dent springs to mind trying to use his digital watch.

So do we need a common package management? No not really. The various distros already have theirs and most times they work. When they don't work, personal experience tells me it has almost invariable been from some error introduced by the person building the package and not the package management code itself. I suppose though for binary distros it might be useful.

Do we need one for source code building? No not really. As the article mentioned there are the autotools stuff and for the most part works just fine. It's just getting the code authors to actually use them might be the hard part.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

What is this tripe?

Sounds like someone couldn't get something to compile and decided to throw a hissy fit and call it news. No constructive suggestions. Not even any reasonable identification of the "problem", just a lot of misunderstandings and blathering.

For the seventeen zillionth time, "So unless (until?) a common packaging format is created, and every distribution and developer adopts it (and I do mean every one) we’re never gone win this battle." is just flat out wrong. Packaging formats are IRRELEVANT. It's just as unlikely that you'll be able to use Red Hat packages on SUSE as it is that you'll be able to use Ubuntu ones - even though Ubuntu uses .deb, and both SUSE and Red Hat use .rpm. Why? BECAUSE THEY'RE DIFFERENT SODDING DISTRIBUTIONS. They package things differently. This makes up rather a lot of the difference between distributions. Even if they all used the same package format you STILL couldn't throw packages from any distro onto any other and expect it to work. So stop beating the wrong dead horse and get a freaking clue already.


Get it packaged, or package it yourself, or just deal with the issues of building from source and quit whining about it. Jeez. The problem is that source code is a sucky method of distributing software to end users. This is hardly news. The solution is to USE OTHER METHODS OF DISTRIBUTING SOFTWARE TO END USERS, which is what distributions have been doing ever since they were created (hell, that's WHY they were created in the first place), and something they're generally rather good at.


Neil Darlow's picture

I believe there are two root causes to the difficulty experienced by the author in compiling software from source on a GNU/Linux distribution:

1) Software developers can choose to make their software compile provided all required dependencies are available or they can go full-out to support building on multiple flavours of GNU/Linux. The former has advantages for software that aims to be cross-platform (by which I mean GNU/Linux, *BSD, MacOS X etc. but not necessarily Windows) the latter serves to make life easier for distribution packagers and those who routinely install from source. Neither approach is bad but the former case might be perceived as better for making software available to a potentially larger audience.

2) GNU/Linux distributions do different things with their packaging and filesystem placement. Taking the need for dependencies as an example, Debian might split a piece of software 3 ways into separate packages i.e. basic libraries, runtime required or utilities and development headers. You might need 2 or all 3 of these packages to satisfy building of software from source and it's your responsibility to install them.

I have used several GNU/Linux distributions (Red Hat, Debian, Mandrake, Gentoo and Ubuntu) with at least two years spent with each of them. In almost all cases I have had occasion to install software from source but this was always possible provided the required supporting and development packages for the particular distribution were installed beforehand. Often I had to read the documentation accompanying the source archive to determine which dependencies were required - diving straight into ./configure isn't always the best way to proceed.

To cite a recent experience, on Ubuntu, I found it necessary to build two kernel modules from source. These were for a PCI Wireless adapter (RT61STA) and Webcam (gspca). In both cases, Ubuntu provides broken support for the devices I chose to use and building from source was the only way to make them work. This was simply achieved through installing build-essential and kernel-headers packages. OK, building a kernel module requires less in the way of dependent libraries than your typical software application but the principle is the same.

The moral of this is that building from source, under a packaged GNU/Linux distribution, should be undertaken with due care to the requirements of the software being built. This includes determining precisely what dependencies are required, what packages will satisfy them and what, if any, modifications the distribution has made to those dependent packages that might prevent a build from source completing successfully.

Mitch Meyran's picture

Personally, I had to compile packages here and there. Usually,

- you don't have to start compiling software right away; many times, distros that use similar packaging systems can share their packages. As such, I had several successes installing SuSE 32-bit packages on a Mandriva 64-bit system...

- it helps to find the software's requirements: .configure will usually spell them out to you. If it doesn't, then yes, you can get angry at the author (but then, you should also peruse as much of the README and author notes as you can)

- it helps to define your library paths: when you're not using the same distribution the developer did, you need to know that stuff like /usr/lib, /usr/share/lib, /usr/local/lib, /usr/lib64 etc. may be different from one distro to the other

- if you can't find the software for your architecture, you may be forced to compile from sources: say, a i386-optimized software for your AMD64 platform. But then you ask for trouble.

- don't forget to install -devel packages! Many compilation problems may come from the absence of header files

Under Windows, you may have trouble finding a compiler, you WILL have trouble installing an IDE, and you WILL have DLL conflicts. I prefer Linux 'compile it if you really want it' approach to M$'s "you won't compile it, your system belongs to us".
A computer is like air conditioning: it becomes useless when you open windows.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Gentoo is getting a lot more user-friendly than it used to be - the preferred method of installation is a graphical installer, which even has the option of installing GNOME, KDE, or Xfce for you initially (with other useful things too). It has some graphical package managers coming along too, and there's work being done on a faster portage. So it's not so difficult to use gentoo as you say.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

The software needed by most people already is compiled and available in Linux repositorires at least if you use some of the larger distros like Red Hat/Fedora/Centors, Novell/Suse or something Ubuntu/Debian.
If its not in the preconfigured repositories of your distro, there it is most likely available in other third party repositiories such as freshrpm (if you use fedora).

Compiling software is for developers and packagers, and it works resonably well for people with the right skills. This is probably the problem, it works so well that people without the necessary skills actually tries to do it, and even get away with it quite frequently.

On windows and even MacOS-X we don't have this problems because most people will get utterly stuck on installing and configuring the necessary development tools to compile software from source. So they never dream of installing something on the bleeding edge. Instead they wait until it gets packaged as an easy installed package. Perhaps Linux users should do the same.