[Bug 263068] KDE ports fail to build without showing why

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon May 2 19:44:21 BST 2022


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263068

Adriaan de Groot <adridg at freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |In Progress

--- Comment #3 from Adriaan de Groot <adridg at freebsd.org> ---
Since this is an affects-only-you thing, it's up to you to move this forward.
We either need a way to reproduce this -- I can build this particular port just
fine, and poudriere is grinding through 504 ports today doing the same -- or an
indication from your machine what's wrong.

- permissions?
- any interesting messages in /var/log/mmessages, /var/log/auth, dmesg
- unusual security settings, permissions in wrkdirs, umask
- repeatable locally? what if you cd into the build dir and run ninja by hand
there (after the first failure). can you strace ninja? how about inserting a
shell-script called /usr/local/bin/ninja (move the binary out of the way) so
you can be more verbose? How about setting ninja flags -- through such a
wrapper -- to log more?

Without more information this could be a bad SSD in your system, or a full ZFS
filesystem, or just about anything else.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the kde-freebsd mailing list