Summary: | app-admin/mcelog-198:0 -- ‘cputype’ has an incomplete type ‘enum cputype’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gary E. Miller <gem> |
Component: | Current packages | Assignee: | Ben Kohler <bkohler> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | amonakov+bugs.gentoo, bkohler, gem |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=855392 https://bugs.gentoo.org/show_bug.cgi?id=701878 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 351559 | ||
Attachments: |
build log
build log |
Description
Gary E. Miller
2024-03-29 21:25:48 UTC
Created attachment 889023 [details]
build log
build log
I'm a bit confused, you seem to be the only person I've seen who has any problems compiling mcelog. Does MAKEOPTS="-j1" work for this build failure? > I'm a bit confused, you seem to be the only person I've seen who has any problems compiling mcelog. No, I'm the only Gentoo user that took the time to report the issue. Most mcelog users gave up on it a long time ago. > Does MAKEOPTS="-j1" work for this build failure? No. I'll upload a new build log with -j1 Created attachment 893191 [details]
build log
new build log with -j1
Can you open an issue upstream? I do not know how to fix this. This can happen if /var/tmp/portage is on a filesystem with low-resolution timestamps. I can reproduce it on an ext4 with 128-byte inodes (which drops timestamp resolution from nanoseconds to seconds): truncate -s 64M ext4-i128 mkfs.ext4 -I 128 ext4-i128 mount -o loop ext4-i128 /var/tmp/portage |