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
>
>
Re: Check for English spelling extension updates broken?
Hi Andrea > On 01/21/2021 11:39 PM Andrea Pescetti wrote: > OK, thank you for checking. I've now reverted the fix and we'll go live > with a more complete version when people will have upgraded to 4.1.9. Agreed. Thank you! > But when we are not in proximity of a release, we can trigger the update > perhaps once a month; fact is, the process I could find is still > cumbersome and requires shell commands to be run, so until we streamline > it it won't be run very frequently. And I would be against fully > automating it as some anti-spam checks might be needed, even though spam > is a problem on the Templates site much more than the Extensions site. If/when the process is streamlined I can volunteer to run it on a monthly/2 months basis (except before and after a new AOO release). It should be an improvement compared to 3 years :) Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
On 21/01/2021 Pedro Lino wrote: Please let me know if it works; if it does, I will then revert it and republish only after 4.1.9 is out ... It is fixed indeed (although I get 2 notifications for that extension, but one problem at a time!). Thanks! OK, thank you for checking. I've now reverted the fix and we'll go live with a more complete version when people will have upgraded to 4.1.9. if an extension author submits a new version does s/he have permission to do that manual update or s/he has to request someone to do it? Extensions authors cannot trigger the update. Site moderators can (and probably should) do it once in a while as a routine task. The worst period is for sure when you are close to a release and the few weeks after a release, since before the release you might be downloading a newer version than the one coming with the release (like: if a bundled extension was updated yesterday, 4.1.9 would contain an older extension version than the one people would download today). But when we are not in proximity of a release, we can trigger the update perhaps once a month; fact is, the process I could find is still cumbersome and requires shell commands to be run, so until we streamline it it won't be run very frequently. And I would be against fully automating it as some anti-spam checks might be needed, even though spam is a problem on the Templates site much more than the Extensions site. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Release AOO 4.1.9-RC1 as GA
On 18/01/21 Jim Jagielski wrote: I am calling a VOTE on releasing the source and complimentary community builds of Apache OpenOffice 4.1.9-RC1 as GA. The Release Candidate is good for production/GA: [X] yes / +1 [ ] no / -1 My vote is based on [X] binding (member of PMC) [X] I have built and tested the RC from source on platform [ Linux64 ] [ ] I have tested the binary RC on platform [ ] - Built on CentOS 7 64-bit, it/en, RPM/DEB/installed - Tested the resulting DEBs (it) on Ubuntu 20.04 - checked LICENSE and NOTICE files - checked that the .bz2 and .gz versions of the source package match Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [VOTE] Release AOO 4.1.9-RC1 as GA
Hi Jim, all The Release Candidate is good for production/GA: [x] yes / +1 [ ] no / -1 My vote is based on [ ] binding (member of PMC) [x] I have built and tested the RC from source on platform [Ubuntu 18.04 x64] [x] I have tested the binary RC on platform [Ubuntu 14.04 x86, Ubuntu 20.04 x64, Windows XP x86, Windows 7 x64] Verified SHA256 and SHA512 for the Windows and Linux DEB binaries, opened documents (ODT, ODS, ODP, ODF, DOC, XLS, PPT and DOCX, XLSX, PPTX), checked for Updates and Extension Updates) Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Hi Andrea > On 01/21/2021 8:04 PM Andrea Pescetti wrote: > I believe it's fixed now (limited to the specific case of the English > dictionary; I had to find some workarounds so I enabled only that > extension for testing). > Please let me know if it works; if it does, I will then revert it and > republish only after 4.1.9 is out (or users will be confused by the > double update; this is exactly the reason for the update to be manual by > the way). It is fixed indeed (although I get 2 notifications for that extension, but one problem at a time!). Thanks! It makes sense that it is manually to prevent double notifications but if an extension author submits a new version does s/he have permission to do that manual update or s/he has to request someone to do it? Is that the part that needs to be documented? Thank you for solving this issue! Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
Am 21.01.21 um 21:04 schrieb Andrea Pescetti: On 20/01/2021 Andrea Pescetti wrote: I think we can fix it. Let me give it a try tomorrow. I believe it's fixed now (limited to the specific case of the English dictionary; I had to find some workarounds so I enabled only that extension for testing). Please let me know if it works; if it does, I will then revert it and republish only after 4.1.9 is out (or users will be confused by the double update; this is exactly the reason for the update to be manual by the way). [...] To check: in OpenOffice, check for Extensions Updates (not OpenOffice updates) and see whether this prompts you with an updated English dictionary to be downloaded (with a web browser, not within OpenOffice) and installed. wow \o/ , it's working again. :-) My English and German dictionaries want to be updated. A click on the [Install] button opens 2 tabs in my browser to the extension website for both dictionaries. Thanks for analysing this old problem. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for English spelling extension updates broken?
On 20/01/2021 Andrea Pescetti wrote: I think we can fix it. Let me give it a try tomorrow. I believe it's fixed now (limited to the specific case of the English dictionary; I had to find some workarounds so I enabled only that extension for testing). Please let me know if it works; if it does, I will then revert it and republish only after 4.1.9 is out (or users will be confused by the double update; this is exactly the reason for the update to be manual by the way). Before: $ curl -s https://extensions.openoffice.org/ExtensionUpdateService/check.Update | grep -A1 org.openoffice.en.hunspell.dictionaries After: $ curl -s https://extensions.openoffice.org/ExtensionUpdateService/check.Update | grep -A1 org.openoffice.en.hunspell.dictionaries To check: in OpenOffice, check for Extensions Updates (not OpenOffice updates) and see whether this prompts you with an updated English dictionary to be downloaded (with a web browser, not within OpenOffice) and installed. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Testing the new version
I have a macbook pro M1 2020 with macOS 11.1 (BigSur). I read about testing the AOO new version in the forum, "We are testing the solution at this point. If you want to join the test of the new version of this fix, drop an e-mail in English to the developers mailing list dev-AT-openoffice.apache-DOT-org. The more environments we test the sooner we can release." I am interested in the testing. Please advise what I should do next. Thanks for all you do! -- :) Betty Knott bettn...@gmail.com
Re: macOS Big Sur configure issue: clang errors
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
[GitHub] [openoffice] ardovm opened a new pull request #119: Clean $OUTPATH directories as well as $INPATH
ardovm opened a new pull request #119: URL: https://github.com/apache/openoffice/pull/119 It is possible that `$OUTPATH` directories are left by previous compilation attempts. A proof that `$OUTPATH` directories are used is the Perl script `solenv/bin/download_external_dependencies.pl` that looks for executables with "special handling" (i.e. dmake and epm) in `$SOLARENV/$OUTPATH`. 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
