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

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon May 2 20:52:11 BST 2022


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

--- Comment #4 from Friedrich Volkmann <bsd at volki.at> ---
If I knew what's wrong, I would have already solved it.

- permissions: What permissions are you talking about? The work directory is
autocreated, I don't set any permissions there.

- messages: Yes, /var/log/messages and dmesg report:
pid 71848 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)
pid 71852 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)
pid 71849 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)
pid 71853 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)
pid 71862 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)
pid 71851 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)
pid 71850 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)
pid 71964 (meinproc5), jid 0, uid 0: exited on signal 11 (core dumped)

- unusual security settings, permissions in wrkdirs, umask: None that I'm aware
of. They would certainly cause problems in non-KDE ports as well.

- repeatable locally: Yes.

- [ninja hacking]: I'm not a ninja, let alone a ninja programmer. I don't even
know what Ninja is doing and why it is needed. Maybe I'll dig into it when I
have more time and I'm in better health.

- bad SSD: No, I have no SSD, only conventional hard drives. No signs of
mechanical defects, such as click sounds.

- full ZFS filesystem: No, I only have UFS. Tens of GB free in /usr and /var
(where tmp is also located).

- Just about anything else: Please be more specific. I can't send you my entire
computer. I need it myself, and the mail carrier would certainly damage the
hard disks. They are not shock proof.

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


More information about the kde-freebsd mailing list