From owner-freebsd-ports@FreeBSD.ORG Sat Jan 4 15:45:38 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECF76FEE for ; Sat, 4 Jan 2014 15:45:38 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C1FFF1A3C for ; Sat, 4 Jan 2014 15:45:38 +0000 (UTC) Received: from [192.168.1.108] (c-174-61-88-207.hsd1.fl.comcast.net [174.61.88.207]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id A5374435AC; Sat, 4 Jan 2014 09:45:26 -0600 (CST) Message-ID: <52C82C86.9060603@marino.st> Date: Sat, 04 Jan 2014 16:45:10 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-ports@freebsd.org, "mbeis@xs4all.nl >> Marco Beishuizen" Subject: Re: how to install ruby18 References: <52C81A22.5030501@marino.st> <52C81E78.4020209@marino.st> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2014 15:45:39 -0000 On 1/4/2014 16:33, Marco Beishuizen wrote: > On Sat, 4 Jan 2014, the wise John Marino wrote: > >> Ruby18 is gone forever, and unsupported, so that's not the best option. >> DragonFly had these same type errors with ruby19, until we redefined >> GEM_ENV in bsd.ruby.mk >> >> -GEM_ENV?= LC_CTYPE=UTF-8 >> +GEM_ENV+= LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 >> >> Maybe setting GEM_ENV in your make.conf and rebuilding all the ruby >> stuff would fix it for you too. Shot in the dark. > > Tried both changing /usr/ports/Mk/bsd.ruby.mk and setting GEM_ENV in > make.conf and rebuilding the ruby stuff, but this had no effect. > > Thanks for the tip anyway. I suspect Mat's comment was closer to the problem, "That error may come from a non us-ascii character in portupgrade's configuration files." My fix was build-time, but you can build it, so it was a different issue. Try following Mat's tip. John