[Ffmpeg-devel] build broken again...
Tue May 10 04:07:52 CEST 2005
On Tue, May 10, 2005 at 02:56:09AM +0200, M?ns Rullg?rd wrote:
> Daniel Serpell <daniel_serpell at yahoo.com> writes:
> > Hi!
> > 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
> > assigned.
> I've seen attempts at such schemes in several old Unix versions. In
> addition to being inconvenient, it is bound to fail if the total size
> of all libraries (on one system) should exceed the address space size.
I agree, it's stupid...
> > And you know, in that times userspace Linux was faster and smaller ;-)
> Perhaps it used less clock cycles, but the overall speed was still
> slower, and perhaps it was smaller, but it did less things. You
> didn't run KDE on your a 386, you ran something like fvwm.
I wouldn't run KDE on an ath64 either, given the choice between it and
fvwm. For those who don't know, fvwm is still the cleanest, most
customizable window manager, and it's very light.
More information about the ffmpeg-devel