Janne Grunau <[email protected]> writes:
> On 2012-11-29 01:01:15 +0000, Måns Rullgård wrote:
>> Sean McGovern <[email protected]> writes:
>>
>> > The Solaris -rpath linker option parser is greedy.
>> > ---
>> > configure | 5 +++++
>> > 1 file changed, 5 insertions(+)
>> >
>> > diff --git a/configure b/configure
>> > index f094a32..79e4897 100755
>> > --- a/configure
>> > +++ b/configure
>> > @@ -3622,6 +3622,11 @@ case $target_os in
>> > plan9)
>> > add_cppflags -Dmain=plan9_main
>> > ;;
>> > + sunos)
>> > + # The Solaris linker doesn't understand -rpath-link
>> > + # but does accept -rpath with the rest of the option string
>> > + LDFLAGS=$(filter_out '-Wl,-rpath-link*' $LDFLAGS)
>> > + ;;
>> > esac
>>
>> If this option doesn't work, how does the link editor find the right
>> libraries? Alternatively, if it works without that option, why do we
>> pass it at all? I tested it on Linux, and everything links properly
>> without this flag (and no libav libs elsewhere on the system).
>
> -rpath-link is required to link shared libs when incompatible
> versions of the same lib are installed in the runtime linker's
> search path.
The manual suggests otherwise:
When the linker encounters such a dependency when doing a
non-shared, non-relocatable link, it will automatically try to
locate the required shared library and include it in the link, if
it is not included explicitly. In such a case, the `-rpath-link'
option specifies the first set of directories to search.
We do specify all the dependencies explicitly.
--
Måns Rullgård
[email protected]
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
