On 24 Aug, Pedro Lino wrote: > Hi Don, all > >> On 08/24/2020 3:18 PM Don Lewis <truck...@apache.org> wrote: > >> Is this a parallel build? > > Switched to single thread building > > build --all > > when it stopped I followed the suggestion by Rigo and deleted > /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1 > > and restarted with build --all:icu > > Now it stopped again at > > In file included from > /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/shared_array.hpp:17:0, > from ../inc/basebmp/bitmapdevice.hxx:32, > from > /source/openoffice/main/basebmp/source/bitmapdevice.cxx:28: > /source/openoffice/main/solver/418/unxlngx6.pro/inc/boost/smart_ptr/shared_array.hpp:177:37: > warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D) [with Y > = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’ will > change in C++17 because the exception specification is part of a function > type [-Wnoexcept-type] > template<class Y, class D> void reset( Y * p, D d ) > ^~~~~ > dmake: Error code 1, while making '../unxlngx6.pro/slo/bitmapdevice.obj' > > 1 module(s): > basebmp > need(s) to be rebuilt > > Reason(s): > > ERROR: error 65280 occurred while making > /source/openoffice/main/basebmp/source > > When you have fixed the errors in that module you can resume the build by > running: > > build --all:basebmp > > Ideas?
This looks like just a warning: 77:37: warning: mangled name for ‘void boost::shared_array<T>::reset(Y*, D) [with Y = unsigned char; D = void (*)(void*) throw (); T = unsigned char]’ will change in C++17 and from the warning it looks like the -std=gnu++98 fix isn't taking effect. basebmp hasn't been converted to gbuild in AOO418, so the fix should be in solenv/inc/unxlng.mk. The actual error should show up as "error: " in the build output. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
