From owner-freebsd-ports@FreeBSD.ORG Fri Aug 24 19:31:03 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 195E316A421 for ; Fri, 24 Aug 2007 19:31:03 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id ED2C913C481 for ; Fri, 24 Aug 2007 19:31:02 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id 9F89365508 for ; Fri, 24 Aug 2007 14:31:02 -0500 (CDT) Date: Fri, 24 Aug 2007 14:31:02 -0500 From: Paul Schmehl To: FreeBSD Ports Message-ID: In-Reply-To: <200708241918.l7OJIB1L019257@smtpclu-3.eunet.yu> References: <20070824172437.GA6987@darklight.org.ru> <092EAD30872B43867019863F@utd59514.utdallas.edu> <200708241918.l7OJIB1L019257@smtpclu-3.eunet.yu> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========DCE2DEEE40C6A57EB2F5==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 19:31:03 -0000 --==========DCE2DEEE40C6A57EB2F5========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Friday, August 24, 2007 21:13:20 +0200 Nikola Lecic =20 wrote: > On Fri, 24 Aug 2007 13:59:10 -0500 > Paul Schmehl wrote: > >> --On Friday, August 24, 2007 21:24:37 +0400 Yuri Pankov >> wrote: >> >> > 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=3Dyes. In your case it was treated as make >> > target, hence error message. >> > >> Yes, but the point is, I *wasn't* trying to build with that flag >> *and* it wasn't *supposed* to build with that flag. Yet it was >> trying to (and failing) anyway. The default value of the OPTION is >> "off", and I didn't turn it on. > > The point of this line > > ---> Building '/usr/ports/shells/scponly' with make flags: > WITH_SCPONLY_WINSCP > > is that this message occurs only if you use --make-args or if you > define something in /usr/local/etc/pkgtools.conf. > > 'Building ... with make flags...' message _doesn't_ appear if you have > saved/changed options in /var/db/ports (this is indicated with "Found > saved configuration...". I reproduced your error like this: > > nyx# portupgrade -f -m 'WITH_SCPONLY_WINSCP' scponly > ---> Reinstalling '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_2) (clean error) > ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > > So, 'WITH_SCPONLY_WINSCP' somehow leaked into make_args of the > portupgrade script -- and you can easily find where. Do you use > portupgrade-devel? > No. As you correctly surmised, I had something in pkgtools.conf (which I=20 had obviously forgotten.) Problem solved. --=20 Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========DCE2DEEE40C6A57EB2F5==========--