Date: Thu, 7 Jun 2018 16:58:54 -0400 From: Robert Huff <roberthuff@rcn.com> To: Yasuhiro KIMURA <yasu@utahime.org>, jrm@FreeBSD.org Cc: ports@FreeBSD.org, emacs@FreeBSD.org Subject: Re: Breakage of editors/tamago (Re: build errors after upgrading editors/emacs to version 26.1) Message-ID: <0ee40182-508d-b76c-02f7-c332ad158ecf@rcn.com> In-Reply-To: <20180608.042403.69889623405676957.yasu@utahime.org> References: <867enmndrn.fsf@phe.ftfl.ca> <20180608.042403.69889623405676957.yasu@utahime.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yasuhiro KIMURA wrote: > Hello all, > > From: Joseph Mingrone <jrm@FreeBSD.org> > Subject: build errors after upgrading editors/emacs to version 26.1 > Date: Tue, 29 May 2018 22:17:00 -0300 > >> Poudriere tests of all 'USES=emacs' ports with the latest editors/emacs >> (version 26.1) resulted in the following errors in either 10i386 or >> 11amd64 jails: >> >> editors/tamago (hrs@) > I'm investigating breakage of this port and submitted report of > current status as following bug report. > > Bug 228812 - editors/tamago: This port is broken only with restrected conditions > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228812 > > Summary of report is > > * This port is not broken with real environment (i.e. not > poudriere). it applies to all flavors. > * With poudriere full, canna and nox are broken. devel_full and > devel_nox are not. > * Accoding to the error message of poudriere build log, source of > build failure may be bug of Emacs 26.1. > > I'll continue to investigating this problem. But to be honest I'm far > from emacs lisp expert, and I know almost nothing about inside of > Emacs either. > > So please give me hint, idea, suggestion, etc if something hits upon > you about this problem. Additional data points: 1) Under Emacs, vm (mail reader viewmail) compiled for Emacs 25.3 does not work for 26.1. 2) Attempts to compile vm-8.2.0b under Emacs 26.1 fail due to changes in how Emacs processes Lisp. This is a registered bug, at "https://bugs.launchpad.net/vm/+bug/1763377". There is a patch, which at least in my case fixes one problem but reveals another. (Build log available on request.) Respectfully, Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0ee40182-508d-b76c-02f7-c332ad158ecf>