From owner-freebsd-current Sun Dec 14 11:59:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA04964 for current-outgoing; Sun, 14 Dec 1997 11:59:49 -0800 (PST) (envelope-from owner-freebsd-current) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA04959 for ; Sun, 14 Dec 1997 11:59:45 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.7) with ESMTP id LAA20309; Sun, 14 Dec 1997 11:59:40 -0800 (PST) (envelope-from jdp) Message-Id: <199712141959.LAA20309@austin.polstra.com> To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: problems with gzip'd executables In-reply-to: Your message of "14 Dec 1997 19:46:45 +0100." <864t4brcdm.fsf@bitbox.follo.net> Date: Sun, 14 Dec 1997 11:59:40 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Personally, I feel that you should just drop the hacks to > handle old emacs binaries and send a clear heads-up to > current@FreeBSD.ORG. Current is for developers - we should have the > hardware to handle an Emacs re-compile :-) I agree with you. I would like to put a patch into the emacs port before I back out the ld.so hack, though. I probably can't get around to doing that for about a week. I have the patch, but I don't have any more time to spend on this until next weekend. Meanwhile, it turns out that the gzipped executable problem was really a bug in imgact_gzip.c. So I committed a fix for that. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth