Date: Thu, 15 Dec 2011 13:14:08 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: FreeBSD Ports <ports@FreeBSD.org>, Gerald Pfeifer <gerald@FreeBSD.org> Subject: Re: lang/gcc on freebsd 10 Message-ID: <4EE9D680.1020507@FreeBSD.org> In-Reply-To: <4EE9D2F6.2090906@FreeBSD.org> References: <4EE9D2F6.2090906@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EE9D680.1020507>