From: Gunter K. <gu...@pe...> - 2016-07-09 17:31:55
|
On 09.07.2016 18:58, Raymond Toy wrote: >>>>>> "Gunter" == Gunter Königsmann <gu...@pe...> writes: > > Gunter> Dear all, Today I tried to clean up a bit and encountered > Gunter> a problem I don't know how to handle: > > Gunter> After a > > Gunter> ./bootstrap ./configure --enable-sbcl --enable-clisp > Gunter> make -j 4 > > Does -j 4 actually work? I'm not sure if the makefile is really set up > to do parallel builds. > I was convinced that Ubuntu's standard build configuration for packages does do parallel builds so somebody will have thought about this: Way back there were packages with bugs that depended on the build order. But it seems like they have changed back to one process at a time => Did a new clean checkout of the maxima repo and the following: ./bootstrap ./configure --enable-sbcl --enable-ccl make make pdf > > Gunter> the file src/share-subdirs.lisp differs from the version > Gunter> in the repository. If the change were reproducible for > Gunter> every build and the changes wouldn't reference > Gunter> autogenerated directories this would be a case for adding > Gunter> the changes to this file to the repo. But this isn't the > Gunter> case. The new entries are: > > Gunter> "contrib/integration/abs_integrate.t2p" > > How were these *.t2p directories created? I don't have them. I also > don't use make -j 4. Normally these things are seldom a coincidence so while waiting for the build I investigated: There is no trace of .t2p directories in my share/Logic/Makefile.am share/Logic/Makefile.in in the same folder mentions them, though: .texi.pdf: $(AM_V_TEXI2PDF)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \ MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I $(srcdir)' \ $(TEXI2PDF) $(AM_V_texinfo) --build-dir=$(@:.pdf=.t2p) -o $@ $(AM_V_texidevnull) \ $< => Something in automake/autoconf/autosomething instructs the pdf target to put all temporary files here. share/Logic/Makefile contains one command that can delete the .t2p directory. But afaics it is only called on "make distclean" or similar: an ordinary "make clean" doesn't help here. Seems like my version of the autotools autogenerates the files. Ok.. ...the new checkout has built. On my system the .t2p files are generated again so I assume (as I have installed the newest version of the autotools) their existence depends on the autotools versions. The questions now are - if the fact that the .t2p directories aren't deleted automatically after the build is a bug or it it will stay this way - we add generated .texi- and .pdf files to the repository: At least for share/logic/logic.texi and share/logic/logic.pdf this is the case. Currently the version that comes with the repo coincides byte-per-byte with the one my system builds. But for others that might not be true which tends to be able to cause nightmares for users that want to do a "git bisect". Can we do something about this. - And (since that makes "git bisect" harder, too): Just changing the status if this file from version controlled to autogenerated by deleting it means that the file hangs around during a git bisect and has to be manually deleted every few steps. ...can we do something about this? I seem to remember adding it to .gitignore isn't enough. Don't know if I should be the one who cleans this up as I honestly am not sure about the answer of any of these questions. Kind regards, Gunter. |