Summary: | dev-util/trace-cmd-2.8 Parallel building fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Phil <Phil> |
Component: | Current packages | Assignee: | Patrick McLean <chutzpah> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 351559 | ||
Attachments: |
/var/tmp/portage/dev-util/trace-cmd-2.8/temp/build.log
trace-cmd-2.8.2-r1-split-build.patch |
Description
Phil
2019-07-18 14:25:04 UTC
Created attachment 583392 [details]
/var/tmp/portage/dev-util/trace-cmd-2.8/temp/build.log
Created attachment 584462 [details, diff]
trace-cmd-2.8.2-r1-split-build.patch
I am having trouble reproducing this on my workstation. Does this patch help?
Hi Patrick, (In reply to Patrick McLean from comment #2) > Created attachment 584462 [details, diff] [details, diff] > trace-cmd-2.8.2-r1-split-build.patch > > I am having trouble reproducing this on my workstation. Does this patch help? Sadly not, I'm still getting the "file truncated" error. Here's a minimal reproducer: CFLAGS="-pipe" make -j5 NO_UDIS86=1 VERBOSE=1 trace-cmd libs Seems the combination of -pipe and specifying the inter-dependent targets 'trace-cmd' and 'libs' when calling make does the trick. I'm not sure whether requesting to build trace-cmd and libs in parallel is a good idea: trace-cmd requires LIBTRACECMD_STATIC which causes make sub-process call in lib/trace-cmd to build libtracecmd.a. OTOH, libs requires LIBTRACECMD_SHARED which causes a similar make sub-process to build libtracecmd.so. Meanwhile I'll remove -pipe from my CFLAGS - my /var/tmp/portage is a tmpfs with 17GB max size, so despite its questionable relevance in modern systems I'll probably not see any of the expected downsides when omitting it. Cheers, Phil compile hangs for -j1 too Toralf, wrong bug? This is not about a hang, but parallel build failure. I can't reproduce this problem at 3.1.5, so will close as obsolete. please try again, and re-open if you still have problem. |