On Sun, Jun 03 2018, Kenneth R Westerback <kwesterb...@gmail.com> wrote: > On Wed, May 30, 2018 at 07:04:46PM +0200, Jeremie Courreges-Anglas wrote: >> On Wed, May 30 2018, kwesterb...@gmail.com wrote: >> >> On May 30, 2018, at 7:55 AM, Jeremie Courreges-Anglas <j...@wxcvbn.org> >> >> wrote: >> >> >> >>> On Tue, May 29 2018, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote: >> >>> So emacs-26.1 has been released yesterday: >> >>> >> >>> https://lists.gnu.org/archive/html/emacs-devel/2018-05/msg00765.html >> >>> >> >>> I doubt that this update addresses the bug encountered by Gr??goire, >> >>> Piotr and Manuel, but I don't think it will make it worse. >> >>> >> >>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29170 >> >>> >> >>> I have only built and tested this on amd64 so far, I'll handle armv7 >> >>> and sparc64 later. People running different archs and/or one of the >> >>> graphical flavors, your test reports are welcome! >> >> >> >> I could have mentioned that I intend to commit this soon. oks welcome >> >> too.
[...] > Once I got that far compiling the gtk+3 version went without incident > and the resulting port works at least as well as the RC1 > version. i.e. nothing breaks in usage case. > > so ok krw@ fwiw. Thanks, Ken. I'd like to move forward with this, but emacs is a pain portability-wise. I've been able to test it on amd64 and sparc64, where it works well. My armv7 machine is mostly offline so building fresh packages will take me more time than I'd like. Are there people around who could test on powerpc, armv7, arm64, mips64(el), hppa or i386? make install && emacs -Q would be a good enough test. Obviously oks (and regression reports) are still welcome. :) -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
