X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20210112;
	h=date:from:to:subject:message-id:in-reply-to:references:reply-to
	:organization:disposition-notification-to:return-receipt-to
	:mime-version;
	bh=nGld4w2JxV3oeDZajR4OGIfqSC7/aKtsttcqTlfXbDQ=;
	b=StsZtLLs3kuivJX+kZK0zPJHPZgUNCWenWv6VqMPM1X5P/RCwZFUyqmF91q/+uGZnl
	AzpAJbF1MVz6lmr6UoGle/1gLomx5rcLnjD3e8j51qvtAkqUUeeGOFVaAE0CI49TBYwc
	K14S47HAbyooJDqbznsRg03oRaecLfZleamshhJo0CCLowZ6tRppktFBbfLZNRX4Nj1X
	trViwRnhxj0F4RnsgGjnvrT+06ZqiAoo6uW4yKeNgAJVYI3HJc4maI1UCCUMasKzQZ8Q
	1arNnVBBedo7qYvPU6Z+wNZkzHvShxyxfN9E57Yuu1yz+Yyq4DXQ0qPmNXoK9yfD6Y3a
	cjiA==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20210112;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:reply-to:organization:disposition-notification-to
	:return-receipt-to:mime-version;
	bh=nGld4w2JxV3oeDZajR4OGIfqSC7/aKtsttcqTlfXbDQ=;
	b=149RUg/X/oqj4leh3ysh8YNA7xiO7bkPRL0wzmtWeagk22v/iKdmu9dlH1vmM1PnNh
	miGZehVtwg61C2QKRleN+3ztdoeHVhGgdxUimrJh08y9GUASCXiVuiRuMeW0WmlqpaTy
	3Pbl9Tx2KDYQUX/H/xGwEMUnFwQIX9aYwZ3Gw3ujg+hO5cQfzCzR14Zn7iHRf2uhSZNp
	/wIY6pkOUhVMGZqyGutxVodRCjNssK1/BfK6vt4bBZXi6cVvP8BjeKXBoJGYKnvYu2v5
	bsF3xL6DtNReqB+KVga7g20WPb35VmOkvoZPjWIfVfEfgDJTmJEKrBWzn+KnnZAkIOT4
	qKQw==
X-Gm-Message-State:	AOAM530O/CC/iXj8auE6B6G7rnzT+coTfAwzC8g8cWkvwPj5qTee+YWs
	m323MsTX3QH5gmUDQhKns1ef/EVgXtRY
X-Google-Smtp-Source:	ABdhPJx0UOlXiwvb3JtWFg+PtqK5sJ2Cb3drQ7oo6X/NTGGat0VqAaQJ/HrssT+WoIrj3eHAQgoSGw==
X-Received:	by 2002:a6b:f111:: with SMTP id e17mr5832738iog.147.1633272819728;
	Sun, 03 Oct 2021 07:53:39 -0700 (PDT)
Date:	Sun, 3 Oct 2021 14:53:25 +0000
From:	"John L. Males (jlmales AT gmail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
To:	geda-help AT delorie DOT com
Subject:	Re: [geda-help] Lepton-EDA Compiling Challenges
Message-Id:	<20211003145325.e25fef4d2670be39b3395acf@gmail.com>
In-Reply-To:	<alpine.DEB.2.21.2110022023340.6807@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>
Organization:	Toronto, Ontario
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.3)
Disposition-Notification-To:	jlmales AT gmail DOT com
X-Compose-Start-Epoch:	`date +%s`
Mime-Version:	1.0
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

--Signature=_Sun__3_Oct_2021_14_53_25_+0000_Ot8ZfrgF/Ty6YZEb
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Roland,

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.

What this means is the "release" file is not the same as the github
tag code for 1.9.16.  That to me is issue in sense changes were
made in the release file that are not in the 1.9.16 github tag
version of the code.  I do not expect the ./configure script to ne
in the github tag for 1.9.16 or any such tagged release, but I do
expect if one runs the ./autogen.sh that the resulting ./configure
and make work to build the code via the make file rules.

Looking at the make file for the release file you last noted I found
a rule called check-TESTS. I ran it.  It ran 16 tests and all
appeared to run as expected. 16 passed of 16 tests.

I did a cmp of the tar file you indicated for me to download to the
tar file part of the Debian 1.9.16 package.  The files compared as
identical.

Despite the identical nature of the tar files there were some
notable differences.

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.

The second difference was related to tests.  The only test I found
with your noted release file did 16 tests and those 16 tests all
passed. The Debian 1.9.16 ran 2587 tests that all passed then ran
another set of tests where 17 tests run and passed, and another
set of tests 408 fail of 408. I not sure why all these tests and
many more than in the release file you provided a link to as the
only things the Debian package is patching is a Perl path and fix
for dynamic linking.


John L. Males
Toronto, Ontario
03 October 2021 10:53 -0400 EDT


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

2021-10-03 12:50:36+0000-UTC Time: 1633265436 PC/System time

 3 Oct 12:50:36 ntpdate[89659]: ntpdate 4.2.8p12-a (1)

3 Oct 12:50:51 ntpdate[89732]: step time server 216.197.228.230
offset +0.003068 sec

FreeBSD 11.4-RELEASE-p3 FreeBSD 11.4-RELEASE-p3 #0: Tue Sep  1
08:22:33 UTC 2020
root AT amd64-builder DOT daemonology DOT net:/usr/obj/usr/src/sys/GENERIC=20

(Work in progress alternative to Linux Kernel of its own right,
 Debian, and
 other Linux based Kernel distributions determined.)

Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz
Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz (1396.86-MHz K8-class CPU)
Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz (1396.86-MHz K8-class CPU)
Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz (1396.86-MHz K8-class CPU)
Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz (1396.86-MHz K8-class CPU)
Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz (1396.86-MHz K8-class CPU)

dev.cpu.0.temperature: 83.0C
dev.cpu.1.temperature: 83.0C
dev.cpu.2.temperature: 79.0C
dev.cpu.3.temperature: 79.0C
hw.acpi.thermal.tz0.temperature: 83.1C

vmstat -s:

3408228125 cpu context switches
1238353972 device interrupts
640119506 software interrupts
448222573 traps
2501782078 system calls
       29 kernel threads created
   338343  fork() calls
    71519 vfork() calls
      148 rfork() calls
 30644847 swap pager pageins
 84559962 swap pager pages paged in
 16104084 swap pager pageouts
 96696578 swap pager pages paged out
  1276627 vnode pager pageins
  8963385 vnode pager pages paged in
    23048 vnode pager pageouts
   364453 vnode pager pages paged out
    48696 page daemon wakeups
419511399 pages examined by the page daemon
     3980 clean page reclamation shortfalls
2977604234 pages reactivated by the page daemon
 26510308 copy-on-write faults
    21356 copy-on-write optimized faults
2906568889 zero fill pages zeroed
   569177 zero fill pages prezeroed
 30969218 intransit blocking page faults
555553642 total VM faults taken
 30732297 page faults requiring I/O
        0 pages affected by kernel thread creation
 21142668 pages affected by  fork()
  2503929 pages affected by vfork()
     7400 pages affected by rfork()
307669553 pages freed
2841349930 pages freed by daemon
1600444223 pages freed by exiting processes
   425084 pages active
  2151220 pages inactive
   413104 pages in the laundry queue
   786173 pages wired down
   277184 pages free
     4096 bytes per page
3080835048 total name lookups
          cache hits (79% pos + 6% neg) system 1% per-directory
          deletions 0%, falsehits 0%, toolong 0%

Boot time : 1623954544

procs     memory        page                    disks
faults        cpu0     cpu1     cpu2     cpu3 r b w     avm
fre  flt  re  pi  po    fr   sr md10 ad0   in    sy    cs us sy id
us sy id us sy id us sy id 2 0 0 70689924 1108664    60 320   3
2    33   45   0   0  133   269   366 27  5 68 27  5 68 27  5 68
27  5 68

memory info:

real memory  =3D 17179869184 (16384 MB)
avail memory =3D 16495013888 (15730 MB)

last pid: 91144;  load averages:  1.86,  1.55,  1.41  up
107+18:21:48    12:50:52 149 processes: 1 running, 147 sleeping, 1
zombie

Mem: 1661M Active, 8403M Inact, 1614M Laundry, 3071M Wired, 1554M
Buf, 1082M Free Swap: 48G Total, 5572M Used, 43G Free, 11% Inuse

hw.physmem: 17053859840
hw.usermem: 13833527296
hw.realmem: 17179869184

             total       used       free     shared    buffers
cached Mem:      16210872    6497384    9713488          0
0          0 Swap:     50331644    5706096   44625548

swapinfo:

Device          1K-blocks     Used    Avail Capacity
/dev/ada0s1b     50331644  5706096 44625548    11%

vmstat:

procs     memory        page                    disks
faults         cpu r b w     avm     fre  flt  re  pi  po    fr
sr md10 ad0   in    sy    cs us sy id 1 0 0 70689924 1108668    60
320   3   2    33   45   0   0  133   269   366 27  5 68


On Sat, 2 Oct 2021 20:34:21 +0200 (CEST)
Roland Lutz <rlutz AT hedmen DOT org> wrote:
Subject: Re: [geda-help] Lepton-EDA Compiling Challenges
To: "John L. Males (jlmales AT gmail DOT com) [via geda-help AT delorie DOT com]"
<geda-help AT delorie DOT com> CC:=20
MessageID: alpine DOT DEB DOT 2 DOT 21 DOT 2110022023340 DOT 6807 AT nimbus

> On Sat, 2 Oct 2021, John L. Males (jlmales AT gmail DOT com) [via=20
> geda-help AT delorie DOT com] wrote:
> > I did download the 1.9.16 release tarball and it did not contain
> > the ./configure script.  I did not download the github snapshot
> > release as the source tarball name was 1.9.16-20210731.zip
>=20
> This is the repository snapshot; GitHub is a bit confusing in that regard=
.=20
> The correct address as from the accouncement mail is:
>=20
>    https://github.com/lepton-eda/lepton-eda/releases/download/1.9.16-2021=
0731/lepton-eda-1.9.16.tar.gz
>=20
> > I was expecting the release source tarball from github to
> > work only to find the release tarball even when I create
> > the ./configure script via ./autogen.sh cannot even run the 'make
> > all' with the prior noted make error for version.h.
>=20
> Building from the repository snapshot should work just like building from=
=20
> the checked-out sources, so this may be an additional, unrelated problem.
>=20
> > With regards to the issues with the Debian source packages I did of
> > course use dpkg-buildpackage.
>=20
> Hmm.  Maybe "gbp buildpackage" does the trick?  But I'd recommend buildin=
g=20
> from the release tarball anyway.
>=20
> Roland
>=20

--Signature=_Sun__3_Oct_2021_14_53_25_+0000_Ot8ZfrgF/Ty6YZEb
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQQxRId2q5JPHFiozTr5X9dS0HpoEAUCYVnD5QAKCRD5X9dS0Hpo
ELkOAKDW8/2vDMjenS6e5sJjRzqqIaVYVQCeLRE5/9Xlonqshzs1NJs7ZiF6drc=
=1Sv7
-----END PGP SIGNATURE-----

--Signature=_Sun__3_Oct_2021_14_53_25_+0000_Ot8ZfrgF/Ty6YZEb--

- Raw text -