Looks like the gpde library causes some problems. :/<br>I guess this is related to the Makefile. The gpde lib Makefile copies the N_pde.h <br>header file into the build include directory before compiling:<br><br>MODULE_TOPDIR = ../..
<br><br>EXTRA_LIBS=$(GISLIB) $(G3DLIB)<br>LIB_NAME = $(GPDE_LIBNAME)<br><br>include $(MODULE_TOPDIR)/include/Make/Lib.make<br>include $(MODULE_TOPDIR)/include/Make/Doxygen.make<br><br>default: headers lib<br><br>headers:<br>
for file in ./N_*.h ; do $(INSTALL_DATA) $$file $(GISBASE)/include/grass/ ; done<br><br>lib: headers<br><br>#doxygen:<br>DOXNAME=gpde<br><br><br>I don't know why this is not working on a smp machine? <br>Are you using NFS? Maybe there is a delay while copying the header?
<br>Sorry, i cant help much in this case, my Makefile knowledge is very limited.<br><br><br>Best regards<br>Soeren<br><br><div><span class="gmail_quote">2007/10/18, Maciej Sieczka <<a href="mailto:tutey@o2.pl">tutey@o2.pl
</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Glynn Clements wrote:<br>> Maciej Sieczka wrote:<br>><br>>>>> sorry but I'm not an make guru and thus see it simple: if I run comand
<br>>>>> "make -j4" it should get along with it or fail with "err blah parallel<br>>>>> buld not supported". Current CVS version does neither of it.<br>>>> I hope we don't give up so early. Probably just a few Makefiles
<br>>>> need to be fixed (basically, get the target order right therein).<br>>>>> As multicore CPU's are getting more popular, more and more users will be<br>>>>> trying to run "make -j X" and thus report failure as bug [1].
<br>>>> Not always. As written yesterday, "make -j3" worked for me on my RHEL5<br>>>> box. Now testing with Mandriva.<br>>>>> If I can help with testing, drop me instructions. I have Gentoo ~x86
<br>>>>> system (gcc version 4.2.1; GNU Make 3.81).<br>>>> Please help testing. Just run it and see if and where it fails.<br>>>> Then check the problematic Makefile(s) for correct order:<br>
>>> <a href="http://grass.gdf-hannover.de/wiki/Development#GRASS_Makefile_writing">http://grass.gdf-hannover.de/wiki/Development#GRASS_Makefile_writing</a><br>>> As for testing: I get the following errors with make -j3 on
<br>>> Intel Core 2 6600 running 2.6.15-29-amd64-xeon (Ubuntu Dapper):<br>>><br>>> --<br>>> Errors in:<br>>> /home/maciek/src/straight/grass63/lib/gpde<br>>> /home/maciek/src/straight/grass63/imagery/i.vpoints
<br>>> /home/maciek/src/straight/grass63/misc/m.cogo<br>>> /home/maciek/src/straight/grass63/raster/r.gwflow<br>>> /home/maciek/src/straight/grass63/raster/r.to.rast3elev<br>>> /home/maciek/src/straight/grass63/raster3d/r3.gwflow
<br>>> /home/maciek/src/straight/grass63/vector/v.sample<br>><br>> What errors, exactly?<br><br>That's all it says:<br><br>Started compilation: Thu Oct 18 00:07:37 CEST 2007<br>--<br>Errors in:<br>/home/maciek/src/straight/grass63/lib/gpde
<br>/home/maciek/src/straight/grass63/misc/m.cogo<br>/home/maciek/src/straight/grass63/raster/r.gwflow<br>/home/maciek/src/straight/grass63/raster3d/r3.gwflow<br>--<br>In case of errors please change into the directory with
<br>error and run 'make'. If you get multiple errors, you need<br>to deal with them in the order they appear in the error log.<br>If you get an error building a library, you will also get<br>errors from anything which uses the library.
<br>--<br>Finished compilation: Thu Oct 18 00:11:12 CEST 2007<br>make: *** [default] Error 1<br><br>If you'd like to see full make and configure output they are<br>here [1].<br><br>(Note this time there are less modules affected, and there
<br>haven't been any commits to CVS between this and previous<br>CVS checkout + make run; I remembered to run "make<br>distclean" both times FWIW).<br><br>When I enter dirs mentioned in "Errors in:", one by one,
<br>and run "make -j3", they build fine and no errors are printed.<br><br>Maciek<br><br>[1]http://www.biol.uni.wroc.pl/sieczka/udostepnione/grass/grass63_make_j3_18.10.07.tar.bz2<br><br>_______________________________________________
<br>grass-dev mailing list<br><a href="mailto:grass-dev@grass.itc.it">grass-dev@grass.itc.it</a><br><a href="http://grass.itc.it/mailman/listinfo/grass-dev">http://grass.itc.it/mailman/listinfo/grass-dev</a><br></blockquote>
</div><br>