Will we get a RELEASE-9.1 for Christmas?

[Scot Hetzel]

On Thu, Dec 13, 2012 at 12:29 AM, Matthew Seaman <matthew at freebsd.org> wrote:
> On 12/12/2012 23:17, Walter Hurry wrote:
>> That looks like a useful feature. But why is it saying this?
>>
>> pkg: (firefox-17.0.1,1) shared library libxpcom.so not found
>> pkg: (firefox-17.0.1,1) shared library libmozalloc.so not found
>> (lots more output snipped)
>>
>> $ locate libxpcom.so
>> /usr/local/lib/firefox/libxpcom.so
>> $ locate libmozalloc.so
>> /usr/local/lib/firefox/libmozalloc.so
>> $ file /usr/local/lib/firefox/libxpcom.so
>> /usr/local/lib/firefox/libxpcom.so: ELF 64-bit LSB shared object, x86-64,
>> version 1 (FreeBSD), dynamically linked, stripped
>> $ file /usr/local/lib/firefox/libmozalloc.so
>> /usr/local/lib/firefox/libmozalloc.so: ELF 64-bit LSB shared object,
>> x86-64, version 1 (FreeBSD), dynamically linked, stripped
>> $
>
> Ah -- that would be a bug.  At a guess, it's not finding the shlibs
> because they're in a location not on the usual path and there's
> something odd about the RPATH settings in the binaries.  I shall
> investigate further.
>
This same issue with firefox was reported in this PR:

http://www.freebsd.org/cgi/query-pr.cgi?pr=131237

And included a simple fix which was rejected by the firefox maintainer
due to firefox sets LD_LIBRARY_PATH at runtime to find its share
libraries.

-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.