https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258679
--- Comment #24 from gn...@justmail.de --- (In reply to Tatsuki Makino from comment #22) > This is what happens when you build www/chromium with these settings: > The 32GB of physical memory is just barely enough. Is this about the (final) link step? A non-debug build works fine for me with $WRKDIR on a memory-backed tmpfs with an equal amount of RAM. > # du -c -h -d 0 -- `make -C /usr/ports/www/chromium/ -V WRKDIR` > 218G /mnt/tmp/ports/work/usr/ports/www/chromium/work That is enormous but then not that surpising with C++. > check-orphans may have made some mistakes by me. I don't think so. Maybe these files are gone given how fast the chromium sources change... > I'll put here the backtrace I was able to get. Those backtraces show the same callstack: first a rename is tried and if that fails a copy is done. > It can be used to determine where to patch and so on :) That information is in the patch itself, thats why I suggested to save as files/patch-zza :) (In reply to Tatsuki Makino from comment #23) > I built and installed chromium-94.0.4606.81_2 with errno == ENOTSOCK added > like the patch. > As a result, the download will no longer fail under conditions where the > download directory is cross-device with XDG_DATA_HOME directory. > Thank you. You are welcome. Good to hear that the modification fixes the issue for you as well. In the meantime I rebuilt v94 using ccache (now a "fresh" build takes only about 23 minutes ;) and I can confirm that the issue is gone. -- You are receiving this mail because: You are the assignee for the bug.
