From owner-freebsd-ports@FreeBSD.ORG Tue Dec 4 16:25:07 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 A457316A468; Tue, 4 Dec 2007 16:25:07 +0000 (UTC) (envelope-from david@wood2.org.uk) Received: from sh-spam-4.gradwell.net (sh-spam-4.gradwell.net [193.84.87.110]) by mx1.freebsd.org (Postfix) with ESMTP id EC16B13C4E1; Tue, 4 Dec 2007 16:25:06 +0000 (UTC) (envelope-from david@wood2.org.uk) Received: from argon.wood2.org.uk ([82.71.104.124] country=GB ident=postmaster$pop3$wood2#org^uk) by sh-spam-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.264) id 475575af.5920.136; Tue, 4 Dec 2007 15:43:43 +0000 (envelope-sender ) Message-ID: Date: Tue, 4 Dec 2007 15:42:19 +0000 To: FreeBSD Ports mailing list From: David Wood References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain;charset=us-ascii;format=flowed User-Agent: Turnpike/6.06-M (<+vqRurpy5oJKIwOHzGcZxw$FYE>) Cc: Sean McNeil , ade@freebsd.org Subject: 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: Tue, 04 Dec 2007 16:25:07 -0000 (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. Best wishes, David -- David Wood david@wood2.org.uk