tech-toolchain archive

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

Re: Sets, subsets, syspkgs, and MK*

On Dec 18, 2009, at 1:22 PM, Aaron J. Grier wrote:

> On Tue, Dec 15, 2009 at 10:55:44PM +0900, Masao Uebayashi wrote:
>> My point is to realize that most USE_* variables change signature
>> globally.  USE_YP even changes libc signature.
> - contents of library files and list of files in distribution are both
>  affected by USE and MK variables.
>> We should audit all those use and make them modular == no signature
>> change but be "subsets".
> I think you are looking for general case solution.  for first draft of
> binary patches, assume that library signatures do not change.  for
> second draft, create a method to determine MK variables from individual
> library.
> making these "subsets" is very intrusive to a lot of code, and does not
> allow size savings.  code can be moved to libYP, but in order to keep
> libc same between MKYP=yes and MKYP=no, libc must continue to have all
> YP code in it.

Not true.  libc must simply have entry points which will dynamically load and use its routines via dlsym.  I've done that in the past and it 
works surprisingly well.

Home | Main Index | Thread Index | Old Index