Hi Dave, Thanks for your reply and my apologies for the very slow response.
Yes, I have passed the -j option to gnu make as in qmake -cwd -v PATH -now no -q all.q -- -j 12 -k <makefile> What would make my rules incorrect for parallel building? Thanks again, Cas On Wed, Jun 22, 2011 at 10:06 AM, Dave Love <[email protected]> wrote: > Casimir Wierzynski <[email protected]> writes: > > > Dear SGE users, > > > > I have a makefile that works correctly when called with the -n option, ie > > all the rules and targets are correctly computed. But *without* the -n > > option, ie when running it for real, it prints out the commands > correctly, > > but then sometimes it spits out a bunch of error messages of the form > > > > qmake: *** No rule to make target > > > `/LD/ld453/analysis/Mingus/06_08_2011_14_34_47/06_08_2011_16_35_13/spikes_tt9.h5', > > needed by `spikes'. > > qmake: *** > > > [/LD/ld453/analysis/Mingus/06_08_2011_14_34_47/06_08_2011_16_35_13/spikes_tt9.h5] > > Error 129 > > > > And sometimes it all just works fine. With ordinary gnu make, everything > > works fine always. > > Is that with concurency (-j)? > > > What is error 129? And has anyone observed this behavior before? > > $ perror $(expr 129 - 127) > OS error code 2: No such file or directory > > I'd guess that the make rules aren't actually correct for parallel > building, > and sometimes you're lucky withy the target already being there. qmake > is based on an ancient GNU make (on the list for fix) but I doubt that's > the cause. > > -- > Excuse the typping -- I have a broken wrist > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
