Date: Mon, 22 Apr 2013 23:52:14 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD ports <freebsd-ports@freebsd.org> Subject: Re: 10.0-CURRENT #0 r249720: graphics/jasper: eval: @CC@: not found Message-ID: <1366667534.1416.11.camel@thor.walstatt.dyndns.org> In-Reply-To: <9024157C-0EA0-4D3A-BC26-60B38F6E054D@FreeBSD.org> References: <1366656425.1416.8.camel@thor.walstatt.dyndns.org> <9024157C-0EA0-4D3A-BC26-60B38F6E054D@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-iJRvNbiqdaYLbI21u7HO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Mon, 2013-04-22 at 21:40 +0200, Dimitry Andric wrote: > On Apr 22, 2013, at 20:47, O. Hartmann <ohartman@zedat.fu-berlin.de> wrot= e: > > Trying to update port graphics/jasper on our FreeBSD 10.0-CURRENT boxes > > (all r249720 or higher) fails on all(!) Core2Duo based systems (Intel > > E8400 or Q6600) (CLANG 3.3) with the below shown error. > ... > > Interestingly, the port does compile on all boxes running the very same > > FreeBSD 10.0-CURRENT with either Sandy-Bridge-E (i7-3939K) or Ivy Bridg= e > > (i3-3220) CPUs. All systems have in common that I compile world and > > kernel with option -O3 (CLANG 3.3), -march=3Dnative. > ... > > I guess I hit a miscompilation with either option -O3 -march=3Dnative o= n > > "Penryn" architectures with the new CLANG 3.3 compiler? > >=20 > > (By the way, I also see this obscure "@CC@: not found" error in > > compiling games/qstat and it hits also the Core2Duo boxes, but not any > > CPU type beyond the C2D). >=20 > This is most likely the same issue you reported in another thread, here: >=20 > http://docs.freebsd.org/cgi/mid.cgi?1365877246.2093.20.camel >=20 > The configure script tries to use sed to replace @CC@ with a build-time s= etting, but the sed replacement fails, because of a problem in the regex fu= nctions in libc, when libc is compiled with -O3 or higher. The exact cause= of the problem is still unknown (likely a bug in the vectorizer, or less l= ikely a bug in libc). >=20 > Please recompile and reinstall at least your libc with -O2 instead of -O3= , and retry the ports build afterwards. You're right. After decreasing from -O3 to -O2 the "problem" on C2D machines went away. >=20 > In general, if you use non-standard optimization settings, always remove = the customizations first, before reporting problems. I should do, indeed, but isn't it interesting of the knowledge, that this happens only on Core2Duo architecure CPUs, but not on more modern designs? Regards, Oliver --=-iJRvNbiqdaYLbI21u7HO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJRdbEOAAoJEOgBcD7A/5N8oO8H/irIYQEdavxRqwp2Is7f7Z14 zJgM7OTesyw56mTDI4w/Bln4OQfWmhIQ/Os0UGI67yCzjvUTTAhf52Pmplf5X5lo Nx6u8ieZBpRzoveSQ9rFcnp3xSMbMD5psxHbfBb7SAxZ/u09qD0fRahlcvCp+QDP 9y8cRJgplkNb61I7Aftk5EKE7A86FhHAlfkDHTdAUEAcwz0oVac0sSkwVkQErczR gbHj7AdfqiS/YrfXV541cG4RrjhngKZMc3fSVpLj7xwtdPAGoJV41g1dSqaHOIjv a7NIkvPqKb2NF7b0Fmbi74yMikEtCQBdrjrkTanicoU++0hsOtjjERXCyaGDzHE= =P00u -----END PGP SIGNATURE----- --=-iJRvNbiqdaYLbI21u7HO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1366667534.1416.11.camel>