[Ffmpeg-devel] build broken again...

Daniel Serpell daniel_serpell
Tue May 10 02:06:55 CEST 2005


El Mon, May 09, 2005 at 11:46:39PM +0200, M?ns Rullg?rd escribio:
> A non-PIC library, as the name implies, must be loaded a specific
> address in memory.  The first time it is mapped, a text relocation
> might fix the problem, but if another application needs the same
> library, and already has mapped something else at that location, there
> is nothing to be done, except making a new copy.

Ah, seems you don't remember the "a.out" times, when distributions had
to select non-overlaping address ranges to the libraries, so each copy
could be shared. Common libraries had their addresses universally

This paragraph is from 1995:

   A list of registered shared libraries can be found in the tools 2.16
   distribution in the directory doc/table_description. Examine this file
   when defining the load address for a new shared library to ensure that
   it doesn't conflict with the address for an existing library.
   In addition, you should probably register the address space used by a
   new shared library so that future libraries will not conflict with it.
   Registration is particularly important if the library is to be

And you know, in that times userspace Linux was faster and smaller ;-) 


More information about the ffmpeg-devel mailing list