It's possible that the latest clang patches that where committed brake chromium if NULL is not defined as nullptr. Let me test this before adding clang as dep, maybe we can get away by applying the extra clang patch on later base versions. On Jul 28, 2013 3:37 PM, "René Ladan" <[email protected]> wrote:
> On 28-07-2013 02:20, Adam McDougall wrote: > > On Sat, Jul 27, 2013 at 01:04:01PM +0100, Brad Karp wrote: > > > > Given hope by Tony's experience, I tried building Chromium 28 on my > > 9.1-RELEASE amd64 box with clang33 instead of the default 9.1R clang > (3.1). > > > > Success here, too: building with clang33 fixes the "unclickable" links > > problem I and others had when building with 9.1R's default clang. > > > > Perhaps the port maintainer might consider requiring clang33 for those > > who build with clang on 9.1R and earlier for the time being? > > > > -Brad, [email protected] > > > > After a brief test with https://scroner.com/~tony/chrome_test/ > > and nagios, I can confirm this. Thanks for the tip. > > I made trivial patch for this at > http://people.freebsd.org/~rene/patches/chromium-clang33.diff > > I think it would be good to commit this, I see similar non-clickable links. > > René > _______________________________________________ > [email protected] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "[email protected] > " > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "[email protected]"
