svn commit: r394871 - in head: Mk mail/thunderbird mail/thunderbird/files www/firefox www/firefox-esr www/firefox-esr/files www/firefox/files www/libxul www/libxul/files www/seamonkey www/seamonkey...

[Jan Beich]

John Marino <freebsd.contact at marino.st> writes:

> On 8/20/2015 5:15 PM, Jan Beich wrote:
>
>> John Marino <freebsd.contact at marino.st> writes:
>>> By switching the comparison from < to >=, I think this just broke
>>> DragonFly which does not support jemalloc on any version.
[...]
>> My intent is to make DragonFly use bundled jemalloc like older releases
>> of FreeBSD. Try applying below commit under ${WRKSRC}/memory/jemalloc.
>>
>> https://github.com/jemalloc/jemalloc/commit/1aa25a3

The change is part of Firefox 37.0.

https://hg.mozilla.org/releases/mozilla-release/diff/b5b1a8e8aee4/memory/jemalloc/src/configure.ac#l1.115

> Why?  jemalloc has never worked on DF.  Ever port with jemalloc support,
> bundled or otherwise fails.

Can you be less vague about brokeness? My quick search only turned up an
ancient irrelevant issue about soon to be removed Mozilla's fork[1]. The
ports never used the fork as it's known to be broken even on FreeBSD[2]. To
be specific --enable-jemalloc without MOZ_JEMALLOC3=1 was never supported
due to severe bitrot of MOZ_MEMORY_BSD[3].

I wonder why bundled jemalloc within lang/rust-dragonfly works fine.

[1] https://bugs.dragonflybsd.org/issues/1532
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1153683
[3] (DPorts carries pointless patch-configure.in for it)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 602 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20150820/84b4112a/attachment.bin>