On 11/11/10 23:28, Jeremy Evans wrote:
On Thu, Nov 11, 2010 at 4:21 PM, STeve Andre'<and...@msu.edu> wrote:
I'm having problems compiling ruby ports--below is an example of ruby-
actionpack, but this affects lots of other ruby ports.
If I stop a bulk build and clean out /var/db/pkg with pkg_delete, I find
things remaining in /usr/local/lib, like ruby. if I remove that the restart
the build things work till the next collision happens.
Clues as to what I've messed up? It's been a while since I've not
been able to figure out what went wrong in a bulk build. Let the
whacks commence...!
I experienced something similar to this at p2k10 when building using
dpb on a fast 8 core amd64 with a -P file argument that only contained
ruby ports. I was never able to replicate it using dpb on my personal
build boxes (a slower 1 core amd64 and 2 core i386), and wasn't able
to reproduce the problem without dpb after repeated attempts on the 8
core machine.
Also, are you building with USE_SYSTRACE=Yes, and are you building as
root or as a normal user with SUDO set? I set USE_SYSTRACE=Yes and
build as a normal user with SUDO on my personal build boxes, but I
think the p2k10 build machine had USE_SYSTRACE not set and was
building as root. If you aren't using both USE_SYSTRACE=Yes and SUDO,
can you do a bulk build with either/both set and see if the problem
goes away? I'm not sure if the problem is mitigated by using either
or both of the options, but hopefully knowing which fixes it will
narrow the problem space.
Jeremy
I've not used systrace in a while, and normally build as root.
This just started sometime around the ports hackathon. I've
been wondering if I missed a comment that talked of a thing
that needed to be set/changed, but so far it has eluded me,
hence this mail.
dpb -a -j2 is how I've been starting the build.
--STeve Andre'
