Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Mar 2011 08:26:56 -0300
From:      "Marcelo/Porks" <marcelorossi@gmail.com>
To:        Dimitry Andric <dim@freebsd.org>
Cc:        FreeBSD-current Current <freebsd-current@freebsd.org>
Subject:   Re: Can't update CLang-based system
Message-ID:  <AANLkTimAiecar4OfEh2kneeEZDz5Eub%2BEodwzVNvKs92@mail.gmail.com>
In-Reply-To: <4D6B8FCA.5050203@FreeBSD.org>
References:  <11C58791-9103-4C0E-8B35-EE46A4A6D3D4@kientzle.com> <4D6B8FCA.5050203@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 28, 2011 at 09:06, Dimitry Andric <dim@freebsd.org> wrote:
> On 2011-02-28 04:30, Tim Kientzle wrote:
>>
>> I have a FreeBSD-CURRENT AMD64 system here that was last updated at
>> r215029.
>>
>> I'm trying to update it to r219079, but the build fails in lib/libz when
>> it tries to compile gvmat64.S. =A0It looks like the Makefile here has a
>> workaround for clang on AMD64, but it doesn't seem to actually be workin=
g in
>> this case.
>
> For this to work, you must put the following fragment in /etc/make.conf,
> *not* in /etc/src.conf.
>
> .if !defined(CC) || ${CC} =3D=3D "cc"
> CC=3Dclang
> .endif
> .if !defined(CXX) || ${CXX} =3D=3D "c++"
> CXX=3Dclang++
> .endif
> # Don't die on warnings
> NO_WERROR=3D
> WERROR=3D
>
> The problem with src.conf is that is only read when make encounters a
> .include <bsd.lib.mk> or <bsd.prog.mk> statement, which usually is at
> the end of a Makefile. =A0Thus, any checks done on ${CC} or ${CXX} in the
> beginning of a Makefile pick up only the default value.

Hi. This worked for me.

Thanks for your help



--=20
Marcelo Rossi
"This e-mail is provided "AS IS" with no warranties, and confers no rights.=
"
"I have nothing against God, I just hate His fan club"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimAiecar4OfEh2kneeEZDz5Eub%2BEodwzVNvKs92>