Date: Tue, 22 Apr 2014 21:30:48 +0200 From: Robert Nagy <robert@openbsd.org> To: =?iso-8859-2?Q?Ren=E9?= Ladan <rene@freebsd.org> Cc: chromium-list freebsd <freebsd-chromium@freebsd.org> Subject: Re: chromium 34.0.1847.116 gives SIGABRT at start Message-ID: <20140422193048.GA8893@bsd.hu> In-Reply-To: <5356C138.5040905@freebsd.org> References: <5356C138.5040905@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140422193048.GA8893>