From owner-freebsd-ports@FreeBSD.ORG Wed Dec 5 01:40:27 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 D02E016A417 for ; Wed, 5 Dec 2007 01:40:27 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from tiamat.relinetworks.com (tiamat.relinetworks.com [204.214.92.162]) by mx1.freebsd.org (Postfix) with ESMTP id 8CDAC13C45B for ; Wed, 5 Dec 2007 01:40:27 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (root@r74-193-170-223.bssrcmta01.bscyla.by.dh.suddenlink.net [74.193.170.223] (may be forged)) by tiamat.relinetworks.com (8.14.1/8.14.1) with ESMTP id lB51eQEn068664; Tue, 4 Dec 2007 20:40:26 -0500 (EST) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.2/8.14.2) with ESMTP id lB51ePSF093450; Tue, 4 Dec 2007 19:40:25 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Tue, 4 Dec 2007 19:40:25 -0600 (CST) From: Wes Morgan To: David Wood In-Reply-To: Message-ID: References: User-Agent: Alpine 0.99999 (BSF 796 2007-11-08) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ade@freebsd.org, Sean McNeil , FreeBSD Ports mailing list Subject: Re: net/freeradius - fixed for RELENG_7 amd64 and 6.x with gcc 4.2 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: Wed, 05 Dec 2007 01:40:27 -0000 On Tue, 4 Dec 2007, David Wood wrote: > (ade@ cc'd as maintainer of devel/libtool) > > Dear all, > > I posted previously on the ports mailing list about problems that were > showing up with net/freeradius when built with gcc 4.2 on 6.x and on 7.x > amd64. > > At that time I was wondering if there was an arcane problem in the toolchain, > maybe in libtool. In fact, the solution appears to be straightforward, and > not libtool's fault. radiusd was being built -pie, which was the default from > upstream. Patching the upstream Makefile.in to remove -pie seems to resolve > both problems. Thanks to Sean McNeil for the report. > > > The moral of the story appears to be "don't use -pie with libtool". I have no > idea why the upstream Makefile.in is like this; I will chase it with the > FreeRADIUS developers. > > > I've just submitted ports/118425 > http://www.freebsd.org/cgi/query-pr.cgi?pr=118425 > which should fix that, as well as chasing a heimdal shared library version > bump. > > > I believe those two fixes may qualify for committing during the current ports > freeze; I've alerted portmgr@ separately. > > I've also incorporated a couple of other outstanding fixes, though I realise > that they may well not qualify to be committed alongside the others because > of the ports freeze. HMMMM... A seemingly silimar issue came up a while back. It was supposed to have been fixed - http://lists.freebsd.org/pipermail/cvs-src/2007-May/078660.html I wonder if perhaps there is something more that needs to be done.