Re: Request for PR reviews
Thank you Dave for the clarification. Dylan On Tue, Feb 23, 2021 at 9:28 PM Dave Fisher wrote: > > > > On Feb 23, 2021, at 9:18 PM, Dylan Pham wrote: > > > > Hello, > > > > I think the wording on the Buildbot info page should be changed from > > "slaves" to something like "worker" or something like that in order to be > > culturally sensitive in this day and age. > > We will have to see if we can get this changed. It’s a Foundation resource > that uses other’s software. Please be patient and don’t take lack of change > as this project not being sensitive. Please keep in mind that we are > volunteers her. > > You should notice that OpenOffice is using “main” and “trunk” for the > default branch in our Git Repositories. We’ve made sure not to use “master”. > > Regards, > Dave > > > > > https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info > > > > > > my 2c, > > Dylan > > > > On Mon, Feb 22, 2021 at 10:39 AM Matthias Seidel < > matthias.sei...@hamburg.de> > > wrote: > > > >> Hi Arrigo, > >> > >> Am 22.02.21 um 19:28 schrieb Arrigo Marchiori: > >>> Hello Matthias, > >>> > >>> On Mon, Feb 22, 2021 at 06:24:07PM +0100, Matthias Seidel wrote: > >>> > >>>> Hi Arrigo, > >>>> > >>>> Am 21.02.21 um 16:01 schrieb Arrigo Marchiori: > >>>>> Dear All, > >>>>> > >>>>> please help me review and finalize PR 122: > >>>>> https://github.com/apache/openoffice/pull/122 > >>>>> as it should fix a top-priority AOO bug, and hopefully help us spot > >>>>> other similar problems in the future. > >>>>> > >>>>> Moreover, I would really like to merge PR 111: > >>>>> https://github.com/apache/openoffice/pull/111 > >>>>> because I do work on openSUSE and I cannot build AOO without it. I > >>>>> dare proposing it as a "Good Thing" for me, and a "Mostly Harmless" > >>>>> change for anyone else. FWIW I could build 4.1.9 for Linux on the > >>>>> CentOS 5 version in both 32-bit and 64-bit versions with that commit > >>>>> included. > >>>>> > >>>>> I'll be more than happy to answer anybody's concerns over both PR's > >>>>> either on GitHub, or on this list. > >>>> Yes, I am a bit puzzled that PRs are so neglected. > >>>> They are a great tool and can really speed up things. > >>>> > >>>> I have merged some of your PRs, but only those I could build and test > >>>> against the (fixed) problem. > >>> That's very kind of you. And I did receive some comments from other > >>> people as well, that I appreciate. > >>> > >>> But can we establish a sort of ``emergency exit'' in the > >>> "commit-then-review" process, like ``if no-one comments a PR it could > >>> be merged in X time''? A sort of lazy consensus? > >> I am not sure, since I really can't evaluate the quality of the code > >> (old and new one). > >>> > >>> Personally, I would really like to see the development branches go > >>> "live" with nightly builds. I see lots of people available to report > >>> bugs and test fixes, and I cannot submit anything to them for testing, > >>> mostly because I cannot build Windows releases! > >> > >> Regarding Windows builds: > >> > >> We have nightly builds of trunk and weekly builds for AOO42X: > >> > >> https://www.openoffice.org/download/devbuilds.html > >> > >> And you can always find my personal Test Builds here: > >> > >> https://home.apache.org/~mseidel/AOO-builds/ > >> > >> If you are interested in building for Windows, I would be happy to help > >> you with it. > >> After all these years, I am still the only one that does release builds > >> for Windows and is able to sign them. Just for redundancy it would be > >> great to have a second person available. > >> > >> Regards, > >> > >> Matthias > >> > >>> > >>> Thank you and best regards, > >> > >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Request for PR reviews
Hello, I think the wording on the Buildbot info page should be changed from "slaves" to something like "worker" or something like that in order to be culturally sensitive in this day and age. https://cwiki.apache.org/confluence/display/OOOUSERS/Buildbot+info my 2c, Dylan On Mon, Feb 22, 2021 at 10:39 AM Matthias Seidel wrote: > Hi Arrigo, > > Am 22.02.21 um 19:28 schrieb Arrigo Marchiori: > > Hello Matthias, > > > > On Mon, Feb 22, 2021 at 06:24:07PM +0100, Matthias Seidel wrote: > > > >> Hi Arrigo, > >> > >> Am 21.02.21 um 16:01 schrieb Arrigo Marchiori: > >>> Dear All, > >>> > >>> please help me review and finalize PR 122: > >>> https://github.com/apache/openoffice/pull/122 > >>> as it should fix a top-priority AOO bug, and hopefully help us spot > >>> other similar problems in the future. > >>> > >>> Moreover, I would really like to merge PR 111: > >>> https://github.com/apache/openoffice/pull/111 > >>> because I do work on openSUSE and I cannot build AOO without it. I > >>> dare proposing it as a "Good Thing" for me, and a "Mostly Harmless" > >>> change for anyone else. FWIW I could build 4.1.9 for Linux on the > >>> CentOS 5 version in both 32-bit and 64-bit versions with that commit > >>> included. > >>> > >>> I'll be more than happy to answer anybody's concerns over both PR's > >>> either on GitHub, or on this list. > >> Yes, I am a bit puzzled that PRs are so neglected. > >> They are a great tool and can really speed up things. > >> > >> I have merged some of your PRs, but only those I could build and test > >> against the (fixed) problem. > > That's very kind of you. And I did receive some comments from other > > people as well, that I appreciate. > > > > But can we establish a sort of ``emergency exit'' in the > > "commit-then-review" process, like ``if no-one comments a PR it could > > be merged in X time''? A sort of lazy consensus? > I am not sure, since I really can't evaluate the quality of the code > (old and new one). > > > > Personally, I would really like to see the development branches go > > "live" with nightly builds. I see lots of people available to report > > bugs and test fixes, and I cannot submit anything to them for testing, > > mostly because I cannot build Windows releases! > > Regarding Windows builds: > > We have nightly builds of trunk and weekly builds for AOO42X: > > https://www.openoffice.org/download/devbuilds.html > > And you can always find my personal Test Builds here: > > https://home.apache.org/~mseidel/AOO-builds/ > > If you are interested in building for Windows, I would be happy to help > you with it. > After all these years, I am still the only one that does release builds > for Windows and is able to sign them. Just for redundancy it would be > great to have a second person available. > > Regards, > >Matthias > > > > > Thank you and best regards, > >
macOS Silver Sparrow security issue
Hello, Just wanted to pass this along to mac users. Check your mac per the article below: https://redcanary.com/blog/clipping-silver-sparrows-wings/ Dylan
Re: Failing downloads during bootstrap [Was Re: Java 8 and Ant 1.10]
Hi Rigo, Thanks for sharing. I looked at the downloading external dependencies perl script and seems like it uses the LWP::UserAgent perl module and I think I need to reinstall it. Also the Archive::Zip perl module is giving me grief as well. I'm trying on different OS X platforms to see which will work. I may end up trying the reference platform mentioned on the build page to see if it can help in my case. Dylan On Thu, Feb 18, 2021 at 4:32 AM Arrigo Marchiori wrote: > Hello Dylan, > > On Tue, Feb 16, 2021 at 06:35:34PM -0800, Dylan Pham wrote: > > > Has anyone experienced issue with the build script downloading external > > files to ext_sources with ./bootstrap? It's throwing me a 500 Can't > > connect...error but I can manually download the file just fine. This > didn't > > happen before... > > I think I saw it happening once or twice, and another person reported > a similar problem some weeks ago. > > But for me it was non-reproducible, so... very very hard to > troubleshoot. > > If you have problems with a certain download, please share its link > here so we can check it from different parts of the world: it may be a > problem related to local mirrors. > > I hope this helps. > > Best regards, > -- > Arrigo > > http://rigo.altervista.org > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Java 8 and Ant 1.10
Has anyone experienced issue with the build script downloading external files to ext_sources with ./bootstrap? It's throwing me a 500 Can't connect...error but I can manually download the file just fine. This didn't happen before... On Thu, Feb 11, 2021 at 10:28 PM Mechtilde wrote: > Hello, > > > Am 12.02.21 um 01:08 schrieb Carl Marcum: > > Hi Jim, > > > > On 2/11/21 7:30 AM, Jim Jagielski wrote: > >> Carl, on what platform? TIA. > > > > CentOS 7. > > and I tested Debian 10 > > > >> > >>> On Feb 11, 2021, at 6:26 AM, Carl Marcum wrote: > >>> > >>> On 2/9/21 6:39 PM, Carl Marcum wrote: > On 2/8/21 8:54 PM, Carl Marcum wrote: > > On 2/8/21 7:15 PM, Carl Marcum wrote: > >> Hi Jim, > >> > >> On 2/8/21 12:51 PM, Jim Jagielski wrote: > >>> Anyone tried building HEAD of AOO42X w/ Java8 (or later) and > >>> Apache Ant 1.10? > >>> > >>> > - > >>> > >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> > >> Normally I build 4.1 and trunk on the same VM's and use JDK 8 and > >> Ant 1.9. > >> > >> I've kicked off a build of trunk with Ant 1.10.15 and JDK 15.0.2. > >> My trunk is not completely up to date but it's withing a few weeks. > >> configure complained about JAVA_HOME even though I have it set so > >> I added the --with-jdk-home flag. > >> > >> I'll let you know how it goes. > >> > >> If trunk won't answer your question I can try and up to date 4.2 > >> tomorrow. > >> > >> Best regards, > >> Carl > > No luck, > > > > 7 module(s): > > beanshell > > hsqldb > > apache-commons > > rhino > > saxon > > lucene > > javaunohelper > > need(s) to be rebuilt > > > > I'll try with an updated 4.2 branch tomorrow. > > > > Best regards, > > Carl > > > Building with an up to date AOO42X branch and > Ant 1.10.15 and JDK 15.0.2. turned out with similar results. > > 9 module(s): > beanshell > hsqldb > apache-commons > rhino > saxon > lucene > qadevOOo > bean > odk > need(s) to be rebuilt > > I'll test backing down Ant next. > > regards, > Carl > > >>> So far I've been able to build 4.2 with Ant 1.10.8 and JDK 8 but not > >>> 11 or 15. > >>> > >>> Best regards, > >>> Carl > > -- > Mechtilde Stehmann > ## Apache OpenOffice > ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 > ## Debian Developer > ## PGP encryption welcome > ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F > >
Re: Java 8 and Ant 1.10
My mistake, I was building trunk instead of AOO42X... On Tue, Feb 9, 2021 at 11:44 PM Dylan Pham wrote: > this is encouraging. the end of the tunnel is sorta in sight. attempting > to figure out what ails these modules. > > ** > ERROR: ERROR: Missing files > in function: remove_Files_Without_Sourcedirectory > ** > in function: remove_Files_Without_Sourcedirectorystopping log at Tue Feb > 9 22:56:51 2021 > dmake: Error code 255, while making 'openoffice_en-US.dmg' > > ERROR: next directories could not be built: > /Users/aoobuild/Documents/openoffice/main/openssl > /Users/aoobuild/Documents/openoffice/main/oox/prj > /Users/aoobuild/Documents/openoffice/ext_libraries/serf > /Users/aoobuild/Documents/openoffice/main/ucb/prj > /Users/aoobuild/Documents/openoffice/main/writerfilter/prj > /Users/aoobuild/Documents/openoffice/main/sc/prj > /Users/aoobuild/Documents/openoffice/main/scripting/java > /Users/aoobuild/Documents/openoffice/main/postprocess/packcomponents > /Users/aoobuild/Documents/openoffice/main/instsetoo_native/util > > ERROR: please check these directories and build the corresponding > module(s) anew!! > > > On Tue, Feb 9, 2021 at 11:39 AM Dylan Pham wrote: > >> Building on OS X 10.10.5 with configurations below: >> $ ant >> Buildfile: build.xml does not exist! >> Build failed >> $ ant -version >> Apache Ant(TM) version 1.10.9 compiled on September 27 2020 >> $ javac -version >> javac 1.8.0_282 >> $ git branch >> * AOO42X >> trunk >> >> Got build error as below regarding autodoc (Ghostscript related?) Full >> config.log file attached. Anyone else ran into this issue? Maybe a >> gbuild issue? >> /Users/aoobuild/Documents/openoffice/main/autodoc/source/inc/estack.hxx:31:10: >> fatal error: 'slist' file not found >> #include >> ^ >> 1 warning and 1 error generated. >> dmake: Error code 2, while making 'all' >> >> 1 module(s): >> autodoc >> need(s) to be rebuilt >> >> On Mon, Feb 8, 2021 at 1:23 PM Dylan Pham wrote: >> >>> Hi Jim, >>> Should we try building this for 32-bit or 64-bit? >>> >>> On Mon, Feb 8, 2021 at 9:52 AM Jim Jagielski wrote: >>> >>>> Anyone tried building HEAD of AOO42X w/ Java8 (or later) and >>>> Apache Ant 1.10? >>>> >>>> - >>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>> >>>>
Re: Java 8 and Ant 1.10
this is encouraging. the end of the tunnel is sorta in sight. attempting to figure out what ails these modules. ** ERROR: ERROR: Missing files in function: remove_Files_Without_Sourcedirectory ** in function: remove_Files_Without_Sourcedirectorystopping log at Tue Feb 9 22:56:51 2021 dmake: Error code 255, while making 'openoffice_en-US.dmg' ERROR: next directories could not be built: /Users/aoobuild/Documents/openoffice/main/openssl /Users/aoobuild/Documents/openoffice/main/oox/prj /Users/aoobuild/Documents/openoffice/ext_libraries/serf /Users/aoobuild/Documents/openoffice/main/ucb/prj /Users/aoobuild/Documents/openoffice/main/writerfilter/prj /Users/aoobuild/Documents/openoffice/main/sc/prj /Users/aoobuild/Documents/openoffice/main/scripting/java /Users/aoobuild/Documents/openoffice/main/postprocess/packcomponents /Users/aoobuild/Documents/openoffice/main/instsetoo_native/util ERROR: please check these directories and build the corresponding module(s) anew!! On Tue, Feb 9, 2021 at 11:39 AM Dylan Pham wrote: > Building on OS X 10.10.5 with configurations below: > $ ant > Buildfile: build.xml does not exist! > Build failed > $ ant -version > Apache Ant(TM) version 1.10.9 compiled on September 27 2020 > $ javac -version > javac 1.8.0_282 > $ git branch > * AOO42X > trunk > > Got build error as below regarding autodoc (Ghostscript related?) Full > config.log file attached. Anyone else ran into this issue? Maybe a > gbuild issue? > /Users/aoobuild/Documents/openoffice/main/autodoc/source/inc/estack.hxx:31:10: > fatal error: 'slist' file not found > #include > ^ > 1 warning and 1 error generated. > dmake: Error code 2, while making 'all' > > 1 module(s): > autodoc > need(s) to be rebuilt > > On Mon, Feb 8, 2021 at 1:23 PM Dylan Pham wrote: > >> Hi Jim, >> Should we try building this for 32-bit or 64-bit? >> >> On Mon, Feb 8, 2021 at 9:52 AM Jim Jagielski wrote: >> >>> Anyone tried building HEAD of AOO42X w/ Java8 (or later) and >>> Apache Ant 1.10? >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>>
Re: Java 8 and Ant 1.10
Building on OS X 10.10.5 with configurations below: $ ant Buildfile: build.xml does not exist! Build failed $ ant -version Apache Ant(TM) version 1.10.9 compiled on September 27 2020 $ javac -version javac 1.8.0_282 $ git branch * AOO42X trunk Got build error as below regarding autodoc (Ghostscript related?) Full config.log file attached. Anyone else ran into this issue? Maybe a gbuild issue? /Users/aoobuild/Documents/openoffice/main/autodoc/source/inc/estack.hxx:31:10: fatal error: 'slist' file not found #include ^ 1 warning and 1 error generated. dmake: Error code 2, while making 'all' 1 module(s): autodoc need(s) to be rebuilt On Mon, Feb 8, 2021 at 1:23 PM Dylan Pham wrote: > Hi Jim, > Should we try building this for 32-bit or 64-bit? > > On Mon, Feb 8, 2021 at 9:52 AM Jim Jagielski wrote: > >> Anyone tried building HEAD of AOO42X w/ Java8 (or later) and >> Apache Ant 1.10? >> >> - >> 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: Java 8 and Ant 1.10
Hi Jim, Should we try building this for 32-bit or 64-bit? On Mon, Feb 8, 2021 at 9:52 AM Jim Jagielski wrote: > Anyone tried building HEAD of AOO42X w/ Java8 (or later) and > Apache Ant 1.10? > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: [Discussion] Would we enable volunteers that develop extensions
>From a legal perspective I think it's best to leave the extensions by themselves. It's like having a parent company and many subsidiaries. If something happens, a particular subsidiary can be cut off without too much damage to the parent company. >From the build/code maintenance perspective, it keeps the main code base easier to maintain and build. Imagine the thousands more dependencies for the thousand more extensions that are popular with users. And the extension authors can do whatever they want with their product. If another person thinks they have a better idea for a better extension then both can compete among users, without the perceived endorsement of the main AOO. Dylan On Fri, Feb 5, 2021 at 12:53 PM Steve Lubbs wrote: > Just a thought. > > As part of an effort to enable volunteer extension authors would it make > sense to selectively approve extension functionality for inclusion into > AOO on a case by case basis? If it provides a level of new functionality > that is considered important and compelling, say something that is on > the wish list and that no one has the time to pursue? For instance a PDF > importer that was mentioned earlier. > > With the author's permission and effort the extension could be ported to > be core code rather than an extension. The author, upon agreeing to > these conditions could be given the right of first refusal to be the > maintainer of the code. There should also be a proviso that the author > will to do the port. > > This, or some permutation, could be one way to reward extension authors > for their efforts, provide incentive, and provide new supported > functionality within the constraints of limited resources. > > It goes without saying that this would need to be carefully managed and > some way to vet the new code would be needed. > > Like I said, just a thought. > > Steve > > On 2/1/21 5:06 PM, Carl Marcum wrote: > > Hi Peter, > > > > On 2/1/21 1:46 AM, Peter Kovacs wrote: > >> I have a question. How much willing are we to support extensions. > > I think for extensions like report builder where the code is donated > > and it's a high-profile extension it makes sense. > > Much more so if we build and bundle during a release. > > > > Freedom to do releases is another issue. If they're AOO sub-projects > > we need to do the releases the same way as the Office and that can be > > cumbersome for something as small as an extension when they are done > > independently and frequently and most members may not have the > > toolchains setup. > > > > I ran into this with things like the NetBeans plugin and some other > > developer tools. > > > > I think for the same reason ASF wants a minimum number of developers > > for a project, a lot of extensions are probably one or two developers > > and we could end up with a lot of abandoned code. > > > >> > >> I mean we have here a voice recognition questions, there is the > >> reporting tool or wiki extension. > >> > >> We already thinking on creating repos for reporting tool or the wiki > >> extensions. > >> > >> But how do we deal with those topics on the organisatorical level? > >> > >> Do we form I do not know how to name them, task force around them? Do > >> the people who whish to be delevop these functions do this in an > >> outside project (independant if this is a Apache project or github > >> self sufficient hosted) > >> > >> > >> I would opt that we agree on some form to enable volunteer to use the > >> project infrastructure and provide them with a stronger feeling that > >> they are part of the project even if they are only working on an > >> extension of none core features. > > > > For most extensions I don't think this is necessary when they have > > GitHub, Sourceforge, etc. > > > >> > >> This makes it easier to bring the community together. I mean the > >> wording 3rd parties bring a lot of discussion and the need to explain > >> things, to the table. > > > > I think there are things we can do as a project to support a community > > which we need to grow. > > Some of which like forums and mailing lists we already do. > > Extension developers are welcome on the dev@ list. > > > > There is an api@ list for that purpose but I thought it was shut down > > for lack of traffic and I didn't subscribe anymore but I see there are > > a few recent posts within the last year and almost no replies to them :( > > > > Jörg had some good points about Extension Manager support and other > > tools for extensions and you may know I'm working on new extension > > creation tools as well. We can also make sure the Developer Guide is > > up to date and things like that. > > > >> > >> > >> I am just wondering what everyone else thinks. > >> > >> All the best > >> > >> Peter > >> > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > >
Re: imposible to open files
Hello Iouri, Would you please try the release candidate from below link and let us know if it fixes the issue? Please choose the file appropriate for your language of choice. Thank you. https://dist.apache.org/repos/dist/dev/openoffice/4.1.9-RC1/binaries/ On Fri, Feb 5, 2021 at 1:42 AM Iouri Tcherniakov, Toronto, Canada wrote: > After installation update from apple, program Big Sure MacOS version11.1 > Impossible to reopen some files especially one in Exel . Looks like need > to switch to apple office. This is unacceptable. > > Please advise, > > iouri >
Re: Problem since inställning MacOS Big Sur
Hello, There is a release candidate that you can test. Please see this link https://dist.apache.org/repos/dist/dev/openoffice/4.1.9-RC1/binaries/ Choose the binary that's appropriate for your language. I've tested on my macOS 11.1 and it works fine. On Sun, Jan 31, 2021 at 1:55 AM Peter Gisle wrote: > Hi > > Since installing macOS Big Sur I have problem opening documents sent to > me. > These files arrive with an OpenOffice logo but a file type pertaining to > Microsoft Office (Word or Ecxcel): > > > > When I try to pen the file OpenOffice shuts down and I am asked if I want > to open again - but to no avail. > > Can you help? > > Peter Gisle > Stockholm, Sweden > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Release macOS community builds AOO 4.1.9-RC1 as GA
+1 Tested with the below binary and system configuration and unable to reproduce Issue 128415 and 128426, although the users reporting the issues were using macOS 11.0 Apache_OpenOffice_4.1.9_MacOS_x86-64_install_en-US.dmg AOO419m1(Build:9805) - Rev. 561082130a 2021-01-28 11:51:18 (Thu, 28 Jan 2021) - Darwin x86_64 System Version: macOS 11.1 (20C69) Kernel Version: Darwin 20.2.0 Processor Name: 8-Core Intel Core i9 Processor Speed: 2.3 GHz 16G RAM On Fri, Jan 29, 2021 at 4:52 AM Jim Jagielski wrote: > FTR: +1 from me. > > > On Jan 28, 2021, at 2:47 PM, Jim Jagielski wrote: > > > > I am calling a VOTE on releasing the complimentary community builds of > > macOS Apache OpenOffice 4.1.9-RC1 as GA. > > > > These artifacts can be found at: > > > > https://dist.apache.org/repos/dist/dev/openoffice/4.1.9-RC1/binaries/ > > > > This vote overrides the previous vote due to some regressions noted > > in the original macOS builds. This vote does not affect the Windows > > or Linux builds or the source files. There are no source code changes > > reflected in this revision: this is 100% a build replacement. As such, > > the About OpenOffice window should show: > > > > AOO419m1(Build:9805) - Rev. 561082130a > > 2021-01-28 11:51:18 (Thu, 28 Jan 2021) - Darwin x86_64 > > > > Note the revised build date. > > > > Please cast your vote: > > > > The Release Candidate is good for production/GA: > > > > [ ] yes / +1 > > > > [ ] no / -1 > > > > > > - > > 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: ext_libraries/apr-util module
I'm using Xcode 12.3 On Thu, Jan 28, 2021 at 4:24 AM Jim Jagielski wrote: > Which version of Xcode? > > > On Jan 27, 2021, at 5:48 PM, Dylan Pham wrote: > > > > Hello, > > > > I'm building trunk/450 on macos big sur and got an error below: > > > > Makefile:50: /Users/devops1/aoodev/openoffice/ext_libraries/apr-util/ > > unxmaccx.pro/misc/build/apr-util-1.6.1/build/rules.mk: No such file or > > directory > > make: *** No rule to make target > > `/Users/devops1/aoodev/openoffice/ext_libraries/apr-util/ > > unxmaccx.pro/misc/build/apr-util-1.6.1/build/rules.mk'. Stop. > > dmake: Error code 2, while making './ > > unxmaccx.pro/misc/build/so_built_aprutil' > > > > Questions: > > 1. the apr module version is 1.6.5, does apr-util version need to match > it? > > 2. I checked the apr module and there is no rules.mk file there and it > > built successfully. Not sure why it's required for apr-util, as specified > > in the makefile.in as below: > > > > # bring in rules.mk for standard functionality > > @INCLUDE_RULES@ > > @INCLUDE_OUTPUTS@ > > > > 3. If I need to have a rules.mk what do I need to do? Is there a > template? > > > > Thank you, > > Dylan > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: ext_libraries/apr-util module
I found apr_rules.mk and apr_rules.mk.in so I'll use these as templates to build apr_util and see how it goes. If I'm heading in wrong direction please feel free to let me know, thanks. Dylan On Wed, Jan 27, 2021 at 2:48 PM Dylan Pham wrote: > Hello, > > I'm building trunk/450 on macos big sur and got an error below: > > Makefile:50: /Users/devops1/aoodev/openoffice/ext_libraries/apr-util/ > unxmaccx.pro/misc/build/apr-util-1.6.1/build/rules.mk: No such file or > directory > make: *** No rule to make target > `/Users/devops1/aoodev/openoffice/ext_libraries/apr-util/ > unxmaccx.pro/misc/build/apr-util-1.6.1/build/rules.mk'. Stop. > dmake: Error code 2, while making './ > unxmaccx.pro/misc/build/so_built_aprutil' > > Questions: > 1. the apr module version is 1.6.5, does apr-util version need to match it? > 2. I checked the apr module and there is no rules.mk file there and it > built successfully. Not sure why it's required for apr-util, as specified > in the makefile.in as below: > > # bring in rules.mk for standard functionality > @INCLUDE_RULES@ > @INCLUDE_OUTPUTS@ > > 3. If I need to have a rules.mk what do I need to do? Is there a template? > > Thank you, > Dylan > > >
ext_libraries/apr-util module
Hello, I'm building trunk/450 on macos big sur and got an error below: Makefile:50: /Users/devops1/aoodev/openoffice/ext_libraries/apr-util/ unxmaccx.pro/misc/build/apr-util-1.6.1/build/rules.mk: No such file or directory make: *** No rule to make target `/Users/devops1/aoodev/openoffice/ext_libraries/apr-util/ unxmaccx.pro/misc/build/apr-util-1.6.1/build/rules.mk'. Stop. dmake: Error code 2, while making './ unxmaccx.pro/misc/build/so_built_aprutil' Questions: 1. the apr module version is 1.6.5, does apr-util version need to match it? 2. I checked the apr module and there is no rules.mk file there and it built successfully. Not sure why it's required for apr-util, as specified in the makefile.in as below: # bring in rules.mk for standard functionality @INCLUDE_RULES@ @INCLUDE_OUTPUTS@ 3. If I need to have a rules.mk what do I need to do? Is there a template? Thank you, Dylan
Re: macOS Big Sur configure issue: clang errors
That fixed my clang errors. Thank you Jim.
Dylan
On Thu, Jan 21, 2021 at 3:33 AM Jim Jagielski wrote:
> My guess is that you do not have SDKROOT defined in your environment.
>
> Before running configure make sure you do:
>
> export SDKROOT=$(xcrun --sdk macosx --show-sdk-path)
>
> > On Jan 20, 2021, at 6:09 PM, Dylan Pham wrote:
> >
> > So I ran below:
> >
> > ./configure \
> >--enable-verbose \
> >--with-openldap \
> >--enable-category-b \
> >--enable-bundled-dictionaries \
> >--enable-wiki-publisher \
> >--without-junit \
> >--with-jdk-home="$JAVA_HOME" \
> >--with-ant-home="$ANT_HOME" \
> >--with-epm=/usr/local/bin/epm \
> >--with-dmake-path=/usr/local/bin/dmake \
> >--without-stlport \
> >--with-package-format="dmg" \
> >--disable-systray \
> >--with-alloc=internal \
> >--with-lang="${LANGS}"
> >
> > and I got errors below in terminal (truncated):
> >
> > checking gcc home... /usr
> > checking for gcc... /Library/Developer/CommandLineTools/usr/bin/clang
> -arch x86_64
> > checking whether the C compiler works... no
> > configure: error: in `/Users/devops1/aoodev/openoffice/main':
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details
> >
> > Below is a snippet from config.log, full file has been attached:
> >
> ---configure:6790:
> $? = 0
> > configure:6779: /Library/Developer/CommandLineTools/usr/bin/clang -arch
> x86_64 -V >&5
> > clang: error: argument to '-V' is missing (expected 1 value)
> > clang: error: no input files
> > configure:6790: $? = 1
> > configure:6779: /Library/Developer/CommandLineTools/usr/bin/clang -arch
> x86_64 -qversion >&5
> > clang: error: unknown argument '-qversion'; did you mean '--version'?
> > clang: error: no input files
> > configure:6790: $? = 1
> > configure:6810: checking whether the C compiler works
> > configure:6832: /Library/Developer/CommandLineTools/usr/bin/clang -arch
> x86_64conftest.c >&5
> > ld: library not found for -lSystem
> > clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> > .
> > .
> > configure: exit 77
> >
> ---
> > Upon checking xcode-select -v shows version 2384 (Xcode 12.3)
> >
> > Should I replace in configure file -qversion with --version as the error
> output seems to suggest?
> > clang: error: unknown argument '-qversion'; did you mean '--version'?
> >
> > How do I find out what line in configure file this error below is
> referring to?
> > clang: error: argument to '-V' is missing (expected 1 value)
> >
> > What does the number refers to in configure:: in the config.log
> (e.g configure:6779:) ?
> >
> > Any idea what I can try to resolve these configure errors? Or is it ok
> to ignore these errors and proceed with the rest of instructions to build?
> Thanks.
> >
> > Dylan
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
macOS Big Sur configure issue: clang errors
So I ran below:
./configure \
--enable-verbose \
--with-openldap \
--enable-category-b \
--enable-bundled-dictionaries \
--enable-wiki-publisher \
--without-junit \
--with-jdk-home="$JAVA_HOME" \
--with-ant-home="$ANT_HOME" \
--with-epm=/usr/local/bin/epm \
--with-dmake-path=/usr/local/bin/dmake \
--without-stlport \
--with-package-format="dmg" \
--disable-systray \
--with-alloc=internal \
--with-lang="${LANGS}"
and I got errors below in terminal (truncated):
checking gcc home... /usr
checking for gcc... /Library/Developer/CommandLineTools/usr/bin/clang -arch
x86_64
checking whether the C compiler works... no
configure: error: in `/Users/devops1/aoodev/openoffice/main':
configure: error: C compiler cannot create executables
See `config.log' for more details
Below is a snippet from config.log, full file has been attached:
---configure:6790:
$? = 0
configure:6779: /Library/Developer/CommandLineTools/usr/bin/clang -arch
x86_64 -V >&5
clang: error: argument to '-V' is missing (expected 1 value)
clang: error: no input files
configure:6790: $? = 1
configure:6779: /Library/Developer/CommandLineTools/usr/bin/clang -arch
x86_64 -qversion >&5
clang: error: unknown argument '-qversion'; did you mean '--version'?
clang: error: no input files
configure:6790: $? = 1
configure:6810: checking whether the C compiler works
configure:6832: /Library/Developer/CommandLineTools/usr/bin/clang -arch
x86_64conftest.c >&5
ld: library not found for -lSystem
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
.
.
configure: exit 77
---
Upon checking xcode-select -v shows version 2384 (Xcode 12.3)
Should I replace in configure file -qversion with --version as the error
output seems to suggest?
clang: error: unknown argument '-qversion'; did you mean '--version'?
How do I find out what line in configure file this error below is referring
to?
clang: error: argument to '-V' is missing (expected 1 value)
What does the number refers to in configure:: in the config.log
(e.g configure:6779:) ?
Any idea what I can try to resolve these configure errors? Or is it ok to
ignore these errors and proceed with the rest of instructions to build?
Thanks.
Dylan
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: SCONS development state
Thank you Peter, this will be very helpful. Dylan On Sat, Jan 16, 2021 at 10:33 AM Peter Kovacs wrote: > Hello Dylan, > > Hello Ho Wang, > > > I am sorry it took me a while. But here Damjan explains all about the > SCONS implementation. Please if still time and interest is there have a > look. > > > https://lists.apache.org/thread.html/r911b40a582019f641e93253df07341370cb9aeb9d1dc50474e48aa09%40%3Cdev.openoffice.apache.org%3E > > > I hope this helps > > All the Best > > Peter > > -- > This is the Way! http://www.apache.org/theapacheway/index.html >
Question regarding build.pl
Hello everyone, I was looking at this build script main/solenv/bin/build.pl and per the attached screenshot, on line 2611, what does this line do? Was there supposed to be a substitution operator at this line? Thanks. Dylan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
