On 19 Mar, Jim Jagielski wrote: > Yeah, I see that now... Before my commits, the macOS builds > broke mid-stream, due to the rdbmaker stuff, et.al... as could > be seen, there was places where macOS was using/expecting > gcc3 and others where it was s5abi. 4.1.5 seemed to use > s5abi universally, but so the issue was/is gcc3 slipping in > somewhere. > > We do have bridges/source/cpp_uno/gcc3_macosx_intel
That's a 32-bit build.
