Date: Wed, 20 Aug 2014 13:30:58 +0200 From: =?UTF-8?Q?Ren=C3=A9_Ladan?= <r.c.ladan@gmail.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: Does www/chromium work? Message-ID: <CADL2u4hrdeFPERjukm7JzRvh6BMGc1rqRA7JdsOT2mkR=k4oLA@mail.gmail.com> In-Reply-To: <lt1r3o$bma$1@ger.gmane.org> References: <lt1r3o$bma$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2014-08-20 11:51 GMT+02:00 Ivan Voras <ivoras@freebsd.org>: > Hello, > > Since there are no binary packages (why? I don't see where the Makefile > prohibits it?), I'm still upgrading chromium by building it with > portupgrade. The package builders are catching up ... > But, it looks like the latest version is broken - it > segfaults in protobuffers: > > (gdb) bt > #0 0x000000080e26d7d2 in __dynamic_cast () from /lib/libcxxrt.so.1 > #1 0x0000000807c873c4 in > google::protobuf::Message::CheckTypeAndMergeFrom () from > /usr/local/lib/libprotobuf.so.8 > #2 0x0000000002e5ddd2 in ?? () > > Yeah, but building with the internal protobuf breaks the build on FreeBSD 8 and 9 due to rtld choosing the wrong libstdc++ (base instead the one in gcc47) Google finds a sort-of similar problem in Ubuntu: > > https://bugs.mageia.org/show_bug.cgi?id=13187#c15 > > ... which appears to be caused by using the non-bundled protobuffer > library, the same as in FreeBSD. However, simply patching Makefile to > have "use_system_protobuf=0" breaks the build, stating missing files. > > In that case you will need to add a line to not remove third_party/protobuf to the remove_bundled_libraries.py call in Makefile. This is chromium-36.0.1985.143_1 on FreeBSD 10.0-RELEASE-p1. Is anybody > running chromium? > > Yes, but as soon as you sign in the Chromium you'll hit the above error. See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192821 Rene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADL2u4hrdeFPERjukm7JzRvh6BMGc1rqRA7JdsOT2mkR=k4oLA>