Date: Sat, 14 Nov 2015 15:16:20 -0500 (EST) From: Louis Epstein <le@main.put.com> To: Jan Beich <jbeich@vfemail.net> Cc: "Marat N.Afanasyev" <amarat@li.ru>, Steve Wills <swills@freebsd.org>, <gecko@freebsd.org> Subject: Re: Seamonkey port? Message-ID: <20151114151202.U48335-100000@main.put.com> In-Reply-To: <8u65-ordq-wny@vfemail.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Nov 2015, Jan Beich wrote:
> "Marat N.Afanasyev" <amarat@li.ru> writes:
>
> > Jan Beich wrote:
> >
> >> So, try building with USE_MOZILLA=-opus again after
> >>
> >> $ sed 's,^[-+]\{3\} ,&mozilla/,' \
> >> ../firefox/files/patch-z-bug517422 \
> >> >files/patch-z-bug517422
> > I have successfully build seamonkey with this patch and
> > USE_MOZILLA=-opus, but it coredumps as soon as starts and tries to
> > restore session. I suppose that opus nowadays is one of core elements
> > of mozilla :(
>
> It doesn't crash here and I'm using 11.0-CURRENT amd64. Without
> stacktrace only guesses. For one, system jemalloc detection is very
> simple and doesn't notice subtle changes in API[1]. --enable-jemalloc
> should toggle bundled version but only works with MOZ_JEMALLOC3=1
> on FreeBSD[2].
I'm using 10.1.-RELEASE-p24.
A revision of the ports tree today updated Seamonkey from 2.33.1_8
to 2.33.1_9 but did not install with portmaster (there was also a
revision of Firefox that I did not attempt to install).
Firefox is at 41 in the ports tree but Seamonkey has yet to reach
2.35 or 2.38 (while Seamonkey 2.39 and Firefox 42 are the current
releases).
In the past I have been able to install Seamonkey revisions that did
not work from ports with pkg upgrade
but pkg always lags ports in latest available version (it wants to
downgrade today's ffmpeg and libvpx revisions).
Mention of Seamonkey 2.38 appeared in /usr/ports/UPDATING on October 6!
> The following patch is a workaround for bogus MOZILLA_VER with seamonkey.
> Otherwise, if != is allowed to pessimize |make describe| one could define
> in www/seamonkey/Makefile instead.
>
> # Examples: 2.33.1 -> 36, 2.35b1 -> 38, 2.38 -> 41
> MOZILLA_VER!= let ${DISTVERSION:C/^2\.([0-9]+).*/\1/} + 3
>
> Index: Mk/bsd.gecko.mk
> ===================================================================
> --- Mk/bsd.gecko.mk (revision 399872)
> +++ Mk/bsd.gecko.mk (working copy)
> @@ -136,7 +136,8 @@ MOZ_EXPORT+= MOZ_JEMALLOC3=1
> # system jemalloc 4.0.0 vs. bundled jemalloc 3.6.0-204-gb4acf73
> EXTRA_PATCHES+= ${FILESDIR}/extra-patch-bug1125514
> . endif
> -.elif ${OPSYS} != FreeBSD || ${OSVERSION} < 1000012 || ${MOZILLA_VER:R:R} >= 37
> +.elif ${OPSYS} != FreeBSD || ${OSVERSION} < 1000012 || \
> + ${MOZILLA_VER:R:R} >= 37 || ${MOZILLA} == seamonkey
> MOZ_OPTIONS+= --enable-jemalloc
> .endif
> .endif # !DragonFly
>
> >
> > I think that porting 2.39 would be more interesting now. What firefox
> > release uses the same codebase as seamonkey-2.39? They forgot to
> > mention this on release information page :(
>
> See mozilla/config/milestone.txt. Firefox X is often SeaMonkey 2.X-3
> e.g., Firefox 36 == SeaMonkey 2.33 or Firefox 41 == SeaMonkey 2.38.
>
> --
> [1] https://lists.freebsd.org/pipermail/freebsd-gecko/2015-July/005557.html
> [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1153683
>
-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151114151202.U48335-100000>