Arch Linux

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!
Tasklist

FS#8626 - r 2.6.0-1 makepkg build error with MAKEFLAGS="-j2"

Attached to Project: Arch Linux
Opened by David Scholl (djscholl) - Monday, 12 November 2007, 20:12 GMT
Last edited by Greg (dolby) - Tuesday, 17 June 2008, 19:27 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Damir Perisa (damir.perisa)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Current PKGBUILD fails with build error "mkdir: cannot create directory `/home/dscholl/devel/abs/r/pkg//usr/share/R/docs//html': file exists".
Would maintainer consider adding "options=('!makeflags')" to PKGBUILD for users who build their own packages, to help the subset who have SMP hardware and use "-j2" by default?


Steps to reproduce:
Only tested on i686. Build r 2.6.0-1 via "makepkg" on dual-processor dual-core Xeon with MAKEFLAGS="-j2". If "options=('!makeflags')" is added to PKGBUILD, build error does not occur. I suspect this is a race condition, so it may be tricky to reproduce on other hardware. It is reproducible on my system.
This task depends upon

Closed by  Greg (dolby)
Tuesday, 17 June 2008, 19:27 GMT
Reason for closing:  Won't fix
Comment by Greg (dolby) - Monday, 05 May 2008, 21:57 GMT
IMO PKGBUILDs should work with the default makepkg.conf. If users make changes to it its their responsibility to keep the PKGBUILD working.
Comment by Allan McRae (Allan) - Tuesday, 06 May 2008, 08:38 GMT
Well, I see this as not a bug, but does this still happen with r-2.7.0?
Comment by David Scholl (djscholl) - Wednesday, 07 May 2008, 12:54 GMT
Sorry, I cannot test for this issue with r-2.7.0. Unhappily, I had to replace Arch with OpenSuSE on that dual-dual Xeon machine at work. The reason I was building r was to set the "--enable-R-shlib" config switch needed for my python-rpy package. This switch is set in the r-2.7.0 Arch binary, so python-rpy users like myself no longer need to build a customized r. I just thought that "options=('!makeflags')" would make the r PKGBUILD work for a broader user base, including those with the default makepkg.conf.
Comment by Gavin Bisesi (Daenyth) - Wednesday, 04 June 2008, 18:13 GMT
Should this be closed?

Loading...