doc/CHANGES typo (2018)

[Geoff Wing]

Hi,
there is a wrong year in doc/CHANGES.

Regards,
Geoff

Index: doc/CHANGES
===
RCS file: /cvsroot/src/doc/CHANGES,v
retrieving revision 1.2587
diff -u -r1.2587 CHANGES
--- doc/CHANGES 2 Oct 2019 11:18:55 -   1.2587
+++ doc/CHANGES 3 Oct 2019 03:37:04 -
@@ -24,7 +24,7 @@
 # 
 
 Changes from NetBSD 9.0 to NetBSD 10.0:
-   openldap: Import 2.4.48. [christos 20180808]
+   openldap: Import 2.4.48. [christos 20190808]
usbnet(9): Add common framework for USB network devices.  Port the
axe(4), axen(4), cdce(4), cue(4), mue(4), smsc(4), udav(4),
ure(4), url(4), and urndis(4) drivers fixing many bugs and

Automated report: NetBSD-current/i386 build success

[NetBSD Test Fixture]

The NetBSD-current/i386 build is working again.

The following commits were made between the last failed build and the
successful build:

2019.10.03.01.15.19 sevan src/usr.bin/nc/netcat.c,v 1.6
2019.10.03.01.34.31 mrg src/etc/mtree/NetBSD.dist.base,v 1.203

Log files can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2019.10.html#2019.10.03.01.34.31

Automated report: NetBSD-current/i386 build failure

[NetBSD Test Fixture]

This is an automatically generated notice of a NetBSD-current/i386
build failure.

The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2019.10.03.00.59.50.

An extract from the build.sh output follows:

   === Removing obsolete files ===
AWK=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbawk 
 DB=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbdb  
 HOST_SH=/bin/sh 
MAKE=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbmake   

PWD_MKDB=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbpwd_mkdb   
SED=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbsed 
STAT=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbstat /bin/sh 
/tmp/bracket/build/2019.10.03.00.59.50-i386/obj/usr.sbin/postinstall/postinstall
   -m i386 -a i386 -s /tmp/bracket/build/2019.10.03.00.59.50-i386/src  -d 
/tmp/bracket/build/2019.10.03.00.59.50-i386/destdir/ fix obsolete_stand
Source directory: /tmp/bracket/build/2019.10.03.00.59.50-i386/src
Target directory: /tmp/bracket/build/2019.10.03.00.59.50-i386/destdir/
obsolete_stand fix:
postinstall fixes passed: obsolete_stand
postinstall fixes failed:
   ===
checkflist ===> distrib/sets
--- check_DESTDIR ---
--- checkflist ---
cd /tmp/bracket/build/2019.10.03.00.59.50-i386/src/distrib/sets &&  
DESTDIR=/tmp/bracket/build/2019.10.03.00.59.50-i386/destdir  MACHINE=i386  
MACHINE_ARCH=i386  
AWK=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbawk  
CKSUM=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbcksum  
DB=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbdb  
EGREP=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbgrep\ -E  
HOST_SH=/bin/sh  
MAKE=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbmake  
MKTEMP=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbmktemp  
MTREE=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbmtree  
PAX=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbpax  
COMPRESS_PROGRAM=gzip  GZIP=-n  XZ_OPT=-9  TAR_SUFF=tgz  
PKG_CREATE=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbpkg_create  
SED=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbsed  
TSORT=/tmp/bracket/build/2019.10.03.00.59.50-i386/tools/bin/nbtsort\ -q  
 /bin/sh 
/tmp/bracket/build/2019.10.03.00.59.50-i386/src/distrib/sets/checkflist  -L 
base  -M /tmp/bracket/build/2019.10.03.00.59.50-i386/destdir/METALOG.sanitised
==  2 missing files in DESTDIR  
Files in flist but missing from DESTDIR.
File wasn't installed ?
--
./usr/include/gcc-8
./usr/include/gcc-8/sanitizer
  end of 2 missing files  ==
*** [checkflist] Error code 1
nbmake[2]: stopped in 
/tmp/bracket/build/2019.10.03.00.59.50-i386/src/distrib/sets

The following commits were made between the last successful build and
the failed build:

2019.10.02.23.15.09 kamil src/tests/lib/libc/sys/t_ptrace_wait.c,v 1.134
2019.10.03.00.59.49 mrg src/distrib/sets/lists/base/ad.mips,v 1.80
2019.10.03.00.59.49 mrg src/distrib/sets/lists/base/mi,v 1.1218
2019.10.03.00.59.50 mrg src/distrib/sets/lists/base/shl.mi,v 1.874
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.aarch64,v 1.33
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.arm,v 1.98
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.hppa,v 1.16
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.m68k,v 1.62
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.mips,v 1.83
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.powerpc,v 1.95
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.riscv,v 1.15
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/ad.sh3,v 1.43
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.alpha,v 1.77
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.amd64,v 1.274
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.hppa,v 1.13
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.i386,v 1.192
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.ia64,v 1.7
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.or1k,v 1.9
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.sparc,v 1.98
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.sparc64,v 1.210
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/md.vax,v 1.51
2019.10.03.00.59.50 mrg src/distrib/sets/lists/comp/mi,v 1.2289
2019.10.03.00.59.50 mrg src/distrib/sets/lists/debug/ad.mips,v 1.74
2019.10.03.00.59.50 mrg src/distrib/sets/lists/debug/shl.mi,v 1.233

Log files can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2019.10.html#2019.10.03.00.59.50

re: retiring arm oabi support for new things

[matthew green]

i think we're missing -m evbarm -a earmv4 builds, which should
create an evbarm set targetting our speical eabi on armv4, and
that "normal" earm builds should elide them.  shouldn't be too
hard, we already collect them eg, into $EVBARM_BOARDS.armv4.

thanks for pointing that out!


.mrg.

re: retiring arm oabi support for new things

[matthew green]

> >netbsd 9 will ship without any targets with oabi as the
> >default, and most of the existing ports were already
> >switched to eabi (epoc32 and acorn32 only.)
> >
> >as part of this, i'm going to stop providing the ability
> >to build any arm with oabi -- turn off the MKCOMPAT for
> >all arm ports, so the oabi libraries are not provided
> >anymore, turn off the oabi ld.elf.so, etc.
> 
> Are you going to change the compiler target name as part of this ?
> 
> I'm currently struggling with an autoconf script that is getting
> confused by the -eabihf part of the armv7--netbsdelf-eabihf name.

i wasn't going to change any names.

target names have meaning and shouldn't change, it's way too
late to change this now.

patch the script to be smarter is the only real option or we
would break all the existing things that already know what
each target is is the only sane response..


.mrg.

Re: netbsd-9 MKDEBUG{,_LIB) build vs debug set lists?

[John D. Baker]

On Tue, 1 Oct 2019, John D. Baker wrote:

> A non-update build of amd64 is underway
> but has not reached the "checkflist" stage yet.

And it has just passed the "checkflist" stage.  In case anyone runs into
this as well, a clean (non-update) build appears to put it right again.

-- 
|/"\ John D. Baker, KN5UKS   NetBSD Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSDFreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

Re: retiring arm oabi support for new things

[Robert Swindells]

matthew green  wrote:
>netbsd 9 will ship without any targets with oabi as the
>default, and most of the existing ports were already
>switched to eabi (epoc32 and acorn32 only.)
>
>as part of this, i'm going to stop providing the ability
>to build any arm with oabi -- turn off the MKCOMPAT for
>all arm ports, so the oabi libraries are not provided
>anymore, turn off the oabi ld.elf.so, etc.

Are you going to change the compiler target name as part of this ?

I'm currently struggling with an autoconf script that is getting
confused by the -eabihf part of the armv7--netbsdelf-eabihf name.

I have been building arm targets with MKCOMPAT=no for a long time now so
no problem with the proposed change.

Re: /rescue is a separate set now

[Piotr Meyer]

On Wed, Oct 02, 2019 at 11:31:32AM +, m...@netbsd.org wrote:

> I had to change a lot of installers and images in distrib/, I hope I
> didn't miss one. Let me know if one doesn't install /rescue now.

Nice. Is it possible to push it into netbsd-9?

-- 
Piotr 'aniou' Meyer

/rescue is a separate set now

[maya]

Hi folks,

I've split out /rescue into its own set.
This is intended to make updates safer. It's not necessary to update it
at all, and if something goes wrong in your update, you can boot
/rescue/init and recover, as described here:
https://www.netbsd.org/docs/current/#recovering-via-rescue

I had to change a lot of installers and images in distrib/, I hope I
didn't miss one. Let me know if one doesn't install /rescue now.