On 21 Oct, Don Lewis wrote: > On 21 Oct, Jim Jagielski wrote: >> >> >>> On Oct 21, 2020, at 4:21 PM, Andrea Pescetti <pesce...@apache.org> >>> wrote: >>> >>> It looks like we are getting closer.... I mean, we have a commit that >>> is only relevant to CentOS 5 and we know that Jim's builds are done >>> on CentOS 5 and have the bug, while the others (mine on CentOS 7; >>> Pedro's on Ubuntu 18) do not have it. >>> >>> Possibly some build error that goes unnoticed due to a "dirty" build? >>> Otherwise I can't explain why Don's CentOS 5 tests passed... >>> >> >> I don't think anyone else tested Don's CentOS5 built builds... just >> himself. I think. > > I only tested my CentOS 5 build on CentOS 5. I think the problem only > occurs when running a CentOS 5 build on something newer (Ubuntu only?). > This sort of smells like a system library incompatability of some sort. > Things work when the build is done using the system headers that match > the destination environment, but the problem crops up if the build is > done with the CentOS 5 headers but the runtime libraries are from a > newer distro. The mystery is what changed between 4.1.7 and now to > trigger the problem.
I only have a 32-bit CentOS 5 VM. My bare-metal Debian stretch machine is 64 bits, so I wasn't able to test the CentOS 5 build on Debian. If I take the output from the 32-bit CentOS 5 build on a 32-bit Ubuntu 16 VM, I can reproduce the problem. I'm currently building the same git revision on Ubuntu 16. I suspect that I won't see the problem with that combo. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
