Package Details: cube-perf 4.3.5-1

Git Clone URL: (read-only, click to copy)
Package Base: cube-perf
Description: Performance report explorer for displaying a multi-dimensional performance space.
Upstream URL:
Licenses: BSD
Submitter: jspencer
Maintainer: jspencer
Last Packager: jspencer
Votes: 2
Popularity: 0.000000
First Submitted: 2015-02-17 16:23
Last Updated: 2017-06-06 21:18

Latest Comments

jspencer commented on 2015-03-18 13:13

The simplest explanation for the install error is if make genuinely hadn't created the directory at that point (after you checked you could do so by hand).

Given (from your snippet) make knew it had to do so, make just hadn't run (or completed) mkdir when the install command ran.

The easiest way for make to hit such a run condition is with parallel builds and an incomplete dependency list.

I had a quick glance at the makefile and didn't spot an explicit dependency on the directory creation target, so thought it was worth a guess.

Of course, it helps to have hit this before. It took longer the first time...

I'll update the PKGBUILD later.

valandil commented on 2015-03-18 12:53

Wow, impressive catch, jspencer! I removed the "-j4" flag from my makepkg.conf, and it installed fine. How did you get that? I never would have guessed that from the failure of install, of all things.

Could you add a "-j1" flag to the PKGBUILD so that doesn't happen to anybody else?


jspencer commented on 2015-03-18 08:50

Sorry, you're right: it does look to be the install command.

Stab in the dark: are you compiling in parallel? What are your MAKEFLAGS in /etc/makepkg.conf? If you're building in parallel, you might be running into a race condition in the makefile due to a missing dependency.

valandil commented on 2015-03-18 02:53

That's the weird part. Running mkdir myself works perfectly. And it's not the mkdir command failing, I think it's the install one. I'm building this on my ~/build/ directory, to which I have write permissions, and it has ~40GB left.

I'll report when I fix this.

jspencer commented on 2015-03-17 23:48

How odd. I do not get this. I just tried a clean build to check and it worked without a problem. The mkdir command failing implies it's something to do with your system (at least, to me). Are you sure you have the right permissions/enough space/etc? Building cube needs around 200MB of space. What happens if you run

$ mkdir -p /home/valandil/build/cube-perf/pkg/cube-perf/usr/libexec/cube

yourself? That might be a good way of tracking it down...

valandil commented on 2015-03-17 19:38

I get this weird error when trying to compile:

test -z "/usr/bin" || /usr/bin/mkdir -p "/home/valandil/build/cube-perf/pkg/cube-perf/usr/bin"
/usr/bin/install -c ../bin/cube-config-backend /home/valandil/build/cube-perf/pkg/cube-perf/usr/bin/
test -z "/usr/libexec/cube" || /usr/bin/mkdir -p "/home/valandil/build/cube-perf/pkg/cube-perf/usr/libexec/cube"
/usr/bin/install: target ‘/home/valandil/build/cube-perf/pkg/cube-perf/usr/bin/’ is not a directory: No such file or directory
Makefile:11542: recipe for target 'install-exec-local' failed

Do you see something similar?