Re: [LyX/master] Avoid warnings with gcc 9
Le 12 juin 2019 21:52:09 GMT+02:00, "José Abílio Matos" a écrit : >On Wednesday, 12 June 2019 17.42.46 WEST Jean-Marc Lasgouttes wrote: >> commit 134f3aedaf4150367cdc2f6855d695d3791a5353 >> Author: Jean-Marc Lasgouttes >> Date: Wed Jun 12 18:49:29 2019 +0200 >> >> Avoid warnings with gcc 9 > >Bah... >Now we get again a boring compile output. ;-) > >Thank you. :-) >-- >José Abílio Note that we still have to fix the warnings, I just disabled them. JMarc
Re: [LyX/master] Avoid warnings with gcc 9
On Wednesday, 12 June 2019 17.42.46 WEST Jean-Marc Lasgouttes wrote: > commit 134f3aedaf4150367cdc2f6855d695d3791a5353 > Author: Jean-Marc Lasgouttes > Date: Wed Jun 12 18:49:29 2019 +0200 > > Avoid warnings with gcc 9 Bah... Now we get again a boring compile output. ;-) Thank you. :-) -- José Abílio
Re: [LyX/master] Get full version of gcc
On Wednesday, 12 June 2019 20.35.24 WEST Kornel Benko wrote: > I don't see it. Just compiled gcc9.1.0. Both calls return the full version > here. > > > $/usr/local/gcc9.1/bin/gcc -dumpversion > 9.1.0 > $/usr/local/gcc9.1/bin/gcc -dumpfullversion > 9.1.0 > > Kornel I do $ gcc -dumpversion 9 $ gcc -dumpfullversion 9.1.1 -- José Abílio
Re: Hunspell update to 1.7.0
Le 06/06/2019 à 16:42, Jürgen Spitzmüller a écrit : Do you still remember how you did that for 1.6.2? I think I just copied over all relevant files from the hunspell tarball to our dir. I did that now. We'll see. At least I checked that dist still works. JMarc
Re: LyX 2.3.3 Tarballs
On Tuesday, 11 June 2019 14.36.50 WEST José Abílio Matos wrote: > Builds cleanly on Fedora 29 to Rawhide (to be Fedora 31). Actually it also > does on Fedora 28 but that it is at EOL (End of Live) stage. > > https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/ > > As soon as the release announce is done I will move it to updates-testing > repositories. Just like Jean-Pierre I can tell that all tests passed on all Fedora releases and architectures (i386, x86_64 and aarch64). https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/build/934304/ You can see the output of the build (in this case for rawhide - F31 on x84_64): https://copr-be.cloud.fedoraproject.org/results/jamatos/lyx-next/fedora-rawhide-x86_64/00934304-lyx/builder-live.log Due to some timing issues the ppc64le (ppc64 Little Endian) servers on copr decided to take some time off. :-) Really, since Sunday that those builders are on strike and are ignoring us so left them out for the moment. :-) -- José Abílio
Re: LyX 2.3.3 Tarballs
Le 11/06/2019 à 18:38, Jean-Pierre Chrétien a écrit : All common manuals compile fine with TL 2019. and 'make check' is successful (9 tests are OK). -- Jean-Pierre
Re: [PATCH] Make math autocorrrect work with more than 2 chars
Le 02/06/2019 à 21:48, Jean-Marc Lasgouttes a écrit : I have not however removed references to this feature in docoumentation, hopefully someone more familiary with the LyX code base will know where these are. Indeed we have to check that. I actually suspect that this feature is not documented. How did you learn about it? I finally found section 2.6 of UserGuide and updated it. JMarc
Re: LyX 2.3.3 Tarballs
Am Dienstag, 11. Juni 2019, 22:18:26 CEST schrieb Richard Kimberly Heck: > On 6/11/19 3:19 PM, Kornel Benko wrote: > > Am Dienstag, 11. Juni 2019, 14:11:17 CEST schrieb Richard Kimberly Heck: > >> On 6/11/19 12:57 PM, Kornel Benko wrote: > >>> Am Dienstag, 11. Juni 2019, 14:01:24 CEST schrieb Pavel Sanda: > On Tue, Jun 11, 2019 at 12:21:51PM +0200, Kornel Benko wrote: > > Tried to compile with cmake and enabled tests ... ( > > -DLYX_ENABLE_EXPORT_TESTS=ON) > I propose that before cmake tests is considered to be showstopper for > release > they do roughly the same as autotools make check (testing various > src/../tests > codes, not this development stuff which seems extremely fragile to all > sorts > of circumstances). > > Pavel > > >>> I suppose, you have tried to use the devel tests, still my opinion is > >>> different. > >>> Nobody is forced to enable these tests, but why should we force anybody > >>> to not > >>> be able to run them? > >> What do we need to do to make the run-able? What's missing? > >> > >> Riki > >> > >> > > Attached should be OK. At least, with the mentioned files, the tests are > > running. > > Please go ahead. I'll rebuild the tarballs. > > This won't affect the binaries already built, right? Yes, nothing to do with binaries. It is only some extra data we provide in case a user wants to compile on his own _and_ wants to run some export tests. > Riki > Done at ac724043. Kornel signature.asc Description: This is a digitally signed message part.
