Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
On 24 Aug, Pedro Lino wrote: > >> On 08/24/2020 3:18 PM Don Lewis wrote: > >> Is this a parallel build? Has the offuh module been built and >> delivered? Seems oa little dd that offuh is not listed as a dependency >> in sax/prj/build.lst, but it is listed as a dependency of cppuhelper and >> cppuhelper is listed as a dependency of sax. >> >> When offuh is delivered, it should put a copy of UnicodeType.hpp here: >> solver/*/unxlngx6.pro/inc/offuh/com/sun/star/i18n/UnicodeType.hpp > > I build using all cores (in this case 8). This was never a problem with 42X. > > There was no offuh module... If offuh was not built and delivered then that will break sax for sure. With the latest set of cherry-picks, I'm seeing these modules fail: beanshell hsqldb saxon apache-commons rhino lucene ridljar jvmfwk which are most/all java, I think. i haven't run into the libgcc_s.so.1 issue. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
On 24 Aug, Don Lewis wrote: > On 24 Aug, Pedro Lino wrote: >> Hi Don, all >> >>> On 08/24/2020 3:18 PM Don Lewis 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::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 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? > > basebmp fails due to a bug that I patched in trunk and AOO42X a while > back, when clang on FreeBSD found it. I guess that the version of gcc > in Ubuntu 18 doesn't like it either. It's one of the bug fixes that I > plan to cherry-pick for AOO418 tonight. I justt did that, but there is another change that I need to cherry-pick for the patch to bundled boost before we are ready for the -std=gnu++98 fix for Linux. The ancient version of boost that we bundle doesn't really understand the features of modern gcc. I can get away with the -std=gnu++98 setting the FreeBSD port of 4.1.7 because it uses system boost, which is more modern. I need to do some more testing before I'm ready for this. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] DonLewisFreeBSD merged pull request #93: Force Linux builds to use gnu++98 (C++98 + GNU extensions) mode to be
DonLewisFreeBSD merged pull request #93: URL: https://github.com/apache/openoffice/pull/93 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
On 24 Aug, Pedro Lino wrote: > Hi Don, all > >> On 08/24/2020 3:18 PM Don Lewis 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::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 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? basebmp fails due to a bug that I patched in trunk and AOO42X a while back, when clang on FreeBSD found it. I guess that the version of gcc in Ubuntu 18 doesn't like it either. It's one of the bug fixes that I plan to cherry-pick for AOO418 tonight. What version of OpenJDK are you using? I'm seeing a fair amount of fallout from OpenJDK 11. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.1.8 on the 20th Anniversary? (was Re: 4.2.0 on the 20th Anniversary?)
Hi Jim > On 08/18/2020 12:09 PM Jim Jagielski wrote: > > > Should we think of doing a 4.1.8 beta? Can you please provide some Linux builds (Beta or not) to test the recent improvements? Unfortunately I can not compile branch 418 under Ubuntu 18.04 x64 Thanks! Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: installing git on centos 5.5
On 24 Aug, Carl Marcum wrote: > Hi Don, > > On 8/23/20 2:58 PM, Don Lewis wrote: >> On 23 Aug, Carl Marcum wrote: >>> I'm setting up a new CentOS 5.5 VM that I can build 4.1.x series on. >>> >>> First hurdle was figuring out out how to point to the vault.centos.org >>> archived rpms. >>> Unfortunately no git was available then. >>> >>> Was this done for the build servers or has anyone else done this and how >>> did you do it? >> You may have to download the source and build it yourself. > > That's what I'll try next. > Any idea if I can build the latest version or need to back up somewhat? One problem you might run into is that the version of openssl might be too old to connect to github. You might need to install a newer version in /usr/local. You might also need to install a newer version of ssh and/or curl to link to that as well. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
Hi Don > On 08/24/2020 4:58 PM Don Lewis wrote: > The actual error should show up as "error: " in the build output. The error messages and compiling stop at a completely different step on each run even if I do a dmake clean and repeat the exact same 3 steps. Adding --enable-verbose did not make messages clearer Thank you for your patience and assistance but this seems like a random task and I have no idea what I'm doing :( Thank you anyway! Best, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
On 24 Aug, Pedro Lino wrote: > Hi Don, all > >> On 08/24/2020 3:18 PM Don Lewis 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::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 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? You might want to configure with --enable-verbose so that you can see the compiler command line as each file is compiled. That will show all the options passed to the compiler. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
On 24 Aug, Pedro Lino wrote: > Hi Don, all > >> On 08/24/2020 3:18 PM Don Lewis 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::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 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::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
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
Hi Don, all > On 08/24/2020 3:18 PM Don Lewis 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::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 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? Thanks! Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
> On 08/24/2020 3:18 PM Don Lewis wrote: > Is this a parallel build? Has the offuh module been built and > delivered? Seems oa little dd that offuh is not listed as a dependency > in sax/prj/build.lst, but it is listed as a dependency of cppuhelper and > cppuhelper is listed as a dependency of sax. > > When offuh is delivered, it should put a copy of UnicodeType.hpp here: > solver/*/unxlngx6.pro/inc/offuh/com/sun/star/i18n/UnicodeType.hpp I build using all cores (in this case 8). This was never a problem with 42X. There was no offuh module... I'm now compiling 418 on a single thread... Thanks! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO418 cherry picks
Hi Don, Am 24.08.20 um 04:04 schrieb Don Lewis: > I've got a bunch of cherry picks that I'm planning to merge into AOO418. > There are two categories: > * Fixes from the FreeBSD port that have been upstreamed to the trunk > and AOO42X branches, but I'm still carrying around in the FreeBSD > port of 4.1.7. > > * Updates of a bunch of the bundled dependencies. These have been > updated in AOO42X and trunk for a while, but haven't been merged to > AOO418. The FreeBSD port mostly usees the system versions of these. > > I'd like to revisit: > > commit 7a3beb322b74df1b6c96e03605837df34781c68f > Author: Matthias Seidel > Date: Thu Oct 11 16:53:51 2018 + > > Rollback to Rev. 1843088 due to build errors. > > git-svn-id: > https://svn.apache.org/repos/asf/openoffice/branches/AOO416@18438571 > 13f79535-47bb-0310-9956-ffa450edef68 > > I'm still using the patch for the FreeBSD port. Without it, a build > with --enable-odk will fail with Java 8 or newer. I don't see how it > would break the build since the changes are just to structured comments > that are parsed to generate the documentation in the ODK. When this was > backed out, I thought the reason was that building with a newer version > of the JDK would prevent runtime detection of older versions of the JDK. > So far asa I know, that's not a problem with AOO42X and trunk, which > have the changes. No, it was backed out because it broke the build. But I am not sure if it was the patch itself or the way it was committed. I think there were several fixes committed at once... However, at that time a build that was compiled with Java 8 could not see an installed Java 7 (at least on Windows). Meanwhile Damjan has changed the Java detection (for AdpoptOpenJDK) so we might try it again. Regards, Matthias > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
On 24 Aug, Pedro Lino wrote: > Ciao Rigo > >> > /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid >> > ELF header >> > > > Now it stopped at expat, but the issue was the same: libgcc_s.so.1: invalid > ELF header > >> > I'm wondering why there is a copy of libgcc_s.so.1 here. That should be >> > a system library. >> >> I also bumped into this very strange error. >> >> The file was indeed not an ELF, but it contained a number (like "42") >> or something like that. I cannot remember exactly. > > If the file contained 42 that would be correct because 42 is the answer to > everything! ;) > > https://duckduckgo.com/?q=the+answer+to+life+the+universe+everything > >> If I recall correctly, deleting that spurious file was enough to let >> the build proceed further. >> >> Once the build succeeded, I was not able to reproduce the problem any >> more, therefore I did not report it. >> >> I hope this helps, > > Yes, it did help to move one step further! Thank you for the suggestion! > > Now it fails at > > = > Building module sax > = > > Entering /source/openoffice/main/sax/source/tools > > mkout -- version: 1.8 > Making:all_sax.dpslo > Compiling: sax/unxlngx6.pro/misc/sax_version.c > Compiling: sax/source/tools/converter.cxx > /source/openoffice/main/sax/source/tools/converter.cxx:25:10: fatal error: > com/sun/star/i18n/UnicodeType.hpp: No such file or directory > #include > ^~~ > compilation terminated. > dmake: Error code 1, while making '../../unxlngx6.pro/slo/converter.obj' > > Any ideas? Is this a parallel build? Has the offuh module been built and delivered? Seems oa little dd that offuh is not listed as a dependency in sax/prj/build.lst, but it is listed as a dependency of cppuhelper and cppuhelper is listed as a dependency of sax. When offuh is delivered, it should put a copy of UnicodeType.hpp here: solver/*/unxlngx6.pro/inc/offuh/com/sun/star/i18n/UnicodeType.hpp - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
Ciao Rigo > > /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid > > ELF header > > Now it stopped at expat, but the issue was the same: libgcc_s.so.1: invalid ELF header > > I'm wondering why there is a copy of libgcc_s.so.1 here. That should be > > a system library. > > I also bumped into this very strange error. > > The file was indeed not an ELF, but it contained a number (like "42") > or something like that. I cannot remember exactly. If the file contained 42 that would be correct because 42 is the answer to everything! ;) https://duckduckgo.com/?q=the+answer+to+life+the+universe+everything > If I recall correctly, deleting that spurious file was enough to let > the build proceed further. > > Once the build succeeded, I was not able to reproduce the problem any > more, therefore I did not report it. > > I hope this helps, Yes, it did help to move one step further! Thank you for the suggestion! Now it fails at = Building module sax = Entering /source/openoffice/main/sax/source/tools mkout -- version: 1.8 Making:all_sax.dpslo Compiling: sax/unxlngx6.pro/misc/sax_version.c Compiling: sax/source/tools/converter.cxx /source/openoffice/main/sax/source/tools/converter.cxx:25:10: fatal error: com/sun/star/i18n/UnicodeType.hpp: No such file or directory #include ^~~ compilation terminated. dmake: Error code 1, while making '../../unxlngx6.pro/slo/converter.obj' Any ideas? Thanks! Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Spurious file libgcc_s.so.1 during Linux build [Was: OpenSSL versions]
Hello All, On Fri, Aug 21, 2020 at 12:13:49PM -0700, Don Lewis wrote: > On 21 Aug, Pedro Lino wrote: > > Hi Don > > > >> Hmn, I don't know about the extras failure, but all of the other errors > >> are failures to build various third party packages that we bundle. This > >> should be independent of the CXXFLAGS issue. More of the output of > >> build --from python > >> might be informative. > > > > Did a Dmake clean and the problem now starts on icu so here is the output > > below > > > > ### > > > > build --from icu > > build -- version: 275224 [...] > > LD_LIBRARY_PATH=../lib:../stubdata:../tools/ctestfw:$LD_LIBRARY_PATH > > ../bin/icupkg -d ./out/build/icudt40l --list -x \* ./in/icudt40l.dat > > > out/tmp/icudata.lst > > ../bin/icupkg: error while loading shared libraries: > > /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid > > ELF header > > Makefile:350: recipe for target 'out/tmp/icudata.lst' failed > > make[1]: *** [out/tmp/icudata.lst] Error 127 > > make[1]: Leaving directory > > '/source/openoffice/main/icu/unxlngx6.pro/misc/build/icu/source/data' > > Makefile:103: recipe for target 'all-recursive' failed > > make: *** [all-recursive] Error 2 > > dmake: Error code 2, while making > > './unxlngx6.pro/misc/build/so_built_so_icu' [...] > /source/openoffice/main/solver/418/unxlngx6.pro/lib/libgcc_s.so.1: invalid > ELF header > > I'm wondering why there is a copy of libgcc_s.so.1 here. That should be > a system library. I also bumped into this very strange error. The file was indeed not an ELF, but it contained a number (like "42") or something like that. I cannot remember exactly. If I recall correctly, deleting that spurious file was enough to let the build proceed further. Once the build succeeded, I was not able to reproduce the problem any more, therefore I did not report it. I hope this helps, -- rigo http://rigo.altervista.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO418 cherry picks
On 24 Aug, Pedro Lino wrote: > Hi Don, all > > I'm still trying to compile 418 on Ubuntu 18.04 x64 > I updated the 418 code but I get stuck at module graphite with the following > error (log file at https://etherpad.wikimedia.org/p/config.log) > > Any ideas? The error is happening during the configure step for graphite. The config.log mentioned is this one: main/graphite/unxlngx6.pro/misc/build/silgraphite-2.3.1/engine/config.log I don't believe I've run across any problems here. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: installing git on centos 5.5
On 24 Aug, Carl Marcum wrote: > Hi Don, > > On 8/23/20 2:58 PM, Don Lewis wrote: >> On 23 Aug, Carl Marcum wrote: >>> I'm setting up a new CentOS 5.5 VM that I can build 4.1.x series on. >>> >>> First hurdle was figuring out out how to point to the vault.centos.org >>> archived rpms. >>> Unfortunately no git was available then. >>> >>> Was this done for the build servers or has anyone else done this and how >>> did you do it? >> You may have to download the source and build it yourself. > > That's what I'll try next. > Any idea if I can build the latest version or need to back up somewhat? No idea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO418 cherry picks
Hi Don, all I'm still trying to compile 418 on Ubuntu 18.04 x64 I updated the 418 code but I get stuck at module graphite with the following error (log file at https://etherpad.wikimedia.org/p/config.log) Any ideas? Thanks! configure: error: C compiler cannot create executables See `config.log' for more details. dmake: Error code 77, while making './unxlngx6.pro/misc/build/so_configured_so_graphite' 1 module(s): graphite need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /source/openoffice/main/graphite When you have fixed the errors in that module you can resume the build by running: build --from graphite > On 08/24/2020 3:04 AM Don Lewis wrote: > > > I've got a bunch of cherry picks that I'm planning to merge into AOO418. > There are two categories: > * Fixes from the FreeBSD port that have been upstreamed to the trunk > and AOO42X branches, but I'm still carrying around in the FreeBSD > port of 4.1.7. > > * Updates of a bunch of the bundled dependencies. These have been > updated in AOO42X and trunk for a while, but haven't been merged to > AOO418. The FreeBSD port mostly usees the system versions of these. > > I'd like to revisit: > > commit 7a3beb322b74df1b6c96e03605837df34781c68f > Author: Matthias Seidel > Date: Thu Oct 11 16:53:51 2018 + > > Rollback to Rev. 1843088 due to build errors. > > git-svn-id: > https://svn.apache.org/repos/asf/openoffice/branches/AOO416@18438571 > 13f79535-47bb-0310-9956-ffa450edef68 > > I'm still using the patch for the FreeBSD port. Without it, a build > with --enable-odk will fail with Java 8 or newer. I don't see how it > would break the build since the changes are just to structured comments > that are parsed to generate the documentation in the ODK. When this was > backed out, I thought the reason was that building with a newer version > of the JDK would prevent runtime detection of older versions of the JDK. > So far asa I know, that's not a problem with AOO42X and trunk, which > have the changes. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: installing git on centos 5.5
Hi Don, On 8/23/20 2:58 PM, Don Lewis wrote: On 23 Aug, Carl Marcum wrote: I'm setting up a new CentOS 5.5 VM that I can build 4.1.x series on. First hurdle was figuring out out how to point to the vault.centos.org archived rpms. Unfortunately no git was available then. Was this done for the build servers or has anyone else done this and how did you do it? You may have to download the source and build it yourself. That's what I'll try next. Any idea if I can build the latest version or need to back up somewhat? Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
