delorie.com/archives/browse.cgi | search |
On Sun, 3 Oct 2021, John L. Males (jlmales AT gmail DOT com) [via geda-help AT delorie DOT com] wrote: > I downloaded the link you last indicated. The ./configure script > was in the tar file. Ran usual "./configure" and "make" and all > was fine, but no tests were run. That's exactly how it should behave. If you want to run the tests as part of building a package, first run "make" as usual, then run "make check". > What this means is the "release" file is not the same as the github > tag code for 1.9.16. A release tarball is what is created using "make dist" / "make distcheck". This not just an archive containing the files from the repository; it contains additional files (like "configure" and the various "Makefile.in") and may not contain others which are not intended to be distributed. > The first difference is not an issue, but frankly I liked how the > release tar file link you noted ran. There was simply one line > for each source element being compiled. With the 1.9.16 Debian > release each source file compile had the familiar many items of > options. Why the difference in how the compile appears on CLI for > same tar file I do not know. I like the clan style as when there > are warnings or errors it is easier to see and find. This is a feature called "silent rules". You can enable this for any package that supports it by passing the option "--enable-silent-rules" to the configure script, or enable it selectively by running "make V=0". Roland
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |