tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: 64 bit time_t changes

On Thu, Mar 27, 2008 at 11:39:19PM +0000, David Holland wrote:
> Since there might exist libs that legitimately don't record a
> dependency on libc, such as maybe app plugins, and new such libs might
> be compiled after the version bump, assuming that every libc-less
> library image really depends on isn't safe.

Does such a dependency help at all ?
If the dependency causes to be loaded into a program that
itself is linked with all hell will break loose - unless
all the function names are versioned as well.

The only way is to mark all new binaries as being incompatible with
any existing binary so they can't exist in the same program.
> So I think what we need to do is write a tool that inspects old libs
> and inserts a dependency record if the lib uses any libc
> symbols. (This is not *completely* foolproof - a library might do
> something inane like use only stdio macros - but probably sufficient.)

That is likely to be impossible unless the linker reserved space in
the elf string table (which it doesn't).


David Laight:

Home | Main Index | Thread Index | Old Index