Date: Thu, 6 Mar 2014 12:04:28 +0000 (UTC) From: "Thomas Mueller" <mueller6724@bellsouth.net> To: freebsd-current@freebsd.org Subject: Re: firebox build fails post clang-3.4 merge Message-ID: <59496.102.bm@smtp118.sbc.mail.gq1.yahoo.com> References: <201402282340.s1SNeXGU098039@gw.catspoiler.org> <E318A9A5-5407-42A4-A329-3ABA24337DFD@FreeBSD.org> <260788.30748.bm@smtp116.sbc.mail.ne1.yahoo.com> <0971DC13-A357-4CA8-87E8-E26F4661E4FA@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Does this mean the bug is fixed in 11-current?
> Yes, the bug is fixed in 11-CURRENT, as of Subversion revision r262809.
> > MFC? Is that to 10-STABLE? Your message is less than clear.
> In FreeBSD, fixes are first applied to head (a.k.a -CURRENT), then
> after a certain period they are merged to one more -STABLE branches,
> depending on the type of fix. This procedure is traditionally called
> a Merge From Current, MFC.
> In this particular case, I will merge the fix to both 10-STABLE and
> 9-STABLE. Older branches do not have clang, so merging the fix to
> them makes no sense.
> > I figure if firefox build fails, the bug would affect some other ports as well.
> Don Lewis already mentioned the libxul port, and in general, any port
> based on certain parts of the Mozilla source tree could be affected.
> -Dimitry
Thanks for response, but I went to FreeBSD website, got to mailing-list archives, in this case, svn-src-head.
This made me feel safe that the bug was fixed, and I can rebuild 11-head system.
But my last update might have been before the now-squashed bug was introduced.
Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59496.102.bm>