From owner-freebsd-chromium@FreeBSD.ORG Tue Apr 22 19:45:13 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 0AF0F6BD; Tue, 22 Apr 2014 19:45:13 +0000 (UTC) Received: from x2100.humppa.hu (x2100.humppa.hu [84.2.34.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nerd.hu", Issuer "nerd.hu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E126131A; Tue, 22 Apr 2014 19:45:12 +0000 (UTC) Received: from x2100.humppa.hu (localhost [127.0.0.1]) by x2100.humppa.hu (8.14.8/8.14.3) with ESMTP id s3MJUpPl000427 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 Apr 2014 21:30:51 +0200 (CEST) Received: (from robert@localhost) by x2100.humppa.hu (8.14.8/8.14.3/Submit) id s3MJUnFg004056; Tue, 22 Apr 2014 21:30:49 +0200 (CEST) X-Authentication-Warning: x2100.humppa.hu: robert set sender to robert@openbsd.org using -f Date: Tue, 22 Apr 2014 21:30:48 +0200 From: Robert Nagy To: =?iso-8859-2?Q?Ren=E9?= Ladan Subject: Re: chromium 34.0.1847.116 gives SIGABRT at start Message-ID: <20140422193048.GA8893@bsd.hu> References: <5356C138.5040905@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5356C138.5040905@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: chromium-list freebsd X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 19:45:13 -0000 Hey, Try this: build/common.gypi: @@ -1322,7 +1322,7 @@ # TODO(jungshik): Turn this on on Android. # For ChromeOS, this should be turned on in chromeos-chrome.ebuild # file as well by adding icu_use_data_file_flag=1 to BUILD_DEFINES. - ['OS!="android"', { + ['OS!="android" and os_bsd!=1', { 'icu_use_data_file_flag%': 1, }], ], On (2014-04-22 21:21), René Ladan wrote: > Hi, > > I ported chromium 34.0.1847.116 to FreeBSD (patches at [1]) but it > currently gives a SIGABRT when starting it without any visible output. > > Building a debug version does not make a difference either. > > This is on FreeBSD 10.0-STABLE, GENERIC amd64 kernel. > > Does anyone see something obviously wrong with the patches that could > result in a SIGABRT ? > > [1] https://github.com/gliaskos/freebsd-chromium/tree/master/www/chromium > > Regards, > René > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org" >