From owner-freebsd-chromium@FreeBSD.ORG Tue May 27 21:54:08 2014 Return-Path: Delivered-To: freebsd-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 ESMTPS id 0B8B523F for ; Tue, 27 May 2014 21:54:08 +0000 (UTC) Received: from smtp4.cc.ksu.edu (smtp4.cc.ksu.edu [129.130.255.116]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFC462A2B for ; Tue, 27 May 2014 21:54:07 +0000 (UTC) Received: from mew.cns.ksu.edu (mew.cns.ksu.edu [129.130.0.181]) by smtp4.cc.ksu.edu (8.14.3/8.14.3) with ESMTP id s4RLiNci029002 for ; Tue, 27 May 2014 16:44:24 -0500 (CDT) Message-ID: <53850736.7020300@ksu.edu> Date: Tue, 27 May 2014 16:44:22 -0500 From: "Lawrence K. Chen, P.Eng." Organization: Kansas State University - ITS/Enterprise Server Technologies User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-chromium@freebsd.org Subject: Chromium after 33? X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.3 at cts-virus4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.72 on 129.130.255.117 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2014 21:54:08 -0000 So, what do I need to do, to have chromium working again? I'm starting to go through withdrawal of the things I can't do using Opera (nuked Firefox after I got it customized the way I liked again and it goes and trashes my profile again...something about changes to how it sync's) Originally with the various 34's and the recent 35....it would just quietly vanish....segv. I tried rebuilding libexecinfo.so, no help. I then tried rebuilding everything it depended on....hope that doesn't break anything else. Though probably wasn't necessary, not everything chooses to use gcc for their compile. But, wondered if the change of default GCC from 4.6 to 4.7 was the problem....not sure I want to rebuild everything....though I was surprised that it churned through them all with only the occasional problem port. It re-installed 249 ports, installed 32 (I have portmaster set to delete build-only ports when its done.) My home system has 2027 ports installed currently. (it takes number 1 :p work system has 1567, headless server 1 has 413 and headless server 2 has 566) Thought at one time there was something about clang vs gcc in getting chromium to work. Or perhaps it was a different port. But, it seems set on using gcc 4.7.3. Even though I though clang is supposed to be the preferred compiler now, also have it set as my FAVORITE_COMPILER in /etc/make.conf... I know I once set "DISABLE_MAKE_JOBS= YES" for it in make.conf (apparently, I have DISABLE_VULNERABILIES set for it :) -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Sr. Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally