X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
Date: Sun, 3 Oct 2021 17:33:06 +0200 (CEST)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "John L. Males (jlmales AT gmail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
Subject: Re: [geda-help] Lepton-EDA Compiling Challenges
In-Reply-To: <20211003145325.e25fef4d2670be39b3395acf@gmail.com>
Message-ID: <alpine.DEB.2.21.2110031719460.7496@nimbus>
References: <20211002151622 DOT 2bde5243b118d2a566d83d97 AT gmail DOT com> <alpine DOT DEB DOT 2 DOT 21 DOT 2110021910260 DOT 1666 AT nimbus> <20211002180121 DOT c6352334739b442056eae81b AT gmail DOT com> <alpine DOT DEB DOT 2 DOT 21 DOT 2110022023340 DOT 6807 AT nimbus> <20211003145325 DOT e25fef4d2670be39b3395acf AT gmail DOT com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

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