From owner-freebsd-ports@FreeBSD.ORG Fri Aug 24 17:24:42 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92A1816A419 for ; Fri, 24 Aug 2007 17:24:42 +0000 (UTC) (envelope-from yuri@darklight.org.ru) Received: from darklight.org.ru (crsd-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2d5::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5D65313C459 for ; Fri, 24 Aug 2007 17:24:40 +0000 (UTC) (envelope-from yuri@darklight.org.ru) Received: from darklight.org.ru (yuri@darklight.org.ru [127.0.0.1]) by darklight.org.ru (8.14.1/8.14.1) with ESMTP id l7OHObb8036431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Aug 2007 21:24:37 +0400 (MSD) (envelope-from yuri@darklight.org.ru) Received: (from yuri@localhost) by darklight.org.ru (8.14.1/8.14.1/Submit) id l7OHObQg036430; Fri, 24 Aug 2007 21:24:37 +0400 (MSD) (envelope-from yuri@darklight.org.ru) Date: Fri, 24 Aug 2007 21:24:37 +0400 From: Yuri Pankov To: Paul Schmehl Message-ID: <20070824172437.GA6987@darklight.org.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Ports Subject: Re: Weird problem with shells/scponly X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2007 17:24:42 -0000 On Fri, Aug 24, 2007 at 12:13:16PM -0500, Paul Schmehl wrote: > I just encountered a very strange problem with shells/scponly. When I > tried to portupgrade it, I consistently got an error: > > /usr/ports/shells/scponly]# portupgrade scponly* > ---> Upgrading 'scponly-4.6_1' to 'scponly-4.6_2' (shells/scponly) > ---> Building '/usr/ports/shells/scponly' with make flags: > WITH_SCPONLY_WINSCP > make: don't know how to make WITH_SCPONLY_WINSCP. Stop > ** Listing the failed packages (*:skipped / !:failed) > ! shells/scponly (scponly-4.6_1) (clean error) > ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > > That option wasn't selected and isn't selected by default. I tried make > rmconfig/make config, and all the other tricks I know, including make > distclean/portupgrade scponly*. > > Finally I deinstalled the port and reinstalled it. It installs fine both > with and without that knob. > > Is portupgrade saving some setting somewhere that is different from config? > > (I've cc'd the port maintainer although it doesn't look like there's a > problem with the port itself.) > > -- > Paul Schmehl (pauls@utdallas.edu) > Senior Information Security Analyst > The University of Texas at Dallas > http://www.utdallas.edu/ir/security/ It's only a make flag and is passed to make as it is. You need to define it using -DWITH_SCPONLY_WINSCP or by assigning some value to it: WITH_SCPONLY_WINSCP=yes. In your case it was treated as make target, hence error message. HTH, Yuri