Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35662 - [ruby-gtk2] make install needs to be run as -j1
Attached to Project:
Community Packages
Opened by Kevin Mihelich (kmihelich) - Wednesday, 05 June 2013, 18:08 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 09 June 2013, 16:02 GMT
Opened by Kevin Mihelich (kmihelich) - Wednesday, 05 June 2013, 18:08 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 09 June 2013, 16:02 GMT
|
DetailsDescription: The make install's for the packages run into a race condition with jobs > 1, causing them to sometimes package, but usually not. Explicitly setting -j1 for the make install lines for each package() solves the problem and the packages build successfully every time.
This also affects ruby-gtk3, though I'm only submitting one bug since it's the same maintainer and it's an identical issue/solution. Additional info: * package version: all * log: ==> Starting package_ruby-glib2()... (cd ext/glib2 && make install) make[1]: Entering directory `/build/src/ruby-gtk2-2.0.2/glib2/ext/glib2' /usr/bin/install -c -m 644 /build/src/ruby-gtk2-2.0.2/glib2/ext/glib2/rbglib.h /build/pkg/ruby-glib2//usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux /usr/bin/install: cannot create regular file '/build/pkg/ruby-glib2//usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux': No such file or directory make[1]: *** [install-headers] Error 1 Steps to reproduce: Build with MAKEFLAGS set with -j2 or higher (in a clean chroot ;) |
This task depends upon
Comment by Alexander F. Rødseth (xyproto) -
Sunday, 09 June 2013, 16:02 GMT
Thanks for reporting. Fixed in SVN, but postponing the release of the package. Please reopen if releasing the packages as well would be benficial.