git: 6733401935f8 - main - nvmecontrol: add device self-test op and log page

[Mark Millard]

Jessica Clarke jrtc27 at freebsd.org wrote on
Fri Jan 8 19:13:36 UTC 2021 :

. . .
> This broke powerpc and powerpc64:
> 
> In file included from ioctl.c:33:
> In file included from /home/jrtc27/src/sys/./cam/scsi/scsi_pass.h:35:
> In file included from /home/jrtc27/src/sys/cam/cam_ccb.h:46:
> In file included from /home/jrtc27/src/sys/cam/nvme/nvme_all.h:33:
> /home/jrtc27/src/sys/dev/nvme/nvme.h:2052:3: error: implicitly declaring library function 'memcpy' with type 'void *(void *, const void *, unsigned long)' [-Werror,-Wimplicit-function-declaration]
>                 memcpy(&failing_lba, s->result[r].failing_lba, sizeof(failing_lba));
>                 ^
> /home/jrtc27/src/sys/dev/nvme/nvme.h:2052:3: note: include the header <string.h> or explicitly provide a declaration for 'memcpy'
> 1 error generated.
> --- ioctl.o ---
> *** [ioctl.o] Error code 1
> 
> make[7]: stopped in /home/jrtc27/src/lib/libsysdecode
> 1 error
. . .

It is too bad that main (no svn involved) has not been getting
ci.freebsd.org builds/build-reports to catch problems with
spanning plaforms. It would be nice to be able to point to
build failures on ci.freebsd.org . This is not the first such
problem without ci.freebsd.org build-reports being available.

Historically I've also used such to have a better clue at what
to avoid in order to sidestep build problems. This will probably
be messier with the hash-id's not being able to compared for
main-commit-time order. I used to sort the list by Build
description. I've not figured out what I'll do once it starts
up again.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)