On 21 Oct, Matthias Seidel wrote: > Am 21.10.20 um 17:43 schrieb Jim Jagielski: >> Should that fix be just: >> >> <xsl:if test="string-length($shift)!=0"> > > https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09 > > Really looks like a candidate...
I doubt it. Unless you are building on CentOS 5, writerfilter/.../inc/doctok/resources.hxx is identical with or without this commit. On CentOS 5, resources.hxx differs, and causes a compile error because it contains the correct C expression "something >> ". I didn't commit this change to trunk or AOO42X because the problem only shows up when building on CentOS 5. Also, I believe that we've seen this problem previously on trunk and/or AOO42X that does not have this commit but the problem has mysteriously gone away, and it seems to be related to the combination of what OS the build was done on and what OS the resulting binaries are run on. I've done testing on CentOS 5, CentOS 7, Debian stretch and a bit of testing on Ubuntu and have never run into this problem, *but* I've always run the binaries on the same OS where they were compiled. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
