From owner-freebsd-chromium@FreeBSD.ORG Sun Jul 28 00:27:15 2013 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 36867B93 for ; Sun, 28 Jul 2013 00:27:15 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id 0B8402A35 for ; Sun, 28 Jul 2013 00:27:14 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id E97752BBAD; Sat, 27 Jul 2013 20:20:26 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqC63U9VHaGO; Sat, 27 Jul 2013 20:20:26 -0400 (EDT) Received: from daemon.localdomain (daemon.egr.msu.edu [35.9.44.65]) by mail.egr.msu.edu (Postfix) with ESMTP id C05032BBA8; Sat, 27 Jul 2013 20:20:22 -0400 (EDT) Received: by daemon.localdomain (Postfix, from userid 21281) id 9B1B413FDDC; Sat, 27 Jul 2013 20:20:22 -0400 (EDT) Date: Sat, 27 Jul 2013 20:20:22 -0400 From: Adam McDougall To: Brad Karp Subject: Re: compiling Chromium 28 with clang33 fixes "unclickable" links Message-ID: <20130728002022.GS81600@egr.msu.edu> References: <51F3B731.7090608@cs.ucl.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51F3B731.7090608@cs.ucl.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "chromium@freebsd.org" X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jul 2013 00:27:15 -0000 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, bkarp@cs.ucl.ac.uk After a brief test with https://scroner.com/~tony/chrome_test/ and nagios, I can confirm this. Thanks for the tip.