Date: Sun, 7 May 2000 11:05:39 -0700 (PDT) From: dann@greycat.com To: FreeBSD-gnats-submit@freebsd.org Subject: ports/18434: EMACS_PORT_NAME variable breakes 'make readmes' Message-ID: <200005071805.LAA67672@mach.greycat.com>
next in thread | raw e-mail | index | archive | help
>Number: 18434
>Category: ports
>Synopsis: 'make readmes' broken by EMACS_PORT_NAME variable in ports/mail
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun May 07 11:10:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Dann Lunsford
>Release: FreeBSD 4.0-STABLE i386
>Organization:
You're kidding, right?
>Environment:
FreeBSD mach.greycat.com 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 28 09:26:56 PDT 2000 root@mach.greycat.com:/usr/src/sys/compile/SATELLITE i386
>Description:
I normally "make readmes" in /usr/ports after updating via cvsup. As of
today, it stops with errors in mail/mew*, mail/mule*, mail/wanderlust* because
of a bad value for EMACS_PORT_NAME.
===> mail/mew
Error: Bad value of EMACS_PORT_NAME: emacs.
Valid values are:
Emacs family: emacs19 mule19 emacs20
XEmacs family: xemacs19 xemacs20 xemacs21 xemacs21-mule
*** Error code 1
Stop.
*** Error code 1
Stop in /usr/ports/mail.
*** Error code 1
Stop in /usr/ports.
>How-To-Repeat:
'make readmes' in /usr/ports/mail
>Fix:
Not sure. I've worked around it by making the variable assignment conditional,
i.e. EMACS_PORT_NAME?= in mew, mew-mule, etc., and then do a
"make EMACS_PORT_NAME=emacs20 readmes", but I consider this to be a complete
kludge.
>Release-Note:
>Audit-Trail:
>Unformatted:
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?200005071805.LAA67672>