On Thu, Aug 27, 2009 at 8:15 AM, John H Palmieri<[email protected]> wrote: > > On Aug 27, 7:05 am, Simon King <[email protected]> wrote: >> Hi Minh, and Hi Mac Experts, >> >> On Aug 27, 12:34 am, Minh Nguyen <[email protected]> wrote: >> >> > This harks back to the build problem with cliquer. I can test spkg's >> > under any Linux boxes that I have access to. But not Mac boxes, which >> > is a shame as many people are using OS X. >> >> Now I feel less lonely. I thought I am the only sage developer without >> a Mac :-) >> >> But seriously, I would appreciate if some Mac expert could try and >> help me to hunt down the build problem on Intel Mac! >> >> The reasons why I am puzzled: >> >> * I understood that William did a successful test on many platforms, >> presumably including Intel Mac, of a previous package version that now >> is an optional package, installable by >> sage: install_package('p_group_cohomology') >> AFAIK, I did not change the part that now fails to build. >> >> * The error reported by John Palmieri was >> {{{ >> ar rv /Applications/sage_builds/sage-4.1.1-binary/spkg/build/ >> p_group_cohomology-1.1/src/lib/libmtx.a os.o >> ar rv /Applications/sage_builds/sage-4.1.1-binary/spkg/build/ >> p_group_cohomology-1.1/src/lib/libmtx.a profile.o >> ar: /Applications/sage_builds/sage-4.1.1-binary/spkg/build/ >> p_group_cohomology-1.1/src/lib/libmtx.a: Resource temporarily >> unavailable >> make[2]: *** [/Applications/sage_builds/sage-4.1.1-binary/spkg/build/ >> p_group_cohomology-1.1/src/lib/libmtx.a(profile.o)] Error 1 >> make[2]: *** Waiting for unfinished jobs.... >> a - os.o >> >> }}} >> >> What does it mean, "Resource temporarily unavailable"? Does the Mac >> try a parallel build, so that two different parts of the build process >> try to write into libmtx.a at the same time? Is it a write permission >> issue? > > I now think it's a parallel build issue. It turns out that I have > "$MAKE" set to "make -j2", and when I unset this, the build process > gets past this point. It now claims to have been installed > successfully, so now I'll test it out. > > Should the use of "make -jN" be checked for in the spkg-install file > in this case, since it seems to lead to problems? >
Yes, this is done in many spkg's actually. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
