Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 07 Dec 2011 10:02:45 +0100
From:      Stefan Esser <se@freebsd.org>
To:        dim@FreeBSD.org
Cc:        freebsd-current@freebsd.org
Subject:   Extend search range of FreeBSD-10 libtools/configure fixup (was: Re: FreeBSD 10.0-CURRENT/AMD64 (CLANG): lang/gcc46 fails to build)
Message-ID:  <4EDF2BB5.10602@freebsd.org>
In-Reply-To: <4EDF249B.8030104@FreeBSD.org>
References:  <4EDEF1FF.5020307@zedat.fu-berlin.de> <4EDF249B.8030104@FreeBSD.org>

index | next in thread | previous in thread | raw e-mail

Am 07.12.2011 09:32, schrieb Dimitry Andric:
> That said, you are most likely running into an issue with the fix for
> FreeBSD 10-CURRENT in bsd.port.mk, causing the lto-plugin stage
> configure script to fail.
> 
> This is because the gcc ports unpack their source code into
> ${WRKDIR}/gcc-${VERSIONSTRING}, and then override WRKSRC to
> ${WRKDIR}/build.  Since bsd.port.mk only applies the run-autotools-fixup
> to ${WRKSRC}, the gcc source itself is not properly fixed up.
> 
> You can try the attached patch, which fixes this (and fixes it for all
> other ports that override WKRSRC).

I had solved a similar problem for BDB a few weeks back and made the
same modification (start searching in WRKDIR instead of in WRKSRC).

This leads to (minimally) higher run time for the fixup, but it should
make a number of ports currently broken on FBSD10 automagically build
again ...

And the pattern for libtool/configure type files should sufficiently
prevent patching of files not touched by the current invocation of "find".

SO I'd vote to get that patch into SVN ...

Regards, STefan


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EDF2BB5.10602>