Date: Fri, 28 Sep 2012 18:41:56 -0800 From: Jan Beich <jbeich@tormail.org> To: obrien@FreeBSD.org Cc: freebsd-ports-bugs@freebsd.org, bug-followup@FreeBSD.org Subject: Re: [patch] vietnamese/libviet: respect CC/CFLAGS Message-ID: <1THn6C-000EaU-DD@internal.tormail.org> In-Reply-To: obrien@freebsd.org's message of "Fri Sep 28 23\:39\:33 UTC 2012"
next in thread | raw e-mail | index | archive | help
obrien@FreeBSD.org writes: > State-Changed-From-To: open->closed > State-Changed-By: obrien > State-Changed-When: Fri Sep 28 23:39:33 UTC 2012 > State-Changed-Why: > This seems fixed to me. Exactly when? I can still reproduce. If you're referring to clang -exp runs see last comment in ports/159117. Leaving aside the issue of portmgr@ embracing false positives # notice 'cc' is used with no clang-specific warnings (then 'cc' is 'gcc') # notice '-O2 -pipe -fno-strict-aliasing' are not actually used http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-errorlogs/a.9-exp-clang.20120902011351.pointyhat-west/vi-libviet-20010210_1.log.bz2 So, try USE_GCC=4.6+ and see if the log contains gcc46 or set CC yourself but place a few traps to prevent build from lying (see quote below). > >Environment: > # slightly different from pointyhat > $ export PATH=~/.bin:$PATH > $ for cc in CC cc c++ gcc g++ cpp; do ln -s /usr/bin/false ~/.bin/${cc}; done Note, assignment on command line has higher precedence than in Makefile. For example, the following $ make CC=gcc46 overrides CC=cc in lib/viqr/Makefile but fails to work when CC is set via environment, make.conf or bsd.gcc.mk (USE_GCC).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1THn6C-000EaU-DD>