2008/148: new ldd(1) -p option

[Rod Evans]

James Carlson wrote:
> Rod Evans writes:
>>    % cat mapfile-extern
>>    {
>> 	global:
>> 		mdb_zalloc =          EXTERN;
>>                  mdb_free =            EXTERN;
>>                  mdb_vread =           EXTERN;
>>                  ...
>>    };
> 
> If the symbols have been explicitly classed such that they're supposed
> to be resolved by the parent, then why should ldd complain about them
> in the first place?
> 
> Why is "-p" needed, rather than just making that behavior the default?
> Isn't the "EXTERN" tag enough information?

You're not the first to make this observation :-)

Yes, the new ldd(1) functionality could be implemented as
the default behavior, and thus error messages that used to
occur would magically disappear.  As usual, I was concerned
that any change in existing behavior might be noticed, and
perhaps unappreciated by one or two.

And thus I also had the fear that someone might ask for a
new option (-p :-) to re-expose the symbols that aren't
explicitly defined by their present dependencies, but were
expected to be found somewhere from the objects callers.

Hence my direction - but I could be easily swayed.

-- 
Rod