I had to set -mfpu=neon in the CFLAGS/CXXFLAGS of /etc/makepkg.conf. This seems to be done in the PKGBUILD as well, but it's broken in some way. Otherwise, I just followed the archarm distcc wiki.
Thanks! I tried to compile chromium locally on my raspberry before and could make clang++ use the correct c++ libs. After setting up ditcc enviroment I can compile it on my main machine appearantly. Still, I am wondering why you set "-mfpu=neon" since it is set to "vfpv3-d16" in makepkg.conf by default.
I'm going off memory here, but I think that the "neon" option override is set in the prepare() function of the PGKBUILD. So if you run the prepare() and build() steps separately, then the build step will not see the altered env variables anymore.
I had run into this myself several times before...
I am experiencing the same problem as miloc reported. I also brought this up on Hexchat IRC for archlinux-arm and was told someone with arch linux arm group needs to fix chromium but the person who does that appears to be missing. Is this where we post bugs like this or should I post this somewhere else? Otherwise, I'm forced to migrate to Raspio which has yet another set of problems, beside being slow and unreliable.
Try renaming the ~/. config/chromium folder to something else. You will loose everything (bookmarks, history, addons, etc). If Chromium works like this, then you may try to recover your old user data from the renamed folder a bit at a time. avast driverjiofi.local.html