From owner-freebsd-questions@FreeBSD.ORG Tue Jan 28 08:03:48 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9FC8E2CE for ; Tue, 28 Jan 2014 08:03:48 +0000 (UTC) Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 601F4128A for ; Tue, 28 Jan 2014 08:03:48 +0000 (UTC) Received: from [87.78.0.77] (helo=elfsechsundzwanzig.de) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1W83dz-0004fk-Su; Tue, 28 Jan 2014 09:03:40 +0100 Date: Tue, 28 Jan 2014 09:03:39 +0100 From: _1126 To: Walter Hurry Subject: Re: [freebsd-questions] Can't upgrade /lang/ruby19 Message-ID: <20140128080339.GA4970@elfsechsundzwanzig.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) X-Df-Sender: bGlzdHNAZWxmc2VjaHN1bmR6d2FuemlnLmRl Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 08:03:48 -0000 Hi Walter! On Mon, Jan 27, 2014 at 10:44:44PM +0000, Walter Hurry wrote: > I am trying to upgrade ruby-1.9.3.484,1 to ruby-1.9.3.484_1,1 (using port= upgrade) but am getting the following compiler error on FreeBSD 10.0-RELEAS= E: >=20 > =3D=3D=3D> Building for ruby-1.9.3.484_1,1 > make[2]: don't know how to make OPENSSL_CFLAGS. Stop >=20 > Is there a workaround, or have I missed something? Apparently, it's not only lang/ruby19. See thread "weird error messages with various ports" from yesterday. The ports/some ports seems to be messed up. I don't know what happened. If you happen to use ports with svn, you could use revision 341159. This one worked for me. I did not check whether any updates to the ports tree resolved the issue, but I assume you used the latest one, so I guess it ain't resolved yet.