Re: Upstreaming FreeBSD ports patches before 4.2.0?

2018-04-28 Thread Damjan Jovanovic
Great, thank you. No idea. Either Sun/Oracle never got around to implementing it, or they planned on scrapping it. On Sat, Apr 28, 2018 at 4:51 AM Don Lewis wrote: > I just committed a fix for this in r1830406. > > Without this I get build failures due to crashes in the unit tests if > --enable

Re: Upstreaming FreeBSD ports patches before 4.2.0?

2018-04-27 Thread Don Lewis
I just committed a fix for this in r1830406. Without this I get build failures due to crashes in the unit tests if --enable-debug is specified. With this change I am able to get a working build with both the system alloc and the internal alloc. I was unaware that this was not getting used on the

Re: Upstreaming FreeBSD ports patches before 4.2.0?

2018-04-16 Thread Damjan Jovanovic
Hi It should be an easy fix, we just #include that file that the boost upstream commit deleted from its includes, into our files that need it. On Mon, Apr 16, 2018 at 4:13 PM, Pedro Giffuni wrote: > Hi guys; > > Just to let you know, OpenOffice is about to break in FreeBSD due to a > boost upda

Re: Upstreaming FreeBSD ports patches before 4.2.0?

2018-04-16 Thread Pedro Giffuni
Hi guys; Just to let you know, OpenOffice is about to break in FreeBSD due to a boost update: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227553 No fix (yet) :(. Pedro. - To unsubscribe, e-mail: dev-unsubscr...@openo

Re: Upstreaming FreeBSD ports patches before 4.2.0?

2018-04-14 Thread Damjan Jovanovic
Alright thank you. Would it be better to just scrap cpprt, like gbuild modules already do? On Sat, Apr 14, 2018 at 4:59 PM, Don Lewis wrote: > On 14 Apr, Damjan Jovanovic wrote: > > Hi > > > > Can we please upstream the patches from FreeBSD ports, before the 4.2.0 > > release? > > > > That idlc

Re: Upstreaming FreeBSD ports patches before 4.2.0?

2018-04-14 Thread Don Lewis
On 14 Apr, Damjan Jovanovic wrote: > Hi > > Can we please upstream the patches from FreeBSD ports, before the 4.2.0 > release? > > That idlc memory alignment SIGBUS crash from > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216206 is Clang specific, > not FreeBSD specific, and could happen on