Bug 17805

Summary: ${CHMOD} is not set in ports makefiles after upgrading
Product: Base System Reporter: tla <tla>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description tla 2000-04-05 02:40:01 UTC
I installed the package for the ports collection (32upgrade.tgz) as
recommended.  Now when building ports ${CHMOD} is null, so a make
install can randomly fail with a message like "640: command not found"
when it should be /bin/chmod 640 <somefile>

I believe this is the issue...I've had to hack several port makefiles
recently to add a value for ${CHMOD}.  If this is too vague, tell me to
go get stuffed, and I'll get more detailed about it next time it happens.

Fix: 

I'm not a make guru, but somewhere in there ${CHMOD} needs to get set.
How-To-Repeat: Install the ports upgrade package.  Build a port that uses ${CHMOD}
in its makefile (the cyrus imap server is one).  Notice that make install
fails with "640: command not found" or similar.
Comment 1 jedgar 2000-04-05 02:46:31 UTC
On Tue, 4 Apr 2000 tla@spiderchain.com wrote:

> 
> >Number:         17805
> >Category:       misc
> >Synopsis:       ${CHMOD} is not set in ports makefiles after upgrading
> 
> I believe this is the issue...I've had to hack several port makefiles
> recently to add a value for ${CHMOD}.  If this is too vague, tell me to
> go get stuffed, and I'll get more detailed about it next time it happens.
> 
> >How-To-Repeat:
> Install the ports upgrade package.  Build a port that uses ${CHMOD}
> in its makefile (the cyrus imap server is one).  Notice that make install
> fails with "640: command not found" or similar.
> >Fix:
> I'm not a make guru, but somewhere in there ${CHMOD} needs to get set.
> 
> 

jedgar@pluto:/usr/ports/Mk$ ident bsd.port.mk && grep chmod bsd.port.mk
bsd.port.mk:
     $FreeBSD: ports/Mk/bsd.port.mk,v 1.332 2000/04/02 08:32:26 asami Exp
$
     $NetBSD: $
CHMOD?=         /bin/chmod
jedgar@pluto:/usr/ports/Mk$

Can you let us know what errors you are seeing?  Also, check that
/usr/ports/Mk/* and the port(s) you are building are up-to-date.

-----
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve   -   http://www.FreeBSD.org
Comment 2 Chris D.Faulhaber freebsd_committer freebsd_triage 2000-04-08 13:01:01 UTC
State Changed
From-To: open->closed

Originator says updating his ports fixed the problem