On 25/09/2015 Pedro Giffuni wrote:
I think it may be desireable to upgrade coinmp in AOO410 and with that
we would solve the issues for people(/buildbots) doing complete builds.
I see you have just committed this to AOO410, but remember: we are not
freely committing to AOO410 at the moment (ev
Hello;
On 09/25/15 12:35, Don Lewis wrote:
Using the FreeBSD ports framework, I am able to successfully build
AOO410 branch revision r1705179 on FreeBSD 9.3, 10.1, and 11.0-CURRENT,
on both i386 and amd64. The only required patch is a tweak to the
optimization flags to avoid a bug in clang 3.6
Using the FreeBSD ports framework, I am able to successfully build
AOO410 branch revision r1705179 on FreeBSD 9.3, 10.1, and 11.0-CURRENT,
on both i386 and amd64. The only required patch is a tweak to the
optimization flags to avoid a bug in clang 3.6 on i386. I use exactly
the same patch when bu
OK this is my list:
r1591501, r1602791, r1669457, r1669459, r1669465, r1694132
It only touches FreeBSD related build issues:
M main
M main/bridges/source/cpp_uno/gcc3_freebsd_intel/cpp2uno.cxx
M main/bridges/source/cpp_uno/gcc3_freebsd_intel/except.cxx
M main/bridges/sour
Pedro Giffuni wrote:
People shouldn't volunteer other people unless tey are also giving them
the means to contribute ... I think.
Status of that item (buildbots) is "Done". Don's name is there for
recognition of the already done work.
Using the buildbots for the release (even not considering
On 09/24/15 11:56, Don Lewis wrote:
On 24 Sep, Pedro Giffuni wrote:
Hi Andrea;
It did catch me somewhat off-guard that the release is not branched from
trunk. It basically means that some changes that have been in the tree
for over a year won't be included into the next release.
I don't real
On 24 Sep, Pedro Giffuni wrote:
> Hi Andrea;
>
> It did catch me somewhat off-guard that the release is not branched from
> trunk. It basically means that some changes that have been in the tree
> for over a year won't be included into the next release.
>
> I don't really want to spend time mergi
Pedro Giffuni wrote:
It did catch me somewhat off-guard that the release is not branched from
trunk. It basically means that some changes that have been in the tree
for over a year won't be included into the next release.
Yes, this is actually quite normal (well, let's say "usual"!): I mean,
4
Hi Andrea;
It did catch me somewhat off-guard that the release is not branched from
trunk. It basically means that some changes that have been in the tree
for over a year won't be included into the next release.
I don't really want to spend time merging changes to the 410 branch, but
I will be
