Welcome to the Linux DLL hell!


/* The complete definition of png_info has, as of libpng-1.5.0,
 * been moved into a separate header file that is not accessible to
 * applications.  Read libpng-manual.txt or libpng.3 for more info.
 */
That is why you should always statically link all libararies or use .Net, else some retarded maintainer will break you app "just for fun".

`>Welcome to the Linux DLL hell!

But Linux doesn't use DLLs!!!!

>>35
/usr/lib*.so

>>36, >>35-san's point is still valid.

>>37
???

>>38
allow me to give you a little hint right here, my little less-gifted autist:

Linux:   .so, called shared objects
Windows: .dll, called dynamically linked library

>>39
so?

>>40
Linux uses shared objects, as opposed to dynamically linked libraries.

>>41
Stollman uses GNU/Linux, as opposed to just Linux.

I'd like to say that I've used Windows since Win95 and have never encountered any "DLL hell" as they describe it. When a program says a DLL is missing or imports are not found in one, I just Google the filename, download it and put it in with the .EXE and it works.

But on Linux... >>24 is right. I find libxyz.so, put it in, program complains it's the wrong version. CAN'T YOU AT LEAST GIVE IT A FUCKING TRY FIRST?

>>43
You're not very good at trolling.

>>28

haha thanks, but it would take a while to do, so you'd have to be able to justify the time investment. It's obviously not necessary for something that is open source, or if you just happen to have access to the source code.

>>37
hax my anus