From owner-freebsd-ports Thu Dec 27 10:30:17 2001 Delivered-To: freebsd-ports@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DAA2037B419 for ; Thu, 27 Dec 2001 10:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fBRIU1V39103; Thu, 27 Dec 2001 10:30:01 -0800 (PST) (envelope-from gnats) Date: Thu, 27 Dec 2001 10:30:01 -0800 (PST) Message-Id: <200112271830.fBRIU1V39103@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Yoichi NAKAYAMA Subject: Re: ports/33249: New port: Code converter for any of Mule's code Reply-To: Yoichi NAKAYAMA Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR ports/33249; it has been noted by GNATS. From: Yoichi NAKAYAMA To: Teruaki Ata Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/33249: New port: Code converter for any of Mule's code Date: Fri, 28 Dec 2001 03:27:41 +0900 Hi, I've tested this port, but coco doesn't work with message Initialization of Mule libarary failed. and m2ps does not work and dumps core on my 4.4-stable machine. Have you tested them? I think you should test on environment without mule itself. At least, first one would not appear with mule's files on share/mule/emacs/19.34/etc/. FYI, privately I also have coco port (at least it works well on my machine) http://people.freebsd.org/~yoichi/coco.tar.gz (It originates in mule-common port.) Refer on it, if you like. Also, I think this port seems to have many unnecessary files for coco and m2ps like files/patch-lisp_sj3-egg.el etc. P.S. If the new port originates in another existing one, note the origin (Such one should be repocopied before committing), please. Best regards, -- Yoichi Nakayama To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message