Date: Mon, 01 Sep 2014 01:41:44 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 192685] www/chromium 36.0.1985.143 fails to build on 10-stable Message-ID: <bug-192685-28929-tKAzi8Rf72@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192685-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-192685-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192685 --- Comment #31 from bkarp@cs.ucl.ac.uk --- Problem with missing type names in the v8 namespace solved. To the maintainers: The chromium port incorrectly picks up the include files in /usr/local/include from any v8 package installation present on the system during build. At the moment, the version of v8 installed by the FreeBSD port/package is different than (older than, one presumes?) the version of v8 included in the chromium 37 sources. After removing my v8 package, I was able to do a "stock" build of the current chromium 37 port on my 10.0-RELEASE p7 box. The fix would seem to be to tweak the -I arguments to the chromium port build to prefer the v8 include files within the chromium build tree to those installed in /usr/local (and analogous changes for libraries?). FWIW, I'd imagine this build breakage may affect others who have v8 installed. So a fix might save others from needing to build chromium in poudriere... -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192685-28929-tKAzi8Rf72>