openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <dam...@apache.org>
Subject Re: Buildbots are working again
Date Wed, 04 Jan 2017 12:27:48 GMT
Yes, the last problem was that main/curl needed adding to
RepositoryExternal.mk. I've committed a fix and am testing it on the
FreeBSD bot now.

The bots will be quite unstable going forward, as I am actively porting
modules to gbuild. They help me a lot to test different platforms quickly,
with different build settings - my PC mostly uses system libraries, the
bots internal ones. If you don't see commits to SVN for a while, and the
bots are still broken, then there's a problem ;-).

Damjan



On Wed, Jan 4, 2017 at 2:16 PM, Matthias Seidel <matthias.seidel@hamburg.de>
wrote:

> Hi Damjan,
>
> Last night the linux64-41x buildbot (and maybe others)  failed. Last
> successful build was 31.12.2016.
>
> Do you have any idea?
>
> Regards, Matthias
>
>
> Am 26.12.2016 um 19:45 schrieb Damjan Jovanovic:
> > Hi
> >
> > All the buildbots are successfully building now.
> >
> > The FreeBSD bot was fixed by changing the buildbot script to use Clang
> > instead of GCC. From what I've seen, on FreeBSD, loading a mixture of C++
> > libraries built with GCC and C++ libraries built with Clang into the same
> > process, and using more advanced C++ features like exception handling,
> > causes memory corruption and crashes due to incompatible C++ ABIs; either
> > every library has to be built with GCC or every library has to be built
> > with Clang. In practice, the former requires a rebuild of the entire base
> > system and building all ports from source, which is why the latter is
> > better.
> >
> > The Linux bots were much harder to fix. The build was breaking because
> libc
> > isn't linked to in some gbuild modules, something that was fixed by
> > explicitly always linking to libc on Linux, and because Google Test
> wasn't
> > linking to libpthread, somehow resulting in missing symbols in at least
> > main/binaryurp when built without --enable-dbgutil, which was fixed by
> > explicitly linking it to libpthread. I don't like these linker mysteries,
> > which never happen on FreeBSD, and some of which can be worked around
> with
> > the "gold" linker...
> >
> > Damjan
> >
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message