From owner-freebsd-chromium@FreeBSD.ORG Fri Sep 12 21:49:34 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4687EFFA for ; Fri, 12 Sep 2014 21:49:34 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (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 1F4E2DF5 for ; Fri, 12 Sep 2014 21:49:33 +0000 (UTC) Received: from mew.cns.ksu.edu ([129.130.0.181]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from ) id 1XSYii-000FCt-PD for freebsd-chromium@freebsd.org; Fri, 12 Sep 2014 21:49:32 +0000 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 129.130.0.181 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18Am/d55zPRLj4KJv8viqj1cCU+9fplPLI= Message-ID: <54136669.6040700@tardisi.com> Date: Fri, 12 Sep 2014 16:32:25 -0500 From: The BSD Dreamer User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: freebsd-chromium@freebsd.org Subject: Chromium 37.0.2062.120 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 21:49:34 -0000 So, I was finally able to upgrade for 35.0.1916.153_3.... to 37.0.2062.94. This seem to be working, except for the extra windows stuff (toggle the setting and it goes away, but close window and reopen...and its back...) But, then I update to 37.0.2062.120...and chrome just exits. Not sure though if the lang/gcc upgrade to 4.8 is involved or not. The update all the other bumped ports is still in progress. During the update, chromium did stop working....but changing rpath from /usr/local/lib/gcc47 to /usr/local/lib/gcc48 fixed that. Had only upgraded my work machine....it was actually by accident.... different hosts get a different set of '-x' switches with portmaster..'-a' (mostly ports that require interaction to get things to update correctly....like cacti or backuppc) Perhaps when I get caught up, I'll look to see why my poudriere setup at home is broken again. Though probably need to take care of a bad drive first. I had built 'devel/chrpath' a while back for the rpath problem...though I also have a section in the post half of bsd.local.mk to remove and re-add the options in better order if both USE_OPENSSL & USE_GCC are defined... For the port I had 'referenced'....I changed the port from .include .if ${PORT_OPTIONS:MKNOB} LDFLAGS+= -Wl,-rpath... .endif to KNOB_LDFLAGS= -Wl,-rpath.... Because bsd.options.mk is included before bsd.openssl.mk ;) -- Email: beastie@tardisi.com Name: Lawrence "The Dreamer" Chen GitHub: https://github.com/TheDreamer Pages: http://beastie.tardisi.com Blog: http://lawrencechen.net WWW: http://tardisi.com