Date: Mon, 10 Sep 2001 08:48:10 -0700 (PDT) From: John Merryweather Cooper <john_m_cooper@yahoo.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/30490: yacc in world does NOT fully respect TMPDIR setting Message-ID: <200109101548.f8AFmAQ68041@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 30490
>Category: bin
>Synopsis: yacc in world does NOT fully respect TMPDIR setting
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Sep 10 08:50:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: John Merryweather Cooper
>Release: FreeBSD 4.4-RC
>Organization:
>Environment:
FreeBSD johncoop.MSHOME 4.4-RC FreeBSD 4.4-RC #37: Sun Sep 9 20:09:38 PDT 2001 jmcoopr@johncoop.MSHOME:/usr/obj/usr/src/sys/JOHNCOOP i386
>Description:
man yacc claims that yacc respects the setting of TMPDIR, but this is definitely not true. The temp file(s) is generated in TMPDIR, but yacc continues to look for it in /tmp. As a result, the parser generation needlessly fails
>How-To-Repeat:
100% repeatable using ${PORTSDIR}/java/jdk13 as an example using these steps:
1) set TMPDIR (in my case, to /usr/tmp) to something other than /tmp
2) run "make" for jdk13 port
3) experience painful "crash-and-burn (tm)" action when yacc is called upon.
>Fix:
The workaround is to unset TMPDIR. The fix is to hack yacc to make it perform in accordance with its own man page.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109101548.f8AFmAQ68041>