On 12/13/14, Carl Eugen Hoyos <ceho...@ag.or.at> wrote:
> Clément Bœsch <u <at> pkh.me> writes:
>
>> > > > Attached patch fixes ticket #4183.
>
>> > --libdir=DIR install libs in DIR [PREFIX/lib]
>> > - --shlibdir=DIR install shared libs in DIR [PREFIX/lib]
>> > + --shlibdir=DIR install shared libs in DIR [LIBDIR]
>
>> What if LIBDIR is not defined? (is it possible?)
It is supposed to be set by the previous option (--libdir).
Just like there is no PREFIX env var, but it is the value set by the
--prefix option.
Probably "[same as --libdir]" would be easier to understand, but it
would not be consistent with the rest of how [] is used in configure
help. And if you go that way, how would you describe the --libdir
default?
"[ --prefix/lib]"
"[ ${--prefix}/lib]"
"[ ${prefix}/lib]"
"[$prefix/lib]"
"[$PREFIX/lib]"
"[PREFIX/lib]"
Hum, actually, I kind of like the 3'd one.
> I believe you misunderstand (there are no shell
> variables involved afaict).
>
> I am not claiming that I am sure this patch is a
> good idea (I am against behaviour changes) but
> this was reported by a user and I believe the
> patch does what the user wants so a decision will
> have to be made: Either close as wont-fix or
> apply this (or a similar) patch.
autoconf handles a single --libdir and people do expect that other
configures work in a similar way.
Please, commit your current patch.
BTW, another possible solution is to remove --shlibdir entirely. Is
that option even used/useful?
Best Regards
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
