NetBSD Problem Report #56238

From www@netbsd.org  Mon Jun  7 07:35:17 2021
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id E822C1A921F
	for <gnats-bugs@gnats.NetBSD.org>; Mon,  7 Jun 2021 07:35:16 +0000 (UTC)
Message-Id: <20210607073515.104DA1A9239@mollari.NetBSD.org>
Date: Mon,  7 Jun 2021 07:35:15 +0000 (UTC)
From: jbglaw@lug-owl.de
Reply-To: jbglaw@lug-owl.de
To: gnats-bugs@NetBSD.org
Subject: Several ARM-Variants seem to miss gcov-iov.h
X-Send-Pr-Version: www-1.0

>Number:         56238
>Category:       port-zaurus
>Synopsis:       Several ARM-Variants seem to miss gcov-iov.h
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-zaurus-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 07 07:40:00 +0000 2021
>Last-Modified:  Tue Jun 15 15:50:01 +0000 2021
>Originator:     Jan-Benedict Glaw
>Release:        
>Organization:
>Environment:
Linux spock 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) x86_64 GNU/Linux

>Description:
Hi!

Now that the ifunc tests are fixed for ARM, there's one issue uncovered for the zaurus port: It builds the kernel, but when preparing the ramdisk (for ./build.sh -P -U -u -m zaurus -a arm release), it fails due to compiler options:

depend ===> etc/notes
depend ===> etc/utils
depend ===> etc/zaurus
depend ===> etc/zaurus/ramdisk
depend ===> etc/zaurus/instkernel
depend ===> etc/zaurus/cdroms
depend ===> etc/zaurus/cdroms/installcd
depend ===> etc/zaurus/liveimage
all ===> etc/notes
all ===> etc/utils
all ===> etc/zaurus
all ===> etc/zaurus/ramdisk
#   compile  ramdisk/getcap.o
/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/arm--netbsdelf-gcc -Os -mthumb -mthumb-interwork -DNDEBUG    -msoft-float  -fdebug-prefix-map=\
$DESTDIR= -fdebug-prefix-map=\$NETBSDSRCDIR=/usr/src -fdebug-prefix-map=\$X11SRCDIR=/usr/xsrc -fdebug-regex-map='/usr/src/(.*)/obj$=/usr/obj/\1' -fdebug-regex-map='/usr/src/(.*)/obj/(.*)=/usr/obj/\1/\2' -fdebug-regex-map='/usr/src/(.*)/obj\..*=/usr/obj/\1' -fdebug-regex-map='/usr/src/(.*)/obj\..*/(.*)=/usr/obj/\1/\2'   -std=gnu99    -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare  -Wsystem-headers   -Wno-traditional   -Wa,--fatal-warnings  -Werror     --sysroot=/var/lib/laminar/run/netbsd-zaurus-arm/8/dest-zaurus-arm -DSMALL -DLIBHACK -Wp,-iremap,/var/lib/laminar/run/netbsd-zaurus-arm/8/dest-zaurus-arm: -Wp,-fno-canonical-system-headers -Wp,-iremap,/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src:/usr/src -Wp,-iremap,/usr/xsrc:/usr/xsrc  -c    /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib/utils/libhack/../../../lib/libc/gen/getcap.c -o getcap.o
cc1: error: target CPU does not support interworking [-Werror]
cc1: error: target CPU does not support THUMB instructions [-Werror]
cc1: all warnings being treated as errors

*** Failed target:  getcap.o
*** Failed command: /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/arm--netbsdelf-gcc -Os -mthumb -mthumb-interwork -DNDEBUG -msoft-float -fdebug-prefix-map=\$DESTDIR= -fdebug-prefix-map=\$NETBSDSRCDIR=/usr/src -fdebug-prefix-map=\$X11SRCDIR=/usr/xsrc -fdebug-regex-map='/usr/src/(.*)/obj$=/usr/obj/\1' -fdebug-regex-map='/usr/src/(.*)/obj/(.*)=/usr/obj/\1/\2' -fdebug-regex-map='/usr/src/(.*)/obj\..*=/usr/obj/\1' -fdebug-regex-map='/usr/src/(.*)/obj\..*/(.*)=/usr/obj/\1/\2' -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Werror --sysroot=/var/lib/laminar/run/netbsd-zaurus-arm/8/dest-zaurus-arm -DSMALL -DLIBHACK -Wp,-iremap,/var/lib/laminar/run/netbsd-zaurus-arm/8/dest-zaurus-arm: -Wp,-fno-canonical-system-headers -Wp,-iremap,/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src:/usr/src -Wp,-iremap,/usr/xsrc:/usr/xsrc -c /var/lib/laminar/run
 /netbsd-zaurus-arm/8/NetBSD-src/distrib/utils/libhack/../../../lib/libc/gen/getcap.c -o getcap.o
*** Error code 1

Stop.
nbmake[4]: stopped in /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib/zaurus/ramdisk 

*** Failed target:  all-ramdisk
*** Failed command: _makedirtarget() { dir="$1"; shift; target="$1"; shift; case "${dir}" in /*) this="${dir}/"; real="${dir}" ;; .) this="etc/zaurus/"; real="/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib/zaurus" ;; *) this="etc/zaurus/${dir}/"; real="/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib/zaurus/${dir}" ;; esac; show=${this:-.}; echo "${target} ===> ${show%/}${1:+ (with: $@)}"; cd "${real}" && /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/nbmake _THISDIR_="${this}" "$@" ${target}; }; _makedirtarget ramdisk all
*** Error code 1

Stop.
nbmake[3]: stopped in /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib/zaurus

*** Failed target:  all-zaurus
*** Failed command: _makedirtarget() { dir="$1"; shift; target="$1"; shift; case "${dir}" in /*) this="${dir}/"; real="${dir}" ;; .) this="etc/"; real="/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib" ;; *) this="etc/${dir}/"; real="/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib/${dir}" ;; esac; show=${this:-.}; echo "${target} ===> ${show%/}${1:+ (with: $@)}"; cd "${real}" && /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/nbmake _THISDIR_="${this}" "$@" ${target}; }; _makedirtarget zaurus all
*** Error code 1

Stop.
nbmake[2]: stopped in /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib

*** Failed target:  snap_post
*** Failed command: cd /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/distrib && /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/nbmake depend && /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/nbmake && /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/nbmake release
*** Error code 1

Stop.
nbmake[1]: stopped in /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/etc

*** Failed target:  release
*** Failed command: _makedirtarget() { dir="$1"; shift; target="$1"; shift; case "${dir}" in /*) this="${dir}/"; real="${dir}" ;; .) this=""; real="/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src" ;; *) this="${dir}/"; real="/var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/${dir}" ;; esac; show=${this:-.}; echo "${target} ===> ${show%/}${1:+ (with: $@)}"; cd "${real}" && /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src/obj/tooldir.Linux-5.10.0-3-amd64-x86_64/bin/nbmake _THISDIR_="${this}" "$@" ${target}; }; _makedirtarget etc release DISTRIBUTION_DONE=1
*** Error code 1

Stop.
nbmake: stopped in /var/lib/laminar/run/netbsd-zaurus-arm/8/NetBSD-src

ERROR: Failed to make release
*** BUILD ABORTED ***



>How-To-Repeat:

>Fix:

>Audit-Trail:
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Mon, 7 Jun 2021 09:45:09 +0200

 --lkwjypj3lk4ew55z
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Mon, 2021-06-07 07:40:00 +0000, gnats-admin@netbsd.org <gnats-admin@netb=
 sd.org> wrote:
 > >Category:       port-zaurus
 > >Responsible:    port-zaurus-maintainer
 > >Synopsis:       Several ARM-Variants seem to miss gcov-iov.h
 > >Arrival-Date:   Mon Jun 07 07:40:00 +0000 2021

 I've seen this for these ports/archs:

 	evbarm / earmv5
 	evbarm / earmv5eb
 	evbarm / earmv5hf
 	evbarm / earmv5hfeb

 However, this probably belongs to 56231.

 Thanks,
   Jan-Benedict
 --=20

 --lkwjypj3lk4ew55z
 Content-Type: application/pgp-signature; name="signature.asc"

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

 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYL3OggAKCRAdvV51g5nh
 u5GcAJ0a2TtQS4Lo5G7HMZG1Cz+AZ4aPaACgiqTXFNw3dUkugDD7AVofk7QLO54=
 =TLVC
 -----END PGP SIGNATURE-----

 --lkwjypj3lk4ew55z--

From: Christos Zoulas <christos@zoulas.com>
To: gnats-bugs@netbsd.org
Cc: port-zaurus-maintainer@netbsd.org,
 gnats-admin@netbsd.org,
 netbsd-bugs@netbsd.org,
 jbglaw@lug-owl.de
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Mon, 7 Jun 2021 07:42:59 -0400

 --Apple-Mail=_2E7CE032-1575-4122-9459-3B326159CCB9
 Content-Transfer-Encoding: 7bit
 Content-Type: text/plain;
 	charset=us-ascii

 I ran build.sh -a earmv5hfeb -m evbarm and it ran to completion for me.

 christos

 --Apple-Mail=_2E7CE032-1575-4122-9459-3B326159CCB9
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 	filename=signature.asc
 Content-Type: application/pgp-signature;
 	name=signature.asc
 Content-Description: Message signed with OpenPGP

 -----BEGIN PGP SIGNATURE-----
 Comment: GPGTools - http://gpgtools.org

 iF0EARECAB0WIQS+BJlbqPkO0MDBdsRxESqxbLM7OgUCYL4GQwAKCRBxESqxbLM7
 OigJAJ9R5B0DNiY4AwBjsyqPaKaT868/cACgwQMAxBDOA+h4e4SSTQwMEmxTNHs=
 =fEYc
 -----END PGP SIGNATURE-----

 --Apple-Mail=_2E7CE032-1575-4122-9459-3B326159CCB9--

From: Christos Zoulas <christos@zoulas.com>
To: gnats-bugs@netbsd.org
Cc: port-zaurus-maintainer@netbsd.org,
 gnats-admin@netbsd.org,
 netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Mon, 7 Jun 2021 07:47:51 -0400

 --Apple-Mail=_74A4E1DA-6833-4367-9D48-D06B770DB831
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/plain;
 	charset=us-ascii

 I think it is time to retire the oabi combinations. build.sh does not =
 detect all
 invalid or obsolete combinations. I posted in tech-toolchain asking for =
 permission
 to do so.

 christos

 --Apple-Mail=_74A4E1DA-6833-4367-9D48-D06B770DB831
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 	filename=signature.asc
 Content-Type: application/pgp-signature;
 	name=signature.asc
 Content-Description: Message signed with OpenPGP

 -----BEGIN PGP SIGNATURE-----
 Comment: GPGTools - http://gpgtools.org

 iF0EARECAB0WIQS+BJlbqPkO0MDBdsRxESqxbLM7OgUCYL4HZwAKCRBxESqxbLM7
 OiJ0AJoC4Cnvg0ku/fibY/R1PBlqUazwOgCfSeSDEYTJ4DZAc1R+HecqzaxTNAs=
 =UMjK
 -----END PGP SIGNATURE-----

 --Apple-Mail=_74A4E1DA-6833-4367-9D48-D06B770DB831--

From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Christos Zoulas <christos@zoulas.com>
Cc: gnats-bugs@netbsd.org, port-zaurus-maintainer@netbsd.org,
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Mon, 7 Jun 2021 19:05:48 +0200

 --n7yj422jyqocblbh
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Mon, 2021-06-07 07:42:59 -0400, Christos Zoulas <christos@zoulas.com> wr=
 ote:
 > I ran build.sh -a earmv5hfeb -m evbarm and it ran to completion for me.

 Are these maybe uncommitted? Do you have build logs around? My builder
 is IPv6-only right now, but I've copied the four most recend logs
 to the lug-owl.de host:

 	https://lug-owl.de/~jbglaw/laminar/netbsd-evbarm-earmv5-5.gz
 	https://lug-owl.de/~jbglaw/laminar/netbsd-evbarm-earmv5eb-5.gz
 	https://lug-owl.de/~jbglaw/laminar/netbsd-evbarm-earmv5hf-6.gz
 	https://lug-owl.de/~jbglaw/laminar/netbsd-evbarm-earmv5hfeb-6.gz

 MfG, JBG

 --=20

 --n7yj422jyqocblbh
 Content-Type: application/pgp-signature; name="signature.asc"

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

 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYL5R6AAKCRAdvV51g5nh
 uywkAJ9vtWVKjJ04/Q1Mv93b2Rx6e7uHuACeN46E7LQ7iup5tOeoNr2gmyENLQE=
 =a7KO
 -----END PGP SIGNATURE-----

 --n7yj422jyqocblbh--

From: Christos Zoulas <christos@zoulas.com>
To: gnats-bugs@netbsd.org
Cc: port-zaurus-maintainer@netbsd.org,
 gnats-admin@netbsd.org,
 netbsd-bugs@netbsd.org,
 jbglaw@lug-owl.de
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Mon, 7 Jun 2021 13:14:08 -0400

 --Apple-Mail=_705AF902-C2F2-438E-842E-FAB77E357999
 Content-Type: multipart/alternative;
 	boundary="Apple-Mail=_3B253E4F-EB6A-4CF7-8F8F-47DF11488CA9"


 --Apple-Mail=_3B253E4F-EB6A-4CF7-8F8F-47DF11488CA9
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/plain;
 	charset=us-ascii

 Mine is ftp://ftp.astron.com/pri/make.evbarm-earmv5hfeb.release.out.gz =
 <ftp://ftp.astron.com/pri/make.evbarm-earmv5hfeb.release.out.gz>.
 My tree has no local changes.

 christos

 --Apple-Mail=_3B253E4F-EB6A-4CF7-8F8F-47DF11488CA9
 Content-Transfer-Encoding: 7bit
 Content-Type: text/html;
 	charset=us-ascii

 <html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Mine is <a href="ftp://ftp.astron.com/pri/make.evbarm-earmv5hfeb.release.out.gz" class="">ftp://ftp.astron.com/pri/make.evbarm-earmv5hfeb.release.out.gz</a>.<div class="">My tree has no local changes.<br class=""><div class=""><br class=""></div><div class="">christos</div></div></body></html>
 --Apple-Mail=_3B253E4F-EB6A-4CF7-8F8F-47DF11488CA9--

 --Apple-Mail=_705AF902-C2F2-438E-842E-FAB77E357999
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 	filename=signature.asc
 Content-Type: application/pgp-signature;
 	name=signature.asc
 Content-Description: Message signed with OpenPGP

 -----BEGIN PGP SIGNATURE-----
 Comment: GPGTools - http://gpgtools.org

 iF0EARECAB0WIQS+BJlbqPkO0MDBdsRxESqxbLM7OgUCYL5T4AAKCRBxESqxbLM7
 OqjaAJ4qwzBKu3XswXF/oNAD4ceHxuEFgQCgro8+Df8zxdeqPxWbDXIDShPuHVs=
 =q7n5
 -----END PGP SIGNATURE-----

 --Apple-Mail=_705AF902-C2F2-438E-842E-FAB77E357999--

From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Christos Zoulas <christos@zoulas.com>
Cc: gnats-bugs@netbsd.org, port-zaurus-maintainer@netbsd.org,
	gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Wed, 9 Jun 2021 10:47:37 +0200

 --qcayz3imuvzjbq3t
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 Hi Christos,

 On Mon, 2021-06-07 07:42:59 -0400, Christos Zoulas <christos@zoulas.com> wr=
 ote:
 > I ran build.sh -a earmv5hfeb -m evbarm and it ran to completion for me.

 I cannot verify this: After installing a fresh NetBSD VM (downloaded
 official ISO:
 netbsd# cat /etc/release=20
 NetBSD 9.2/amd64

 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
     2018, 2019, 2020 The NetBSD Foundation, Inc.  All rights reserved.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

 Build information:
           Build date   Wed May 12 13:15:55 UTC 2021
             Built by   builder@localhost.NetBSD.org
             Build ID   202105121714Z

 Build settings:

           DISTRIBVER =3D '9.2'
   EXTERNAL_TOOLCHAIN =3D (undefined)
             HAVE_GCC =3D '7'
             HAVE_GDB =3D '830'

 then installed as a complete installation without X.)

 I copied over my GITtish "src" tree, placed a "git" shell script
 returning a matching build timestamp (to make build.sh happy) and ran
 (as root)

 cd ~/NetBSD-src
 =2E/build.sh -P -U    -m evbarm -a earmv5hfeb -E -D /root/D -R /root/R tools
 =2E/build.sh -P -U -u -m evbarm -a earmv5hfeb -E -D /root/D -R /root/R rele=
 ase

   Building tools worked, but building the release broke as it broke
 when building within the Linux (Debian) docker containers due to not
 finding gcov-iov.h.  So I guess something broke in the toolchain?

   Logs can be found at:

 	https://lug-owl.de/~jbglaw/laminar/tools.log
 	https://lug-owl.de/~jbglaw/laminar/release.log

 MfG, JBG

 --=20

 --qcayz3imuvzjbq3t
 Content-Type: application/pgp-signature; name="signature.asc"

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

 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYMCAIwAKCRAdvV51g5nh
 u2a2AJwOCXyPHV63GcMIx+nw1D5U6t92WQCfYilWWSjQiRka2jVl+sZ3mVBuzBo=
 =ELQ6
 -----END PGP SIGNATURE-----

 --qcayz3imuvzjbq3t--

From: Martin Husemann <martin@duskware.de>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Christos Zoulas <christos@zoulas.com>, gnats-bugs@netbsd.org,
	port-zaurus-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Wed, 9 Jun 2021 11:35:19 +0200

 On Wed, Jun 09, 2021 at 10:47:37AM +0200, Jan-Benedict Glaw wrote:
 >   Building tools worked, but building the release broke as it broke
 > when building within the Linux (Debian) docker containers due to not
 > finding gcov-iov.h.  So I guess something broke in the toolchain?
 > 
 >   Logs can be found at:
 > 
 > 	https://lug-owl.de/~jbglaw/laminar/tools.log
 > 	https://lug-owl.de/~jbglaw/laminar/release.log

 Well, it works for the official builds (which are done from cvs source
 trees), so it must be something git specific.

 Maybe a timestamp getting set differently, unveiling an unnoticed makefile
 bug?

 Martin

From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Martin Husemann <martin@duskware.de>
Cc: Christos Zoulas <christos@zoulas.com>, gnats-bugs@netbsd.org,
	port-zaurus-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Wed, 9 Jun 2021 11:56:39 +0200

 --7ixx25tnfjbea7uw
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Wed, 2021-06-09 11:35:19 +0200, Martin Husemann <martin@duskware.de> wro=
 te:
 > On Wed, Jun 09, 2021 at 10:47:37AM +0200, Jan-Benedict Glaw wrote:
 > >   Building tools worked, but building the release broke as it broke
 > > when building within the Linux (Debian) docker containers due to not
 > > finding gcov-iov.h.  So I guess something broke in the toolchain?
 > >=20
 > >   Logs can be found at:
 > >=20
 > > 	https://lug-owl.de/~jbglaw/laminar/tools.log
 > > 	https://lug-owl.de/~jbglaw/laminar/release.log
 >=20
 > Well, it works for the official builds (which are done from cvs source
 > trees), so it must be something git specific.
 >=20
 > Maybe a timestamp getting set differently, unveiling an unnoticed makefile
 > bug?

 Will check that next.

 MfG, JBG

 --=20

 --7ixx25tnfjbea7uw
 Content-Type: application/pgp-signature; name="signature.asc"

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

 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYMCQVAAKCRAdvV51g5nh
 uwxoAJ0T/b7DeEBOFO5wu+z/0YWD6qAgawCcDQjpk81G7/gARHk8r0EQhluvMSM=
 =YhdR
 -----END PGP SIGNATURE-----

 --7ixx25tnfjbea7uw--

From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Martin Husemann <martin@duskware.de>
Cc: Christos Zoulas <christos@zoulas.com>, gnats-bugs@netbsd.org,
	port-zaurus-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Thu, 10 Jun 2021 20:19:51 +0200

 --53uj6mijzn4d6pxg
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Wed, 2021-06-09 11:35:19 +0200, Martin Husemann <martin@duskware.de> wro=
 te:
 > On Wed, Jun 09, 2021 at 10:47:37AM +0200, Jan-Benedict Glaw wrote:
 > >   Building tools worked, but building the release broke as it broke
 > > when building within the Linux (Debian) docker containers due to not
 > > finding gcov-iov.h.  So I guess something broke in the toolchain?
 > >=20
 > >   Logs can be found at:
 > >=20
 > > 	https://lug-owl.de/~jbglaw/laminar/tools.log
 > > 	https://lug-owl.de/~jbglaw/laminar/release.log
 >=20
 > Well, it works for the official builds (which are done from cvs source
 > trees), so it must be something git specific.

 That's an interesting idea; I went out and checked it. The CVS and GIT
 trees are quite in sync (except for sync difference, the GIT tree lags
 behind a few hours), with the exception of this:

 $ diff -Nurp netbsd-from-cvs netbsd-from-git
 diff -Nurp netbsd-from-cvs/sys/arch/x68k/include/cdefs.h netbsd-from-git/sy=
 s/arch/x68k/include/cdefs.h
 --- netbsd-from-cvs/sys/arch/x68k/include/cdefs.h       1996-05-05 14:17:03=
 =2E000000000 +0200
 +++ netbsd-from-git/sys/arch/x68k/include/cdefs.h       2021-06-10 09:43:48=
 =2E000000000 +0200
 @@ -1,4 +1,4 @@
 -/*     $NetBSD: cdefs.h,v 1.1.1.1 1996/05/05 12:17:03 oki Exp $        */
 +/*     $NetBSD: cdefs.h,v 1.1 1996/05/05 12:17:15 oki Exp $    */
 =20
  #ifndef _MACHINE_CDEFS_H_
  #define _MACHINE_CDEFS_H_
 diff -Nurp netbsd-from-cvs/sys/arch/x68k/include/cpufunc.h netbsd-from-git/=
 sys/arch/x68k/include/cpufunc.h
 --- netbsd-from-cvs/sys/arch/x68k/include/cpufunc.h     1996-05-05 14:17:03=
 =2E000000000 +0200
 +++ netbsd-from-git/sys/arch/x68k/include/cpufunc.h     2021-06-10 09:43:48=
 =2E000000000 +0200
 @@ -1,4 +1,4 @@
 -/*     $NetBSD: cpufunc.h,v 1.1.1.1 1996/05/05 12:17:03 oki Exp $      */
 +/*     $NetBSD: cpufunc.h,v 1.1 1996/05/05 12:17:15 oki Exp $  */
 =20
  /*
   * Functions to provide access to special cpu instructions.
 diff -Nurp netbsd-from-cvs/sys/arch/x68k/include/ieeefp.h netbsd-from-git/s=
 ys/arch/x68k/include/ieeefp.h
 --- netbsd-from-cvs/sys/arch/x68k/include/ieeefp.h      1996-05-05 14:17:03=
 =2E000000000 +0200
 +++ netbsd-from-git/sys/arch/x68k/include/ieeefp.h      2021-06-10 09:43:48=
 =2E000000000 +0200
 @@ -1,4 +1,4 @@
 -/*     $NetBSD: ieeefp.h,v 1.1.1.1 1996/05/05 12:17:03 oki Exp $       */
 +/*     $NetBSD: ieeefp.h,v 1.1 1996/05/05 12:17:14 oki Exp $   */
 =20
  /* Just use the common m68k definition */
  #include <m68k/ieeefp.h>
 diff -Nurp netbsd-from-cvs/sys/arch/x68k/include/profile.h netbsd-from-git/=
 sys/arch/x68k/include/profile.h
 --- netbsd-from-cvs/sys/arch/x68k/include/profile.h     1996-05-05 14:17:03=
 =2E000000000 +0200
 +++ netbsd-from-git/sys/arch/x68k/include/profile.h     2021-06-10 09:43:48=
 =2E000000000 +0200
 @@ -1,3 +1,3 @@
 -/*     $NetBSD: profile.h,v 1.1.1.1 1996/05/05 12:17:03 oki Exp $      */
 +/*     $NetBSD: profile.h,v 1.1 1996/05/05 12:17:14 oki Exp $  */
 =20
  #include <m68k/profile.h>
 diff -Nurp netbsd-from-cvs/sys/arch/x68k/include/setjmp.h netbsd-from-git/s=
 ys/arch/x68k/include/setjmp.h
 --- netbsd-from-cvs/sys/arch/x68k/include/setjmp.h      1996-05-05 14:17:03=
 =2E000000000 +0200
 +++ netbsd-from-git/sys/arch/x68k/include/setjmp.h      2021-06-10 09:43:48=
 =2E000000000 +0200
 @@ -1,3 +1,3 @@
 -/*     $NetBSD: setjmp.h,v 1.1.1.1 1996/05/05 12:17:03 oki Exp $       */
 +/*     $NetBSD: setjmp.h,v 1.1 1996/05/05 12:17:15 oki Exp $   */
 =20
  #include <m68k/setjmp.h>



 > Maybe a timestamp getting set differently, unveiling an unnoticed makefile
 > bug?

 Timestamp handling (file-based vs. commit based) may indeed be an
 issue, but as it turned out, after tar-piping over a NetBSD CVS tree
 (this VM has no direct Internet connectivity) to the NetBSD VM (the
 same 9.2 freshly installed as for the previous GIT-based build), it
 failed as well.

 My build logs (from `script`) are here:

 GIT:
   tools:   https://lug-owl.de/~jbglaw/laminar/tools.log
   release: https://lug-owl.de/~jbglaw/laminar/release.log

 CVS:
   tools:   https://lug-owl.de/~jbglaw/laminar/tools-cvs.log
   release: https://lug-owl.de/~jbglaw/laminar/release-cvs.log

 MfG, JBG

 --=20

 --53uj6mijzn4d6pxg
 Content-Type: application/pgp-signature; name="signature.asc"

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

 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYMJXxQAKCRAdvV51g5nh
 u9zWAJ94Oz2G71/BM288dMacEgXhpJRylwCcD1jU+p1KMGcw+haiIc+op8V48Gw=
 =YdZ7
 -----END PGP SIGNATURE-----

 --53uj6mijzn4d6pxg--

From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Martin Husemann <martin@duskware.de>
Cc: Christos Zoulas <christos@zoulas.com>, gnats-bugs@netbsd.org,
	port-zaurus-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Sun, 13 Jun 2021 00:24:57 +0200

 --zixwbteuk43hfh2e
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Wed, 2021-06-09 11:35:19 +0200, Martin Husemann <martin@duskware.de> wro=
 te:
 > On Wed, Jun 09, 2021 at 10:47:37AM +0200, Jan-Benedict Glaw wrote:
 > >   Building tools worked, but building the release broke as it broke
 > > when building within the Linux (Debian) docker containers due to not
 > > finding gcov-iov.h.  So I guess something broke in the toolchain?
 > >=20
 > >   Logs can be found at:
 > >=20
 > > 	https://lug-owl.de/~jbglaw/laminar/tools.log
 > > 	https://lug-owl.de/~jbglaw/laminar/release.log
 >=20
 > Well, it works for the official builds (which are done from cvs source
 > trees), so it must be something git specific.
 >=20
 > Maybe a timestamp getting set differently, unveiling an unnoticed makefile
 > bug?

 I've now nearly fully automated a NetBSD 9.2 installation in Qemu
 (using the serial installer at
 ftp.netbsd.org:/pub/NetBSD/NetBSD-9.2/amd64/installation/cdrom/boot-com.iso,
 just to have it somewhat reproducible if it gets f*cked up for
 whatever reason), with proper bridged network, and will use that Qemu
 VM to also do test-builds of the NetBSD sources. One at a time, with
 Qemu's "-snapshot" option to keep the VM pristine.

   For preparation, I struggle a bit with CVS. I really don't want to
 do a fresh checkout hitting anoncvs.netbsd.org each time. I saw that
 `rsync anoncvs.netbsd.org::cvsroot/` has the repo available. Using a
 local copy of that pointed to by $CVSROOT should work, shouldn't it?

 Thanks,
   Jan-Benedict

 --=20

 --zixwbteuk43hfh2e
 Content-Type: application/pgp-signature; name="signature.asc"

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

 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYMU0NAAKCRAdvV51g5nh
 uwTVAJ9NI4nVHn+4xGYEeh9KxE3gMsD7xwCfeub0vevxzcrfLQLk7jGTcXli7jc=
 =kKnN
 -----END PGP SIGNATURE-----

 --zixwbteuk43hfh2e--

From: Christos Zoulas <christos@zoulas.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Martin Husemann <martin@duskware.de>,
 gnats-bugs@netbsd.org,
 port-zaurus-maintainer@netbsd.org,
 gnats-admin@netbsd.org,
 netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Sat, 12 Jun 2021 18:28:55 -0400

 --Apple-Mail=_ACAB6C02-4236-4D06-AE7F-AADBE0DDA657
 Content-Type: multipart/alternative;
 	boundary="Apple-Mail=_265B1AB0-7E90-4EC2-9B0A-A4ECDDB8FE30"


 --Apple-Mail=_265B1AB0-7E90-4EC2-9B0A-A4ECDDB8FE30
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/plain;
 	charset=us-ascii

 Sure, that works too.

 christos

 > On Jun 12, 2021, at 6:24 PM, Jan-Benedict Glaw <jbglaw@lug-owl.de> =
 wrote:
 >=20
 > Signed PGP part
 > On Wed, 2021-06-09 11:35:19 +0200, Martin Husemann <martin@duskware.de =
 <mailto:martin@duskware.de>> wrote:
 >> On Wed, Jun 09, 2021 at 10:47:37AM +0200, Jan-Benedict Glaw wrote:
 >>>  Building tools worked, but building the release broke as it broke
 >>> when building within the Linux (Debian) docker containers due to not
 >>> finding gcov-iov.h.  So I guess something broke in the toolchain?
 >>>=20
 >>>  Logs can be found at:
 >>>=20
 >>> 	https://lug-owl.de/~jbglaw/laminar/tools.log
 >>> 	https://lug-owl.de/~jbglaw/laminar/release.log
 >>=20
 >> Well, it works for the official builds (which are done from cvs =
 source
 >> trees), so it must be something git specific.
 >>=20
 >> Maybe a timestamp getting set differently, unveiling an unnoticed =
 makefile
 >> bug?
 >=20
 > I've now nearly fully automated a NetBSD 9.2 installation in Qemu
 > (using the serial installer at
 > ftp.netbsd.org =
 <http://ftp.netbsd.org/>:/pub/NetBSD/NetBSD-9.2/amd64/installation/cdrom/b=
 oot-com.iso,
 > just to have it somewhat reproducible if it gets f*cked up for
 > whatever reason), with proper bridged network, and will use that Qemu
 > VM to also do test-builds of the NetBSD sources. One at a time, with
 > Qemu's "-snapshot" option to keep the VM pristine.
 >=20
 >  For preparation, I struggle a bit with CVS. I really don't want to
 > do a fresh checkout hitting anoncvs.netbsd.org =
 <http://anoncvs.netbsd.org/> each time. I saw that
 > `rsync anoncvs.netbsd.org <http://anoncvs.netbsd.org/>::cvsroot/` has =
 the repo available. Using a
 > local copy of that pointed to by $CVSROOT should work, shouldn't it?
 >=20
 > Thanks,
 >  Jan-Benedict
 >=20
 > --
 >=20
 > <sanitizer.log>


 --Apple-Mail=_265B1AB0-7E90-4EC2-9B0A-A4ECDDB8FE30
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/html;
 	charset=us-ascii

 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
 charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
 -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Sure,=
  that works too.<div class=3D""><br class=3D""></div><div =
 class=3D"">christos<br class=3D""><div><br class=3D""><blockquote =
 type=3D"cite" class=3D""><div class=3D"">On Jun 12, 2021, at 6:24 PM, =
 Jan-Benedict Glaw &lt;<a href=3D"mailto:jbglaw@lug-owl.de" =
 class=3D"">jbglaw@lug-owl.de</a>&gt; wrote:</div><br =
 class=3D"Apple-interchange-newline"><div class=3D""><meta =
 charset=3D"UTF-8" class=3D""><div class=3D"content-isolator__container" =
 style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
 12px; font-style: normal; font-variant-caps: normal; font-weight: =
 normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
 text-transform: none; white-space: normal; word-spacing: 0px; =
 -webkit-text-stroke-width: 0px; text-decoration: none;"><div =
 class=3D"protected-part"><div class=3D"protected-title">Signed PGP =
 part</div><div class=3D"protected-content">On Wed, 2021-06-09 11:35:19 =
 +0200, Martin Husemann &lt;<a href=3D"mailto:martin@duskware.de" =
 class=3D"">martin@duskware.de</a>&gt; wrote:<br class=3D""><blockquote =
 type=3D"cite" class=3D"">On Wed, Jun 09, 2021 at 10:47:37AM +0200, =
 Jan-Benedict Glaw wrote:<br class=3D""><blockquote type=3D"cite" =
 class=3D"">&nbsp;Building tools worked, but building the release broke =
 as it broke<br class=3D"">when building within the Linux (Debian) docker =
 containers due to not<br class=3D"">finding gcov-iov.h. &nbsp;So I guess =
 something broke in the toolchain?<br class=3D""><br class=3D"">&nbsp;Logs =
 can be found at:<br class=3D""><br class=3D""><span =
 class=3D"Apple-tab-span" style=3D"white-space: pre;">	</span><a =
 href=3D"https://lug-owl.de/~jbglaw/laminar/tools.log" =
 class=3D"">https://lug-owl.de/~jbglaw/laminar/tools.log</a><br =
 class=3D""><span class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
 </span>https://lug-owl.de/~jbglaw/laminar/release.log<br =
 class=3D""></blockquote><br class=3D"">Well, it works for the official =
 builds (which are done from cvs source<br class=3D"">trees), so it must =
 be something git specific.<br class=3D""><br class=3D"">Maybe a =
 timestamp getting set differently, unveiling an unnoticed makefile<br =
 class=3D"">bug?<br class=3D""></blockquote><br class=3D"">I've now =
 nearly fully automated a NetBSD 9.2 installation in Qemu<br =
 class=3D"">(using the serial installer at<br class=3D""><a =
 href=3D"http://ftp.netbsd.org/" =
 class=3D"">ftp.netbsd.org</a>:/pub/NetBSD/NetBSD-9.2/amd64/installation/cd=
 rom/boot-com.iso,<br class=3D"">just to have it somewhat reproducible if =
 it gets f*cked up for<br class=3D"">whatever reason), with proper =
 bridged network, and will use that Qemu<br class=3D"">VM to also do =
 test-builds of the NetBSD sources. One at a time, with<br =
 class=3D"">Qemu's "-snapshot" option to keep the VM pristine.<br =
 class=3D""><br class=3D"">&nbsp;For preparation, I struggle a bit with =
 CVS. I really don't want to<br class=3D"">do a fresh checkout =
 hitting<span class=3D"Apple-converted-space">&nbsp;</span><a =
 href=3D"http://anoncvs.netbsd.org/" class=3D"">anoncvs.netbsd.org</a><span=
  class=3D"Apple-converted-space">&nbsp;</span>each time. I saw that<br =
 class=3D"">`rsync<span class=3D"Apple-converted-space">&nbsp;</span><a =
 href=3D"http://anoncvs.netbsd.org/" =
 class=3D"">anoncvs.netbsd.org</a>::cvsroot/` has the repo available. =
 Using a<br class=3D"">local copy of that pointed to by $CVSROOT should =
 work, shouldn't it?<br class=3D""><br class=3D"">Thanks,<br =
 class=3D"">&nbsp;Jan-Benedict<br class=3D""><br class=3D"">--<span =
 class=3D"Apple-converted-space">&nbsp;</span><br =
 class=3D""></div></div><br class=3D""><span =
 id=3D"cid:B700F5A6-97DF-4120-92E4-02686DBC3F85">&lt;sanitizer.log&gt;</spa=
 n></div></div></blockquote></div><br class=3D""></div></body></html>=

 --Apple-Mail=_265B1AB0-7E90-4EC2-9B0A-A4ECDDB8FE30--

 --Apple-Mail=_ACAB6C02-4236-4D06-AE7F-AADBE0DDA657
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 	filename=signature.asc
 Content-Type: application/pgp-signature;
 	name=signature.asc
 Content-Description: Message signed with OpenPGP

 -----BEGIN PGP SIGNATURE-----
 Comment: GPGTools - http://gpgtools.org

 iF0EARECAB0WIQS+BJlbqPkO0MDBdsRxESqxbLM7OgUCYMU1JwAKCRBxESqxbLM7
 OkK6AKDPvbu6IJi7c0jHogrHQ84keOWQBACgg1aGh0Ebcc2QxeOguL8l7n223HQ=
 =9j4+
 -----END PGP SIGNATURE-----

 --Apple-Mail=_ACAB6C02-4236-4D06-AE7F-AADBE0DDA657--

From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Martin Husemann <martin@duskware.de>
Cc: Christos Zoulas <christos@zoulas.com>, gnats-bugs@netbsd.org,
	port-zaurus-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Tue, 15 Jun 2021 14:27:48 +0200

 --guoszkdoeiodrwie
 Content-Type: multipart/mixed; boundary="2qnpn3vygsri2lmi"
 Content-Disposition: inline


 --2qnpn3vygsri2lmi
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable

 On Wed, 2021-06-09 11:35:19 +0200, Martin Husemann <martin@duskware.de> wro=
 te:
 > On Wed, Jun 09, 2021 at 10:47:37AM +0200, Jan-Benedict Glaw wrote:
 > >   Building tools worked, but building the release broke as it broke
 > > when building within the Linux (Debian) docker containers due to not
 > > finding gcov-iov.h.  So I guess something broke in the toolchain?
 > >=20
 > >   Logs can be found at:
 > >=20
 > > 	https://lug-owl.de/~jbglaw/laminar/tools.log
 > > 	https://lug-owl.de/~jbglaw/laminar/release.log
 >=20
 > Well, it works for the official builds (which are done from cvs source
 > trees), so it must be something git specific.
 >=20
 > Maybe a timestamp getting set differently, unveiling an unnoticed makefile
 > bug?

 Whee!  So I've not got a quite pristinely installed NetBSD 9.2
 (installed via boot-com.iso), just a SSH key for root added. From the
 Laminar CI job scheduler, the following script is called.
 JOB=3Dnnetbsd-evbarm-earmv5hfeb, so BUILD_MACHINE=3Devbarm and
 BUILD_ARCH=3Dearmv5hfeb.


 =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=3D=3D=3D=3D=3D=3D=3D=3D
 #!/usr/bin/env bash

 set -ex

 laminar_jb_tool_dir=3D"/var/lib/laminar/cfg/jb-helpers"
 netbsd_src_tree=3D/var/cache/git/NetBSD-src-in-cvs

 BUILD_MACHINE=3D"$(echo "${JOB}" | cut -f 2 -d -)"
 BUILD_ARCH=3D"$(   echo "${JOB}" | cut -f 3 -d -)"

 function Scp() {
 	scp -i "${laminar_jb_tool_dir}/netbsd-ssh-key" -o StrictHostKeyChecking=3D=
 no -o UserKnownHostsFile=3D/dev/null "${@}"
 }

 function Ssh() {
 	ssh -i "${laminar_jb_tool_dir}/netbsd-ssh-key" -o StrictHostKeyChecking=3D=
 no -o UserKnownHostsFile=3D/dev/null "${@}"
 }

 (
 	cd "${laminar_jb_tool_dir}"
 	./run_netbsd_amd64_qemu.sh
 )


 # Copy CVS Tree.
 ( cd "${netbsd_src_tree}" && tar cf - .) | Ssh root@netbsd2 "cd /root && mk=
 dir NetBSD-src-in-cvs && cd NetBSD-src-in-cvs && tar xf -"

 set +e
 Ssh root@netbsd2 "BUILD_MACHINE=3D'${BUILD_MACHINE}' BUILD_ARCH=3D'${BUILD_=
 ARCH}' sh" << 'EOF'
 	export PKG_PATH=3D"http://ftp.NetBSD.org/pub/pkgsrc/packages/$(uname -s)/$=
 (uname -m)/$(uname -r)/All"
 	export PATH=3D"/sbin:/usr/sbin:/bin:/usr/bin:/usr/pkg/sbin:/usr/pkg/bin:/u=
 sr/X11R7/bin:/usr/local/sbin:/usr/local/bin:$PATH"
 	set
 	export
 	pkg_add moreutils
 	pkg_add bash
 	cd /root/NetBSD-src-in-cvs
 	ls -l
 	cat > log_execute << 'LOG_EXECUTE'
 #!/usr/bin/env bash

 	NAME=3D"$( echo "${1}" | sed -e 's/%/&%/g')"; shift
 	TS_FORMAT=3D"[${NAME} %Y-%m-%d %H:%M:%S]"

 	"${@}" 2>&1 | ts "${TS_FORMAT}"
 	exit "${PIPESTATUS[0]}"
 LOG_EXECUTE
 	chmod +x log_execute
 	./log_execute 'bld tls' ./build.sh -P -U    -m "${BUILD_MACHINE}" -a "${BU=
 ILD_ARCH}" -E -D "/root/DEST-${BUILD_MACHINE}-${BUILD_ARCH}" -R "/root/REL-=
 ${BUILD_MACHINE}-${BUILD_ARCH}" tools     && \
 	./log_execute 'bld rls' ./build.sh -P -U -u -m "${BUILD_MACHINE}" -a "${BU=
 ILD_ARCH}" -E -D "/root/DEST-${BUILD_MACHINE}-${BUILD_ARCH}" -R "/root/REL-=
 ${BUILD_MACHINE}-${BUILD_ARCH}" release   && \
 	./log_execute 'bld iso' ./build.sh -P -U -u -m "${BUILD_MACHINE}" -a "${BU=
 ILD_ARCH}" -E -D "/root/DEST-${BUILD_MACHINE}-${BUILD_ARCH}" -R "/root/REL-=
 ${BUILD_MACHINE}-${BUILD_ARCH}" iso-image
 	RET=3D$?
 	poweroff < /dev/null > /dev/null 2>&1 &
 	exit $RET
 EOF
 =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

 So basically, the NetBSD VM is started (with a snapshot overlay to
 keep it clean), a freshly checked-out CVS tree is tar'ed over and
 built. (I only scheduled one variant up to now, this can be found at
 http://toolchain2.lug-owl.de:8080/jobs/nnetbsd-evbarm-earmv5hfeb, the
 log file is
 http://toolchain2.lug-owl.de:8080/log/nnetbsd-evbarm-earmv5hfeb/1 .

   That's as fresh as it gets, and fails:

 [bld rls 2021-06-15 11:27:06] /root/NetBSD-src-in-cvs/obj/tooldir.NetBSD-9.=
 2-amd64/bin/armeb--netbsdelf-eabihf-c++ -O2 -fdebug-prefix-map=3D\$DESTDIR=
 =3D -fdebug-prefix-map=3D\$NETBSDSRCDIR=3D/usr/src -fdebug-prefix-map=3D\$X=
 11SRCDIR=3D/usr/xsrc -fdebug-regex-map=3D'/usr/src/(.*)/obj$=3D/usr/obj/\1'=
  -fdebug-regex-map=3D'/usr/src/(.*)/obj/(.*)=3D/usr/obj/\1/\2' -fdebug-rege=
 x-map=3D'/usr/src/(.*)/obj\..*=3D/usr/obj/\1' -fdebug-regex-map=3D'/usr/src=
 /(.*)/obj\..*/(.*)=3D/usr/obj/\1/\2' -Wall -Wpointer-arith -Wno-sign-compar=
 e -Wa,--fatal-warnings -Werror   -fPIE -Wno-narrowing -Wno-unused -std=3Dgn=
 u++98 -fdebug-prefix-map=3D\$DESTDIR=3D -fdebug-prefix-map=3D\$NETBSDSRCDIR=
 =3D/usr/src -fdebug-prefix-map=3D\$X11SRCDIR=3D/usr/xsrc -fdebug-regex-map=
 =3D'/usr/src/(.*)/obj$=3D/usr/obj/\1' -fdebug-regex-map=3D'/usr/src/(.*)/ob=
 j/(.*)=3D/usr/obj/\1/\2' -fdebug-regex-map=3D'/usr/src/(.*)/obj\..*=3D/usr/=
 obj/\1' -fdebug-regex-map=3D'/usr/src/(.*)/obj\..*/(.*)=3D/usr/obj/\1/\2' -=
 Wno-stack-protector -fno-exceptions -fno-rtti -fasynchronous-unwind-tables =
   -I. -I/root/NetBSD-src-in-cvs/external/gpl3/gcc.old/usr.bin/backend/../gc=
 c/arch/earmhfeb -DIN_GCC -DHAVE_CONFIG_H -I/root/NetBSD-src-in-cvs/external=
 /gpl3/gcc.old/dist/gcc -I/root/NetBSD-src-in-cvs/external/gpl3/gcc.old/dist=
 /gcc/. -I/root/NetBSD-src-in-cvs/external/gpl3/gcc.old/dist/gcc/../include =
 -I/root/NetBSD-src-in-cvs/external/gpl3/gcc.old/dist/gcc/../libcpp/include =
 -I/root/NetBSD-src-in-cvs/external/gpl3/gcc.old/dist/gcc/../libdecnumber -I=
 /root/NetBSD-src-in-cvs/external/gpl3/gcc.old/dist/gcc/../libdecnumber/dpd =
 -I/root/NetBSD-src-in-cvs/external/gpl3/gcc.old/dist/gcc/../libbacktrace -D=
 TARGET_NAME=3D\"armeb--netbsdelf-eabihf\" -I/root/NetBSD-src-in-cvs/externa=
 l/gpl3/gcc.old/dist/libgcc -I/root/NetBSD-src-in-cvs/external/gpl3/gcc.old/=
 usr.bin/backend/../../lib/libgcc/libgcov/arch/earmv5hfeb --sysroot=3D/root/=
 DEST-evbarm-earmv5hfeb -DLOCALEDIR=3D\"/usr/share/locale\" -DNETBSD_NATIVE =
 -I. -DENABLE_SHARED_LIBGCC -Wp,-iremap,/root/DEST-evbarm-earmv5hfeb: -Wp,-f=
 no-canonical-system-headers -Wp,-iremap,/root/NetBSD-src-in-cvs:/usr/src -W=
 p,-iremap,/usr/xsrc:/usr/xsrc  -c    /root/NetBSD-src-in-cvs/external/gpl3/=
 gcc.old/dist/gcc/auto-profile.c -o auto-profile.o
 [bld rls 2021-06-15 11:27:06] In file included from /root/NetBSD-src-in-cvs=
 /external/gpl3/gcc.old/dist/gcc/auto-profile.c:34:
 [bld rls 2021-06-15 11:27:06] /root/NetBSD-src-in-cvs/external/gpl3/gcc.old=
 /dist/gcc/gcov-io.h:215:10: fatal error: gcov-iov.h: No such file or direct=
 ory
 [bld rls 2021-06-15 11:27:06]   215 | #include "gcov-iov.h"
 [bld rls 2021-06-15 11:27:06]       |          ^~~~~~~~~~~~
 [bld rls 2021-06-15 11:27:06] compilation terminated.

 I really think there's some leftover from a former successful run that
 enables new builds...

 Thanks,
   Jan-Benedict
 PS: I'll attach the expect script that I used/created to install this
 NetBSD instance.
 --=20

 --2qnpn3vygsri2lmi
 Content-Type: application/x-sh
 Content-Disposition: attachment; filename="create_netbsd_amd64_qemu.sh"
 Content-Transfer-Encoding: quoted-printable

 #!/usr/bin/env bash=0A=0A# apt-get install qemu-system-x86 qemu-utils expec=
 t=0A=0ABASEDIR=3D"/mnt/sdb1/netbsd-amd64_qemu"=0A# ftp.netbsd.org:/pub/NetB=
 SD/NetBSD-9.2/amd64/installation/cdrom/boot-com.iso=0AISO=3D"${BASEDIR}/Net=
 BSD-9.2-amd64.iso"=0AISO=3D"${BASEDIR}/boot-com.iso"=0AHDA=3D"${BASEDIR}/hd=
 a.qcow2"=0AHDA_SIZE=3D"32G"=0APIDFILE=3D"${BASEDIR}/qemu.pid"=0A=0A# Create=
  basedir. Own to laminar so that we can create snapshot images=0A# therein.=
  A bit clumpsy though...=0Amkdir -p "${BASEDIR}"=0Achown laminar.laminar "$=
 {BASEDIR}"=0A=0A# Initial Image. Probably quite too large, but at least CoW=
 =2E After initial=0A# installation, it's only used as a base image for over=
 laying snapshots.=0Aqemu-img create -f qcow2 "${HDA}" "${HDA_SIZE}"=0A=0Aqe=
 mu-system-x86_64	-m 4096						\=0A			-enable-kvm					\=0A			-drive if=3Dvir=
 tio,file=3D${HDA},format=3Dqcow2	\=0A			-device e1000,netdev=3Dvm0,mac=3Dcc=
 :32:e5:17:b4:a4	\=0A			-netdev bridge,br=3Dbr0,id=3Dvm0			\=0A			-cdrom "${=
 ISO}"					\=0A			-serial mon:telnet:127.0.0.1:6665,server,wait	\=0A			-daem=
 onize					\=0A			-vga none					\=0A			-pidfile "${PIDFILE}" > /dev/null 2>&=
 1		&=0A=0A# Wait for Qemu to start up.=0Asleep 2=0A=0A# Install NetBSD.=0Ae=
 xpect -d <<- 'EOF'=0Aset timeout 3600=0Aspawn telnet localhost 6665=0A=0Aex=
 pect "vt220"=0Asleep 5=0Asend -- "\r"=0A=0Aexpect "Installation messages in=
 "=0Asleep 1=0Asend -- "a\r"=0A=0Aexpect "Install NetBSD to hard disk"=0Asle=
 ep 1=0Asend -- "a\r"=0A=0Aexpect "Yes or no"=0Asleep 1=0Asend -- "b\r"=0A=
 =0Aexpect "Available disks"=0Asleep 1=0Asend -- "\r"=0A=0Aexpect "Guid Part=
 ition Table"=0Asleep 1=0Asend -- "a\r"=0A=0Aexpect "This is the correct geo=
 metry"=0Asleep 1=0Asend -- "a\r"=0A=0Aexpect "Use default partition sizes"=
 =0Asleep 1=0Asend -- "b\r"=0A=0Aexpect "Partition sizes ok"=0Asleep 1=0Asen=
 d -- "x\r"=0A=0Aexpect "Yes or no"=0Asleep 1=0Asend -- "b\r"=0A=0Aexpect "B=
 ootblocks selection"=0Asleep 1=0Asend -- "b\r"=0Asleep 1=0Asend -- "f\r"=0A=
 =0Aexpect "Set serial baud rate"=0Asleep 1=0Asend -- "\r"=0A=0Aexpect ""=0A=
 sleep 1=0Asend -- "x\r"=0A=0Aexpect "Installation without X11"=0Asleep 1=0A=
 send -- "b\r"=0A=0Aexpect "Install from"=0Asleep 1=0Asend -- "b\r"=0A=0Aexp=
 ect "Configure network"=0Asleep 1=0Asend -- "j\r"=0A=0Aexpect "Available in=
 terfaces"=0Asleep 1=0Asend -- "a\r"=0A=0Aexpect "autoselect"=0Asleep 1=0Ase=
 nd -- "\r"=0A=0Aexpect "Perform autoconfiguration"=0Asleep 1=0Asend -- "a\r=
 "=0A=0Aexpect "Are they OK"=0Asleep 1=0Asend -- "a\r"=0Asleep 1=0Asend -- "=
 x\r"=0A=0Aexpect "Is the network information you entered accurate for this =
 machine"=0Asleep 1=0Asend -- "a\r"=0A=0Aexpect "Hit enter to continue"=0Asl=
 eep 1=0Asend -- "\r"=0A=0Aexpect "Change root password"=0Asleep 1=0Asend --=
  "d\r"=0A=0Aexpect "Yes or no"=0Asleep 1=0Asend -- "a\r"=0A=0Aexpect "New p=
 assword"=0Asleep 1=0Asend -- "BuildVm\r"=0A=0Aexpect "Retype new password"=
 =0Asleep 1=0Asend -- "BuildVm\r"=0A=0Aexpect "Enable sshd"=0Asleep 1=0Asend=
  -- "g\r"=0A=0Aexpect "Enable ntpd"=0Asleep 1=0Asend -- "h\r"=0A=0Aexpect "=
 Finished configuring"=0Asleep 1=0Asend -- "x\r"=0A=0A#  At a minimum, you s=
 hould edit /etc/rc.conf to match your needs.  See=0A# /etc/defaults/rc.conf=
  for the default values.=0A=0Aexpect "Hit enter to continue"=0Asleep 1=0Ase=
 nd -- "\r"=0A=0Aexpect "Utility menu"=0Asleep 1=0Asend -- "e\r"=0A=0Aexpect=
  "Run /bin/sh"=0Asleep 1=0Asend -- "a\r"=0A=0Aexpect "#"=0Asend -- "mount /=
 dev/dk0 /mnt\r"=0Asleep 1=0Aexpect "#"=0Asend -- "mkdir /mnt/root/.ssh\r"=
 =0Asleep 1=0Aexpect "#"=0Asend -- "echo 'ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA=
 ABgQDRxDbznSLIvujpJO/wg944U64HRvG9e4f3Hfody2f2vFQFWuix8SPNUIm+TzO77M0vfw0Kq=
 vVpyv3sF611hSFsrRnXU8N4ke+AZ99eColOsiiQ84fF5vAN9FwjdrSdg1qDql8ZAC/HVb/yyKhV=
 4UeOGRG166GZkizXu5KQlSNRwHBpLYEb2KR1Sqs6y0s1zWh4pFmNB4OHiAIdka1eO/pmXiqqVDk=
 6vq4FOBel+7CZ/gvSaCXsU1Fjhxz5V3g1zSnVpy627HXdOxFZNg6Cl8P8ufEZ64M0Iv/ppWwegz=
 wuJRsusm9DwP0LHFuou9RB/5kTExaXhlPwRAdWXS0KQ2NTL1Mbtso5VQAUJcthFYjpmnW35p5Mf=
 +z00AAVITPf3bawD5+WWin1FSW7RRRerw6fXJf3AzmN5MROxkBNxFS3wagru7Xdz46OxmAFFy+V=
 bu4z/ZD3l9rgcVImr4jmKzIxdAEXSj5dBm7wytOSBkEVgM4EJY345IMLA8rcEDABhEE=3D root=
 @spock' > /mnt/root/.ssh/authorized_keys\r"=0Asleep 1=0Aexpect "#"=0Asend -=
 - "chmod go-r /mnt/root/.ssh/authorized_keys\r"=0Asleep 1=0Aexpect "#"=0Ase=
 nd -- "umount /mnt\r"=0Asleep 1=0Aexpect "#"=0Asend -- "poweroff\r"=0A=0Aex=
 pect eof=0Asleep 1=0AEOF=0A=0Asleep 10=0Akill "$(cat "${PIDFILE}")"=0A
 --2qnpn3vygsri2lmi--

 --guoszkdoeiodrwie
 Content-Type: application/pgp-signature; name="signature.asc"

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

 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYMicwgAKCRAdvV51g5nh
 uy7eAJ9nQt/mYKnu61eQH3BWOd811F57WQCeIN5mwMPcQ0wMzRNQH8QHnKkMsdM=
 =8NV+
 -----END PGP SIGNATURE-----

 --guoszkdoeiodrwie--

From: Martin Husemann <martin@duskware.de>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Christos Zoulas <christos@zoulas.com>, gnats-bugs@netbsd.org,
	port-zaurus-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Tue, 15 Jun 2021 15:05:04 +0200

 On Tue, Jun 15, 2021 at 02:27:48PM +0200, Jan-Benedict Glaw wrote:
 > I really think there's some leftover from a former successful run that
 > enables new builds...

 No, we only do clean builds on the auto build cluster. It could leak in
 from the host headers though. Most other arm variants specify a proper
 path for that header, but for v5 (the default evbarm architecture) it
 does not match (dir is arm, -I is evbarmv5 or similar).

 Martin

From: matthew green <mrg@eterna.com.au>
To: Martin Husemann <martin@duskware.de>
Cc: Christos Zoulas <christos@zoulas.com>, gnats-bugs@netbsd.org,
    port-zaurus-maintainer@netbsd.org, gnats-admin@netbsd.org,
    netbsd-bugs@netbsd.org, Jan-Benedict Glaw <jbglaw@lug-owl.de>
Subject: re: port-zaurus/56238: Several ARM-Variants seem to miss gcov-iov.h
Date: Wed, 16 Jun 2021 01:47:04 +1000

 Martin Husemann writes:
 > On Tue, Jun 15, 2021 at 02:27:48PM +0200, Jan-Benedict Glaw wrote:
 > > I really think there's some leftover from a former successful run that
 > > enables new builds...
 >
 > No, we only do clean builds on the auto build cluster. It could leak in
 > from the host headers though. Most other arm variants specify a proper
 > path for that header, but for v5 (the default evbarm architecture) it
 > does not match (dir is arm, -I is evbarmv5 or similar).

 the dir should be "earm".  "arm" and "armeb" subdirs are
 obsolete and should be removed.


 .mrg.

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.46 2020/01/03 16:35:01 leot Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2020 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.