Re: hardcode_direct_absolute description

[Bruno Haible]

Albert Chin-A-Young wrote:
> > 2) If DIR is a relative pathname, it is first made absolute before being
> >    hardcoded in the binary. In other words, it's not
> > DIR/libNAME${shared_ext} which is hardcoded, but `cd DIR &&
> > pwd`/libNAME${shared_ext}.
>
> Really?
>   $ cc a.c /opt/TWWfsw/zlib11/lib/../lib/libz.sl
>   $ chatr a.out
>   ...
>          shared library list:
>              static    /opt/TWWfsw/zlib11/lib/../lib/libz.sl.2
>              dynamic   /usr/lib/libc.2
>   ...

OK, you got me. I only meant to say that if DIR is not an absolute pathname,
the current directrory is prepended. As you point out, ".." (and probably
symlinks too) are apparently not resolved at link time.

Bruno