Isn't the main issue whether these are blockers or not? > On Oct 26, 2018, at 3:39 PM, Don Lewis <truck...@apache.org> wrote: > > On 26 Oct, Jim Jagielski wrote: >> >> >>> On Oct 26, 2018, at 2:30 PM, Don Lewis <truck...@apache.org> wrote: >>> >>> The redland/raptor/rasqal upgrade >>> https://bz.apache.org/ooo/show_bug.cgi?id=127887 got backed out. >>> Someone with a Mac needs to see if the configure.in changes are needed >>> or if it builds on a Mac as-is. > > When we upgraded those in trunk, it broke the Mac build. You committed > this change https://svn.apache.org/viewvc?view=revision&revision=1805089 > to unbreak things on the Mac, which include some changes to > configure.ac. AOO416 has configure.in instead of configure.ac, so in my > instructions for merging this upgrade back to AOO416 here: > https://bz.apache.org/ooo/show_bug.cgi?id=127887 I said to hand apply > the configure.ac changes to configure.in. That broke the buildbot > builds at the configure stage due to shell syntax errors: > https://ci.apache.org/builders/openoffice-linux64-41x/builds/159/steps/configure/logs/stdio > so the entire upgrade was backed out of AOO416 with r1843571. > > The question is whether we can merge the four commits from trunk to > AOO416 and skip the configure changes and get a successful build on the > Mac, or do we need to do some other change to configure.in to get a > successful build. My testing without any configure.in changes worked on > Linux and Windows. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
