Date: Sat, 26 May 2012 21:02:30 +0200 From: Mel Flynn <rflynn@acsalaska.net> To: Oliver Pinter <oliver.pntr@gmail.com> Cc: ports@freebsd.org, x11@freebsd.org Subject: Re: libX11 and clang: compile error Message-ID: <4FC128C6.1020902@acsalaska.net> In-Reply-To: <CAPjTQNEvV_%2BVT2iE_1EHDdR_nciMc1yWLFGnDKyqd6nu-wek2Q@mail.gmail.com> References: <CAPjTQNHCHCPNm=6%2BinkDmbnj4%2BW1kdcXkwFxS8LURj3kqWPDmg@mail.gmail.com> <4FC1082A.9090801@acsalaska.net> <CAPjTQNG-8mosRuun-u%2BWHVVAu_VydDhdLekrQ8hOEQ%2BPML-3Zg@mail.gmail.com> <4FC112A1.7080600@acsalaska.net> <CAPjTQNEvV_%2BVT2iE_1EHDdR_nciMc1yWLFGnDKyqd6nu-wek2Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26-5-2012 20:40, Oliver Pinter wrote: > On 5/26/12, Mel Flynn <rflynn@acsalaska.net> wrote: >> On 26-5-2012 19:17, Oliver Pinter wrote: >>> I think src.conf is relevant, while it changes the system behavior, as >>> changed the default cc from gcc-4.2 to clang. >> >> Thinking it doesn't make it so. Run: >> grep _WITHOUT_SRCCONF /usr/share/mk/*.mk >> >> Then investigate. >> Setting CC in /etc/src.conf has *no effect on CC passed to the ports*. >> Really. It does not. >> The file that can do that is /etc/make.conf. >> Another way is setting CC in your environment variables, through >> /etc/login.conf, /etc/yourshellrc ~/.profile ~/.[cz]?shrc and what not. >> >> In order to debug your issue, you should provide the output of what make >> thinks CC and CPP are and backtrack where they are set. >> Start with: >> make -C /usr/ports/x11/libX11 -V CC -V CPP >> -- >> Mel >> > > After setting WITH_CLANG_IS_CC in src.conf the base system cc,cpp and > c++ has changed: See ports/166373. Also, the fact that your /usr/bin/cpp == clang-cpp is relevant! Especially if you report: > Somewhere in config* or Makefile are a hardcoded /usr/bin/cpp ... -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FC128C6.1020902>