Date: 08 Apr 1999 21:17:31 -0500 From: Joel Ray Holveck <joelh@gnu.org> To: Steve Price <sprice@hiwaay.net> Cc: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>, current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: emacs* broken in -current (was Re: Vtable thunks with egcs) Message-ID: <86lng2wn9g.fsf@detlev.UUCP> In-Reply-To: Steve Price's message of "Thu, 8 Apr 1999 17:58:59 -0500 (CDT)" References: <Pine.OSF.4.10.9904081749420.6267-100000@fly.HiWAAY.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> You are absolutely right. I just tried the new version of emacs > that I built on my pre-egcs box and it doesn't work on that box > either. This definitely doesn't appear to be anything caused by > changing to egcs. Not that it matters much but for grins I just > built/installed the xemacs port and it _does_ appear to work. I've been having no problems with an Emacs 20.3 and X11R6 built in October on a -current system from April 6. (The Emacs is ELF, and built from my own sources instead of the port.) I'd like to track this down; could people give me more info privately? rms is looking at releasing a mostly bugfix Emacs, possibly tommorow, but it may be another month (he's about to leave town). I haven't been watching the changes; there may be some X-related fixes in there. Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86lng2wn9g.fsf>