10.11.2011 13:01, René Ladan wrote:
2011/11/10 Volodymyr Kostyrko<[email protected]>:
2011/11/9 George Liaskos<[email protected]>:
I am not sure if the problem is with the base or chrome... I've added
René, he reported the issue with clang to me.
This can be base. I have built chrome with gcc46 with same luck, just
now it says `bad address`. Sorry, I have compiled only non-debug
version, so there's all backtrace I can give:
[snip trace]
I rebuilt all my ports this week on my laptop because of base/ports openssl
conflicts and chose base gcc as the compiler for all ports unless some port
insisted on another lang/gcc* version (including chromium). With just
CODECS and GCONF, chromium 15.0.874.106 works fine (world and
kernel are still built with clang, 9.0-rc2-amd64).
I assume you use the default versions for your ports (ok, I have
WITHOUT_NOUVEAU defined to make the binary NVidia driver work)
Regards,
René
I found the cause. google-perftools-1.8.3 works incorrectly when
compiled with clang. After recompilation with stock gcc everything works
fine.
--
Sphinx of black quartz judge my vow.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chromium
To unsubscribe, send any mail to "[email protected]"
