chromium 34.0.1847.116 gives SIGABRT at start

[Robert Nagy]

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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium
> To unsubscribe, send any mail to "freebsd-chromium-unsubscribe at freebsd.org"
>