Re: GCC 10 available for testing etc. in -current.

2021-04-18 Thread Michael van Elst
ll...@must-have-coffee.gen.nz (Lloyd Parkes) writes:

>On 17/04/21 6:30 pm, Lloyd Parkes wrote:
>> I am using the Mercurial repository at https://anonhg.NetBSD.org/src 
>> for fetching the source code because it's nice and quick

>I've been running CVS for more than two hours now, and it has terminated 
>with a broken connection 10 (make that 11) times so far.


The funny thing is that it works the opposite way for me. CVS checkout
works without problems and Mercurial checkouts almost always time out
or aren't succesful.

Should tell you that the software is only a small part of the problem.



Re: GCC 10 available for testing etc. in -current.

2021-04-18 Thread Lloyd Parkes



On 19/04/21 10:21 am, Lloyd Parkes wrote:


On 17/04/21 6:30 pm, Lloyd Parkes wrote:
I am using the Mercurial repository at https://anonhg.NetBSD.org/src 
for fetching the source code because it's nice and quick


So I'm now downloading the source code through CVS instead of 
Mercurial because nobody else seems to be having the same problems 
that I'm having building with GCC 10.


I found the answer.

Someone moved the bookmark called "@" in a way that Mercurial wasn't 
willing to blindly propagate into my local, central copy of the 
Mercurial src repository. This could easily have been done by part of 
the CVS to Mercurial tracking that is done rather than by a real person.


Mercurial then left the original "@" bookmark in place in my central 
copy of the src repository, created a bookmark called "@default" to 
track the upstream "@", and finally issued me a warning about a 
"divergent bookmark". I didn't know what that meant or that I was using 
the "@" bookmark. It turns out that "@" is the default thing to checkout 
if such a bookmark exists.


Of course, when cloning to a build box Mercurial just cloned my central 
repository without needing to warn me about divergent bookmarks (there 
was no divergence at this step) and I was unknowingly using an old 
version of the source tree with no possibility of it ever getting updated.


The fix is for me to explicitly checkout the branch "trunk" when I don't 
want a specific branch. And also to keep an eye on messages when I 
update my local, central copy of the Mercurial src repository.


Now I can get back to building things with GCC 10 and then wondering how 
to get all the hardware booted.


Cheers,
Lloyd



daily CVS update output

2021-04-18 Thread NetBSD source update


Updating src tree:
P src/common/lib/libc/string/memset2.c
P src/distrib/sets/lists/tests/mi
P src/external/bsd/tmux/dist/cmd-display-menu.c
P src/external/bsd/tmux/dist/window-customize.c
P src/external/bsd/tmux/dist/window-tree.c
P src/sbin/cgdconfig/cgdconfig.8
P src/sbin/cgdconfig/cgdconfig.c
P src/share/mk/bsd.own.mk
P src/sys/arch/evbmips/conf/OCTEON
P src/sys/arch/mips/conf/std.octeon
P src/sys/arch/mips/mips/locore.S
P src/tests/usr.bin/xlint/lint1/Makefile
U src/tests/usr.bin/xlint/lint1/emit.c
U src/tests/usr.bin/xlint/lint1/emit.exp
U src/tests/usr.bin/xlint/lint1/emit.ln
P src/tests/usr.bin/xlint/lint1/gcc_init_compound_literal.c
U src/tests/usr.bin/xlint/lint1/gcc_init_compound_literal.exp
P src/tests/usr.bin/xlint/lint1/msg_260.c
U src/tests/usr.bin/xlint/lint1/msg_260.exp
P src/tests/usr.bin/xlint/lint1/t_integration.sh
P src/usr.bin/xlint/Makefile.inc
P src/usr.bin/xlint/common/mem.c
P src/usr.bin/xlint/common/tyname.c
P src/usr.bin/xlint/lint1/Makefile
P src/usr.bin/xlint/lint1/cgram.y
P src/usr.bin/xlint/lint1/ckgetopt.c
P src/usr.bin/xlint/lint1/decl.c
P src/usr.bin/xlint/lint1/emit1.c
P src/usr.bin/xlint/lint1/err.c
P src/usr.bin/xlint/lint1/externs1.h
P src/usr.bin/xlint/lint1/func.c
P src/usr.bin/xlint/lint1/init.c
P src/usr.bin/xlint/lint1/lex.c
P src/usr.bin/xlint/lint1/lint1.h
P src/usr.bin/xlint/lint1/main1.c
P src/usr.bin/xlint/lint1/tree.c
P src/usr.bin/xlint/lint2/Makefile
P src/usr.bin/xlint/lint2/main2.c
P src/usr.bin/xlint/lint2/read.c
P src/usr.bin/xlint/xlint/xlint.c

Updating xsrc tree:


Killing core files:



Updating release-8 src tree (netbsd-8):

Updating release-8 xsrc tree (netbsd-8):



Updating release-9 src tree (netbsd-9):

Updating release-9 xsrc tree (netbsd-9):




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  38766788 Apr 19 03:11 ls-lRA.gz


Re: GCC 10 available for testing etc. in -current.

2021-04-18 Thread Thomas Mueller
> On 17/04/21 6:30 pm, Lloyd Parkes wrote:
> > I am using the Mercurial repository at https://anonhg.NetBSD.org/src for
> > fetching the source code because it's nice and quick

> So I'm now downloading the source code through CVS instead of Mercurial
> because nobody else seems to be having the same problems that I'm having
> building with GCC 10.
> 
> I've been running CVS for more than two hours now, and it has terminated with
> a broken connection 10 (make that 11) times so far. I'm rerunning with "cvs
> update", so I am making progress. Even so, CVS has only just got to paths
> starting with the letter "d".

> As someone who has used CVS for almost 30 years now, I'm happy to say that CVS
> just needs to be retired. Have a flag day, check that the content in the HEADs
> all match up and then make CVS read-only. I know many of us are old and
> grumpy, but that model T isn't our every day drive any more.
> 
> Cheers,
> Lloyd
 
> p.s. The code in Mercurial seems to match what I can browse on the FTP site,  
> so I really am at a loss as to why I can't build, so I am checking everything.

I too would like to see CVS retired.  

There is a long wait for cvs update to start, and longer wait to return to 
command prompt after the update download is finished.

Svn has lesser such delays; git is much faster.

FreeBSD switched doc and src trees from svn to git, and more recently switched 
the ports tree to git.

Tom



Automated report: NetBSD-current/i386 build success

2021-04-18 Thread 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:

2021.04.18.22.51.24 rillig src/usr.bin/xlint/Makefile.inc,v 1.14
2021.04.18.22.51.24 rillig src/usr.bin/xlint/common/mem.c,v 1.12
2021.04.18.22.51.24 rillig src/usr.bin/xlint/lint1/Makefile,v 1.70
2021.04.18.22.51.24 rillig src/usr.bin/xlint/lint1/main1.c,v 1.45
2021.04.18.22.51.24 rillig src/usr.bin/xlint/lint2/Makefile,v 1.20
2021.04.18.22.51.24 rillig src/usr.bin/xlint/lint2/main2.c,v 1.17
2021.04.18.22.51.24 rillig src/usr.bin/xlint/lint2/read.c,v 1.45
2021.04.18.22.51.25 rillig src/usr.bin/xlint/xlint/xlint.c,v 1.62
2021.04.18.23.02.16 rillig src/distrib/sets/lists/tests/mi,v 1.1044
2021.04.18.23.02.16 rillig src/tests/usr.bin/xlint/lint1/Makefile,v 1.45
2021.04.18.23.05.26 rillig src/tests/usr.bin/xlint/lint1/Makefile,v 1.46

Logs can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2021.04.html#2021.04.18.23.05.26


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Johnny Billquist

New one:

In the process of running build.sh for a full distribution:

#   compile  tmux/cmd-display-menu.o
/usr/src/obj/tooldir.NetBSD-8.0-amd64/bin/vax--netbsdelf-gcc -O2 
-std=gnu99-Wall -Wstrict-prototypes -Wmissing-prototypes 
-Wpointer-arith -Wno-sign-compare  -Wsystem-headers   -Wno-traditional 
 -Wa,--fatal-warnings  -Wreturn-type -Wswitch -Wshadow -Wcast-qual 
-Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare 
-Wsign-compare -Wformat=2  -Wno-format-zero-length  -Werror 
--sysroot=/usr/src/obj/destdir.vax -DSUPPORT_UTMP -DSUPPORT_UTMPX 
-I/usr/src/external/bsd/tmux/dist 
-I/usr/src/external/bsd/tmux/usr.bin/tmux -DHAVE_ASPRINTF=1 
-DHAVE_B64_NTOP=1  -DHAVE_BITSTRING_H=1  -DHAVE_BSD_GETOPT=1 
-DHAVE_CFMAKERAW=1  -DHAVE_CLOCK_GETTIME=1  -DHAVE_CLOSEFROM=1 
-DHAVE_CURSES_H=1  -DHAVE_DAEMON=1  -DHAVE_DIRENT_H=1 
-DHAVE_EVENT2_EVENT_H=1  -DHAVE_FCNTL_CLOSEM=1  -DHAVE_FCNTL_H=1 
-DHAVE_FGETLN=1  -DHAVE_FLOCK=1  -DHAVE_FORKPTY=1  -DHAVE_FPARSELN=1 
-DHAVE_GETDTABLESIZE=1  -DHAVE_GETLINE=1  -DHAVE_GETOPT=1 
-DHAVE_GETPROGNAME=1  -DHAVE_INTTYPES_H=1  -DHAVE_LIBM=1 
-DHAVE_LIBPROC_H=1  -DHAVE_MEMMEM=1  -DHAVE_MEMORY_H=1  -DHAVE_PATHS_H=1 
 -DHAVE_PROC_PID=1  -DHAVE_QUEUE_H=1  -DHAVE_REALLOCARRAY=1 
-DHAVE_SETENV=1  -DHAVE_SETPROCTITLE=1  -DHAVE_STDINT_H=1 
-DHAVE_STDLIB_H=1  -DHAVE_STRCASESTR=1  -DHAVE_STRINGS_H=1 
-DHAVE_STRING_H=1  -DHAVE_STRLCAT=1  -DHAVE_STRLCPY=1  -DHAVE_STRNDUP=1 
 -DHAVE_STRSEP=1  -DHAVE_STRTONUM=1  -DHAVE_SYSCONF=1 
-DHAVE_SYS_DIR_H=1  -DHAVE_SYS_SIGNAME=1  -DHAVE_SYS_STAT_H=1 
-DHAVE_SYS_TREE_H=1  -DHAVE_SYS_TYPES_H=1  -DHAVE_TREE_H=1 
-DHAVE_UNISTD_H=1  -DHAVE_UTEMPTER=1  -DHAVE_UTIL_H=1  -DHAVE_VIS=1 
-DHAVE___PROGNAME=1  -DPACKAGE=\"tmux\"  -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_NAME=\"tmux\"  -DPACKAGE_STRING=\"tmux\ 3.2\" 
-DPACKAGE_TARNAME=\"tmux\"  -DPACKAGE_URL=\"\" 
-DPACKAGE_VERSION=\"3.2\"  -DSTDC_HEADERS=1 
-DTMUX_CONF="\"/etc/tmux.conf:~/.tmux.conf:~/.config/tmux/tmux.conf\"" 
-DTMUX_VERSION='"3.2"'  -DVERSION=\"3.2\"  -D_ALL_SOURCE=1 
-D_GNU_SOURCE=1  -D_NETBSD_SOURCE  -D_OPENBSD_SOURCE 
-D_POSIX_PTHREAD_SEMANTICS=1  -D_TANDEM_SOURCE=1  -D_XOPEN_SOURCE=500 
-D__EXTENSIONS__=1  -c 
/usr/src/external/bsd/tmux/dist/cmd-display-menu.c -o cmd-display-menu.o
/usr/src/external/bsd/tmux/dist/cmd-display-menu.c: In function 
'cmd_display_menu_get_position':
/usr/src/external/bsd/tmux/dist/cmd-display-menu.c:158:8: error: 
comparison of integer expressions of different signedness: 'long int' 
and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]

  158 |  if (n >= tty->sy)
  |^~
/usr/src/external/bsd/tmux/dist/cmd-display-menu.c:191:8: error: 
comparison of integer expressions of different signedness: 'long int' 
and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]

  191 |  if (n >= tty->sy)
  |^~
/usr/src/external/bsd/tmux/dist/cmd-display-menu.c:239:8: error: 
comparison of integer expressions of different signedness: 'long int' 
and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]

  239 |  if (n < h)
  |^
cc1: all warnings being treated as errors

*** Failed target:  cmd-display-menu.o


Anyone have any idea about that one?

  Johnny

--
Johnny Billquist  || "I'm on a bus
  ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol


Re: GCC 10 available for testing etc. in -current.

2021-04-18 Thread Lloyd Parkes



On 17/04/21 6:30 pm, Lloyd Parkes wrote:
I am using the Mercurial repository at https://anonhg.NetBSD.org/src 
for fetching the source code because it's nice and quick


So I'm now downloading the source code through CVS instead of Mercurial 
because nobody else seems to be having the same problems that I'm having 
building with GCC 10.


I've been running CVS for more than two hours now, and it has terminated 
with a broken connection 10 (make that 11) times so far. I'm rerunning 
with "cvs update", so I am making progress. Even so, CVS has only just 
got to paths starting with the letter "d".


As someone who has used CVS for almost 30 years now, I'm happy to say 
that CVS just needs to be retired. Have a flag day, check that the 
content in the HEADs all match up and then make CVS read-only. I know 
many of us are old and grumpy, but that model T isn't our every day 
drive any more.


Cheers,
Lloyd

p.s. The code in Mercurial seems to match what I can browse on the FTP 
site, so I really am at a loss as to why I can't build, so I am checking 
everything.




Automated report: NetBSD-current/i386 build failure

2021-04-18 Thread 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 2021.04.18.20.15.17.

An extract from the build.sh output follows:

   ===
checkflist ===> distrib/sets
--- check_DESTDIR ---
--- checkflist ---
cd /tmp/build/2021.04.18.20.15.17-i386/src/distrib/sets &&  
DESTDIR=/tmp/build/2021.04.18.20.15.17-i386/destdir  MACHINE=i386  
MACHINE_ARCH=i386  AWK=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbawk  
CKSUM=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbcksum  
DB=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbdb  
EGREP=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbgrep\ -E  HOST_SH=/bin/sh 
 MAKE=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbmake  
MKTEMP=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbmktemp  
MTREE=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbmtree  
PAX=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbpax  COMPRESS_PROGRAM=gzip  
GZIP=-n  XZ_OPT=-9  TAR_SUFF=tgz  
PKG_CREATE=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbpkg_create  
SED=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbsed  
TSORT=/tmp/build/2021.04.18.20.15.17-i386/tools/bin/nbtsort\ -q  /bin/sh 
/tmp/build/2021.04.18.20.15.17-i386/src/distrib/sets/checkflist  -L base  -M 
/tmp/build/2021.04.
 18.20.15.17-i386/destdir/METALOG.sanitised
===  1 extra files in DESTDIR  =
Files in DESTDIR but missing from flist.
File is obsolete or flist is out of date ?
--
./usr/tests/usr.bin/xlint/lint1/emit.ln
=  end of 1 extra files  ===
*** [checkflist] Error code 1
nbmake[2]: stopped in /tmp/build/2021.04.18.20.15.17-i386/src/distrib/sets
1 error
nbmake[2]: stopped in /tmp/build/2021.04.18.20.15.17-i386/src/distrib/sets
nbmake[1]: stopped in /tmp/build/2021.04.18.20.15.17-i386/src
nbmake: stopped in /tmp/build/2021.04.18.20.15.17-i386/src
ERROR: Failed to make release

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

2021.04.18.19.56.09 maya src/sbin/cgdconfig/cgdconfig.8,v 1.49
2021.04.18.19.56.09 maya src/sbin/cgdconfig/cgdconfig.c,v 1.51
2021.04.18.20.02.56 rillig src/distrib/sets/lists/tests/mi,v 1.1043
2021.04.18.20.02.56 rillig src/tests/usr.bin/xlint/lint1/Makefile,v 1.44
2021.04.18.20.02.56 rillig src/tests/usr.bin/xlint/lint1/emit.c,v 1.1
2021.04.18.20.02.56 rillig src/tests/usr.bin/xlint/lint1/emit.exp,v 1.1
2021.04.18.20.02.56 rillig src/tests/usr.bin/xlint/lint1/emit.ln,v 1.1
2021.04.18.20.02.56 rillig src/tests/usr.bin/xlint/lint1/t_integration.sh,v 
1.43
2021.04.18.20.02.56 rillig src/usr.bin/xlint/lint1/emit1.c,v 1.44
2021.04.18.20.15.17 rillig src/usr.bin/xlint/lint1/main1.c,v 1.44
2021.04.18.20.15.17 rillig src/usr.bin/xlint/lint2/main2.c,v 1.16

Logs can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2021.04.html#2021.04.18.20.15.17


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Johnny Billquist

On 2021-04-18 17:55, Paul Goyette wrote:

Something in your environment? /etc/mk.conf ?


Dang. You're right. I wonder when any why I got that in there...?

Ok. Nothing to see here. Sorry for the noise.

  Johnny



On Sun, 18 Apr 2021, Johnny Billquist wrote:


On 2021-04-18 17:49, Martin Husemann wrote:

On Sun, Apr 18, 2021 at 05:46:39PM +0200, Johnny Billquist wrote:

I said in my original mail:

"Building from NetBSD-8 does not work. Unsure if this is a known
limitation."

So, not building from current, but am trying to build current.


Yes, but you are overriding HAVE_GCC somehow.


Not that I am aware of. But obviously it has been set by something 
already before it comes to those lines in bsd.own.mk


But I checked, and my whole source tree is pretty much unmodified, 
except for some vax specific files, where I have my own development 
stuff going on. Nothing that affects this.


 Johnny

--
Johnny Billquist  || "I'm on a bus
 ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol

!DSPAM:607c55fb81081654361426!




++--+---+
| Paul Goyette   | PGP Key fingerprint: | E-mail addresses: |
| (Retired)  | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org   |
++--+---+



--
Johnny Billquist  || "I'm on a bus
  ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Paul Goyette

Something in your environment? /etc/mk.conf ?

On Sun, 18 Apr 2021, Johnny Billquist wrote:


On 2021-04-18 17:49, Martin Husemann wrote:

On Sun, Apr 18, 2021 at 05:46:39PM +0200, Johnny Billquist wrote:

I said in my original mail:

"Building from NetBSD-8 does not work. Unsure if this is a known
limitation."

So, not building from current, but am trying to build current.


Yes, but you are overriding HAVE_GCC somehow.


Not that I am aware of. But obviously it has been set by something already 
before it comes to those lines in bsd.own.mk


But I checked, and my whole source tree is pretty much unmodified, except for 
some vax specific files, where I have my own development stuff going on. 
Nothing that affects this.


 Johnny

--
Johnny Billquist  || "I'm on a bus
 ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol

!DSPAM:607c55fb81081654361426!




++--+---+
| Paul Goyette   | PGP Key fingerprint: | E-mail addresses: |
| (Retired)  | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org   |
++--+---+


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Johnny Billquist

On 2021-04-18 17:49, Martin Husemann wrote:

On Sun, Apr 18, 2021 at 05:46:39PM +0200, Johnny Billquist wrote:

I said in my original mail:

"Building from NetBSD-8 does not work. Unsure if this is a known
limitation."

So, not building from current, but am trying to build current.


Yes, but you are overriding HAVE_GCC somehow.


Not that I am aware of. But obviously it has been set by something 
already before it comes to those lines in bsd.own.mk


But I checked, and my whole source tree is pretty much unmodified, 
except for some vax specific files, where I have my own development 
stuff going on. Nothing that affects this.


  Johnny

--
Johnny Billquist  || "I'm on a bus
  ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Johnny Billquist

On 2021-04-18 17:48, Martin Husemann wrote:

On Sun, Apr 18, 2021 at 05:44:36PM +0200, Johnny Billquist wrote:

On 2021-04-18 17:42, Martin Husemann wrote:

On Sun, Apr 18, 2021 at 03:09:17PM +0200, Johnny Billquist wrote:

Basically, the problem is that HAVE_GCC is there set to 8,


Where and why? This should not happen - HAVE_GCC for -current is either 9
or 10, no matter on what host / which tools you compile with.


GW:/usr/src# uname -a
NetBSD GW.SoftJAR.SE 8.0 NetBSD 8.0 (GENERIC) #0: Tue Jul 17 14:59:51 UTC
2018 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
amd64

Cross compiling for vax with a current checkout from a couple of hours ago.


No, I mean where the HAVE_GCC=8 comes from.

The only places where we set is is in bsd.own.mk, in this code:

#
# What GCC is used?
#
.if ${MACHINE} == "alpha" || \
 ${MACHINE_ARCH} == "x86_64" || \
 ${MACHINE} == "ia64" || \
 ${MACHINE} == "sparc" || \
 ${MACHINE} == "sparc64" || \
 ${MACHINE} == "vax" || \
 ${MACHINE_ARCH} == "riscv32" || \
 ${MACHINE_ARCH} == "riscv64"
HAVE_GCC?=  10
.else
HAVE_GCC?=  9
.endif


... so if you end up with "8" here, something is wrong in your setup.


bsd.own.mk only conditionally sets it if it is unset.
I have no idea where it comes from. I certainly have not touched it.
I only added a .info to print out what the actual value is, and it's 
already set to 8 by something previous, obviously, since it's not being 
set there.


  Johnny

--
Johnny Billquist  || "I'm on a bus
  ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Martin Husemann
On Sun, Apr 18, 2021 at 05:46:39PM +0200, Johnny Billquist wrote:
> I said in my original mail:
> 
> "Building from NetBSD-8 does not work. Unsure if this is a known
> limitation."
> 
> So, not building from current, but am trying to build current.

Yes, but you are overriding HAVE_GCC somehow.

Martin


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Martin Husemann
On Sun, Apr 18, 2021 at 05:44:36PM +0200, Johnny Billquist wrote:
> On 2021-04-18 17:42, Martin Husemann wrote:
> > On Sun, Apr 18, 2021 at 03:09:17PM +0200, Johnny Billquist wrote:
> > > Basically, the problem is that HAVE_GCC is there set to 8,
> > 
> > Where and why? This should not happen - HAVE_GCC for -current is either 9
> > or 10, no matter on what host / which tools you compile with.
> 
> GW:/usr/src# uname -a
> NetBSD GW.SoftJAR.SE 8.0 NetBSD 8.0 (GENERIC) #0: Tue Jul 17 14:59:51 UTC
> 2018 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> amd64
> 
> Cross compiling for vax with a current checkout from a couple of hours ago.

No, I mean where the HAVE_GCC=8 comes from.

The only places where we set is is in bsd.own.mk, in this code:

#
# What GCC is used?
#
.if ${MACHINE} == "alpha" || \
${MACHINE_ARCH} == "x86_64" || \
${MACHINE} == "ia64" || \
${MACHINE} == "sparc" || \
${MACHINE} == "sparc64" || \
${MACHINE} == "vax" || \
${MACHINE_ARCH} == "riscv32" || \
${MACHINE_ARCH} == "riscv64"
HAVE_GCC?=  10
.else
HAVE_GCC?=  9
.endif


... so if you end up with "8" here, something is wrong in your setup.

Martin


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Johnny Billquist

On 2021-04-18 17:44, Johnny Billquist wrote:

On 2021-04-18 17:42, Martin Husemann wrote:

On Sun, Apr 18, 2021 at 03:09:17PM +0200, Johnny Billquist wrote:

Basically, the problem is that HAVE_GCC is there set to 8,


Where and why? This should not happen - HAVE_GCC for -current is either 9
or 10, no matter on what host / which tools you compile with.


GW:/usr/src# uname -a
NetBSD GW.SoftJAR.SE 8.0 NetBSD 8.0 (GENERIC) #0: Tue Jul 17 14:59:51 
UTC 2018 
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64


Cross compiling for vax with a current checkout from a couple of hours ago.


I said in my original mail:

"Building from NetBSD-8 does not work. Unsure if this is a known 
limitation."


So, not building from current, but am trying to build current.

  Johnny

--
Johnny Billquist  || "I'm on a bus
  ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Johnny Billquist

On 2021-04-18 17:42, Martin Husemann wrote:

On Sun, Apr 18, 2021 at 03:09:17PM +0200, Johnny Billquist wrote:

Basically, the problem is that HAVE_GCC is there set to 8,


Where and why? This should not happen - HAVE_GCC for -current is either 9
or 10, no matter on what host / which tools you compile with.


GW:/usr/src# uname -a
NetBSD GW.SoftJAR.SE 8.0 NetBSD 8.0 (GENERIC) #0: Tue Jul 17 14:59:51 
UTC 2018 
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64


Cross compiling for vax with a current checkout from a couple of hours ago.

  Johnny

--
Johnny Billquist  || "I'm on a bus
  ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Martin Husemann
On Sun, Apr 18, 2021 at 03:09:17PM +0200, Johnny Billquist wrote:
> Basically, the problem is that HAVE_GCC is there set to 8,

Where and why? This should not happen - HAVE_GCC for -current is either 9
or 10, no matter on what host / which tools you compile with.

Martin


Automated report: NetBSD-current/i386 build success

2021-04-18 Thread 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:

2021.04.18.14.01.29 christos 
src/external/bsd/tmux/dist/cmd-display-menu.c,v 1.3
2021.04.18.14.01.29 christos 
src/external/bsd/tmux/dist/window-customize.c,v 1.3
2021.04.18.14.01.29 christos src/external/bsd/tmux/dist/window-tree.c,v 1.9

Logs can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2021.04.html#2021.04.18.14.01.29


Re: Automated report: NetBSD-current/i386 build failure

2021-04-18 Thread Christos Zoulas
Fixed...

christos

> On Apr 18, 2021, at 9:39 AM, Andreas Gustafsson  wrote:
> 
> The i386 build is still failing, with errors like these:
> 
>  --- dependall-tmux ---
>  
> /tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:
>  In function 'cmd_display_menu_get_position':
>  
> /tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:158:8:
>  error: comparison of integer expressions of different signedness: 'long int' 
> and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]
>158 |  if (n >= tty->sy)
>|^~
>  
> /tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:191:8:
>  error: comparison of integer expressions of different signedness: 'long int' 
> and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]
>191 |  if (n >= tty->sy)
>|^~
>  
> /tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:239:8:
>  error: comparison of integer expressions of different signedness: 'long int' 
> and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]
>239 |  if (n < h)
>|^
> 
> --
> Andreas Gustafsson, g...@gson.org



signature.asc
Description: Message signed with OpenPGP


Re: Automated report: NetBSD-current/i386 build failure

2021-04-18 Thread Andreas Gustafsson
The i386 build is still failing, with errors like these:

  --- dependall-tmux ---
  
/tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:
 In function 'cmd_display_menu_get_position':
  
/tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:158:8:
 error: comparison of integer expressions of different signedness: 'long int' 
and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]
158 |  if (n >= tty->sy)
|^~
  
/tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:191:8:
 error: comparison of integer expressions of different signedness: 'long int' 
and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]
191 |  if (n >= tty->sy)
|^~
  
/tmp/build/2021.04.18.12.05.29-i386/src/external/bsd/tmux/dist/cmd-display-menu.c:239:8:
 error: comparison of integer expressions of different signedness: 'long int' 
and 'u_int' {aka 'unsigned int'} [-Werror=sign-compare]
239 |  if (n < h)
|^

-- 
Andreas Gustafsson, g...@gson.org


Re: HEADS UP: GCC 10 now default on several ports

2021-04-18 Thread Johnny Billquist

On 2021-04-17 10:01, John Paul Adrian Glaubitz wrote:

On 4/17/21 6:15 AM, matthew green wrote:

i've switched the alpha, amd64, sparc*, riscv*, ia64, and vax ports
have all been switched to GCC 10.

please send-pr or send email here about problems you encounter.


And please report compiler-specific issues such as miscompiliations to the
GCC bug tracker such that a broader audience becomes aware of these problems.


Building from NetBSD-8 does not work. Unsure if this is a known limitation.

Basically, the problem is that HAVE_GCC is there set to 8, and in 
bsd.own.mk there is this piece:


.if ${HAVE_GCC} == 9
EXTERNAL_GCC_SUBDIR?=   gcc.old
.elif ${HAVE_GCC} == 10
EXTERNAL_GCC_SUBDIR?=   gcc
.else
EXTERNAL_GCC_SUBDIR?=   /does/not/exist
.endif

Which means EXTERNAL_GCC_SUBDIR gets set to /does/not/exist
and then build.sh borks out with non-existing directory pretty quickly 
when building the tools.


  Johnny

--
Johnny Billquist  || "I'm on a bus
  ||  on a psychedelic trip
email: b...@softjar.se ||  Reading murder books
pdp is alive! ||  tryin' to stay hip" - B. Idol