From owner-freebsd-ports@FreeBSD.ORG Thu Dec 15 11:14:12 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76E861065672; Thu, 15 Dec 2011 11:14:12 +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 759DB8FC0A; Thu, 15 Dec 2011 11:14:11 +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 NAA25199; Thu, 15 Dec 2011 13:14:09 +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 1Rb9GL-0002C0-Km; Thu, 15 Dec 2011 13:14:09 +0200 Message-ID: <4EE9D680.1020507@FreeBSD.org> Date: Thu, 15 Dec 2011 13:14:08 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111206 Thunderbird/8.0 MIME-Version: 1.0 To: FreeBSD Ports , Gerald Pfeifer References: <4EE9D2F6.2090906@FreeBSD.org> In-Reply-To: <4EE9D2F6.2090906@FreeBSD.org> X-Enigmail-Version: undefined Content-Type: text/plain; charset=x-viet-vps Content-Transfer-Encoding: 7bit Cc: Subject: Re: lang/gcc on freebsd 10 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: Thu, 15 Dec 2011 11:14:12 -0000 on 15/12/2011 12:59 Andriy Gapon said the following: > > lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22 > installed during its configure step with the errors like the following in > config.log: > > configure:2978: checking for C compiler default output file name > configure:3000: /usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/xgcc > -B/usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/ > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem > /usr/local/x86_64-portbld-freebsd10.0/include -isystem > /usr/local/x86_64-portbld-freebsd10.0/sys-include -g -O2 -gtoggle > -static-libstdc++ -static-libgcc conftest.c >&5 > xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found > > It seems that the error occurs because the preceding steps create > liblto_plugin.so.0.0 file, but no liblto_plugin.so link to it. Not sure why is > that though. Maybe something about platform misdetection. > Yeah, lto-plugin/configure: freebsd* | dragonfly*) # DragonFly does not have aout. When/if they implement a new # versioning mechanism, adjust this. if test -x /usr/bin/objformat; then objformat=`/usr/bin/objformat` else case $host_os in freebsd[123]*) objformat=aout ;; *) objformat=elf ;; esac fi freebsd[123]* is it. Other configure scripts have this thing too. -- Andriy Gapon