From owner-freebsd-ruby@FreeBSD.ORG Mon Feb 11 08:17:28 2013 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D2BC6BFD for ; Mon, 11 Feb 2013 08:17:28 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0CDEECC1 for ; Mon, 11 Feb 2013 08:17:27 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA06315; Mon, 11 Feb 2013 10:17:06 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1U4oZV-000Fwz-RG; Mon, 11 Feb 2013 10:17:05 +0200 Message-ID: <5118A8FF.4070007@FreeBSD.org> Date: Mon, 11 Feb 2013 10:17:03 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: Steve Wills Subject: Re: ruby-1.9.pc; strange/harmful entry References: <510FD6A0.2010303@FreeBSD.org> <5117FB5E.1000502@mouf.net> <51181185.1080802@FreeBSD.org> <5118488D.3080706@FreeBSD.org> <51186D35.8080207@mouf.net> In-Reply-To: <51186D35.8080207@mouf.net> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ruby@FreeBSD.org X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 08:17:28 -0000 on 11/02/2013 06:01 Steve Wills said the following: > The more I look at it, the more I think this may be a bug in Ruby or > configure. the file is generated by config.status like so: > > ./config.status --file=ruby-1.9.pc:./template/ruby.pc.in > > Try the attached patch, also available here: > > http://meatwad.mouf.net/~swills/ruby_pc.diff.txt > > It builds, but otherwise it's untested. Should be harmless. Let me know > if this fixes it for you and I'll get added on the next update to the port. >From a quick look at configure.in I see that there is a special case for freebsd | dragonflybsd: [freebsd*|dragonfly*], [ ... DLDFLAGS="$DLDFLAGS "'-Wl,-soname,$(.TARGET)' I think that this assignment should be removed. That's the only occurrence of -Wl,-soname in DLDFLAGS in the whole script. Possibly we should do instead what is done for netbsd elsewhere in the script: [netbsd*], [ ... LIBRUBY_DLDFLAGS='-Wl,-soname,lib$(RUBY_SO_NAME).so.$(MAJOR)$(MINOR)' In freebsd/dragonfly block (preceding the netbsd one) this could be written more compactly as: LIBRUBY_DLDFLAGS='-Wl,-soname,$(LIBRUBY_SO)' -- Andriy Gapon