From owner-freebsd-amd64@FreeBSD.ORG  Sat Oct  4 22:30:55 2008
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 78B561065698
	for <freebsd-amd64@freebsd.org>; Sat,  4 Oct 2008 22:30:55 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from parsely.rain.com (parsely.rain.com [199.26.172.196])
	by mx1.freebsd.org (Postfix) with ESMTP id CF5C88FC14
	for <freebsd-amd64@freebsd.org>; Sat,  4 Oct 2008 22:30:54 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com (uucp@localhost)
	by parsely.rain.com (8.11.4/8.11.4) with UUCP id m94MUnl90867
	for freebsd-amd64@freebsd.org; Sat, 4 Oct 2008 15:30:49 -0700 (PDT)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id WAA04290; Sat, 4 Oct 2008 22:26:04 GMT
Message-Id: <200810042226.WAA04290@sopwith.solgatos.com>
To: freebsd-amd64@freebsd.org
In-reply-to: Your message of "Fri, 26 Sep 2008 20:10:18 +0300."
	<20080926171018.GX47828@deviant.kiev.zoral.com.ua> 
Date: Sat, 04 Oct 2008 15:26:04 +0100
From: Dieter <freebsd@sopwith.solgatos.com>
Subject: Re: amd64/127640: GCC will not build shared libraries with
	-fprofile-generate on amd64 
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Oct 2008 22:30:55 -0000

Kostik writes:
> > > Note that libgcov needs to be recompiled with -fPIC.
> > > The R_X86_64_32 issue is systematic on amd64. When you build a shared
> > > object, better make sure that all .o are compiled with -fPIC.

> Should /usr/lib/libgcov.a be built with -fPIC, is debatable. I think it
> is overkill for most other static libs from /usr/lib.

I don't know what the pros and cons of -fPIC are, is there a case
for libs with and without it?

Having ports not build isn't acceptable.  AMD64 isn't some rare and exotic
architecture.

> Note that there
> are reasonable arguments against supplying static system libraries like
> libc and libpthread.

There are?  I can't think of any.

Mark writes:
>> Ports should compile cleanly out of the box, on all archs, with no problems.
>
> A noble goal, but we are a long way from it, and rely on volunteers
> to take maintainership of individual ports to make it happen.

Does "tinderbox" build ports?  Finding the problems as they are created
should help a lot.