Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote: > Hi, > > Am 22.07.23 um 16:09 schrieb Andreas Schwab: >> On Jul 22 2023, Rene Engelhard wrote: >> >>> Am 22.07.23 um 15:53 schrieb Andreas Schwab: >>>> On Jul 22 2023, Rene Engelhard wrote: >>>> >>>>> Does opensuse have some public git/$VCS? >>>> https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64 >>> Thanks... >>> >>> But maybe I am too blind. >>> >>> I don't see the actual spec + related files anywhere? >> See Overview: >> >> https://build.opensuse.org/package/show/openSUSE:Factory:RISCV/libreoffice > > Thanks. > > > I don't see anyone obvious there (except not running *any* test) there > offhand, though. I tried to enable the smoketest, but it fails even on x86-64: https://build.opensuse.org/project/show/home:Andreas_Schwab:riscv:libreoffice Since I don't know much about the libreoffice sources, I have just copied the %check section from an old revision of our libreoffice package. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote: > Am 22.07.23 um 15:53 schrieb Andreas Schwab: >> On Jul 22 2023, Rene Engelhard wrote: >> >>> Does opensuse have some public git/$VCS? >> https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64 > > Thanks... > > But maybe I am too blind. > > I don't see the actual spec + related files anywhere? See Overview: https://build.opensuse.org/package/show/openSUSE:Factory:RISCV/libreoffice -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote: > Does opensuse have some public git/$VCS? https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64 > (Though I would more bet of some system evironment thingy) Perhaps it is a matter of using a good java. Have you tried java 19 or 20? -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote: > Hi, > > Am 22.07.23 um 14:28 schrieb Andreas Schwab: >> On Jul 22 2023, Rene Engelhard wrote: >> >>> Yes. _basically_. (Only with -O0 or maybe -Os as upstreams makefile says, >>> though) >> On openSUSE Factory, libreoffice is built with the usual compiler flags, >> wich includes full optimisation and hardening. > > Which gives the smoketest test failure here I pointed out (again) in my > other mail. $ find /usr/lib64/libreoffice/ -name "*smoke*" /usr/lib64/libreoffice/program/classes/smoketest.jar How can I run that? -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote:
> https://lists.debian.org/debian-riscv/2023/07/msg00014.html is for manual
> thing. And the IRC log shows that even libreoffice-lightproof-en etc don't
> appear as bundled extensions.
$ unopkg list --bundled
All deployed bundled extensions:
Identifier: org.openoffice.en.hunspell.dictionaries
Version: 2022.05.01
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/lightproof-en
is registered: yes
Media-Type: application/vnd.sun.star.package-bundle
Description:
bundled Packages: {
URL:
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/lightproof-en/Lightproof.components
is registered: yes
Media-Type: application/vnd.sun.star.uno-components
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/lightproof-en/Linguistic.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
}
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote: > And that includes LibreOffice-bundled extensions like the > english,hungarian,russian grammar checker for example. Ot external finnish > spellchecking, hyphenation and grammer checking. Or turkish spellchecing. > > And those are extensions written in python which neither register when > registering manually nor when being installed as bundled extensions (see > the discussion in this thread, not going to reiterate) How can I test that? I have never used libreoffice before, so I don't know what to look for. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote: > Yes. _basically_. (Only with -O0 or maybe -Os as upstreams makefile says, > though) On openSUSE Factory, libreoffice is built with the usual compiler flags, wich includes full optimisation and hardening. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jul 22 2023, Rene Engelhard wrote: > Just not registering or unregistering *any* extension. What does that mean? I haven't seen any errors about extensions. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: unbreaking LibreOffices tests on at least release architectures
On Jun 18 2023, Rene Engelhard wrote: > For riscv64 I already pointed that out in the thread starting at > https://lists.debian.org/debian-riscv/2023/06/msg0.html, but for the > other architectures there is the mail now. riscv64 is different because > the failures are even more big than any other down below and it's actually > a new architecture anyway. Libreoffice is actually basically working on riscv64. I have tested it with openSUSE Tumbleweed on BeagleV Beta and Hifive Unmatched (with an AMD graphics card). -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: Same procedure as every year: GCC defaults change (GCC 9)
On Jul 28 2019, Aurelien Jarno wrote: > The two MIPS libffi patches have been accepted upstream (i.e. in the > libffi git repository) 1.5 years ago for one and 4 years ago for the > other. I know there hasn't been any recent libffi release, so what can > be done to sync the gcc repository? Would it be possible to stop using > that outdated embedded copy and use the debian libffi package instead? The gcc copy of libffi accepts backports. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
