[Bug 267842] sysutils/u-boot-tools: error: typedef redefinition with different types ('uint64_t' (aka 'unsigned long') vs 'unsigned long long')
Date: Fri, 18 Nov 2022 07:18:40 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267842 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #1 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Martin Filla from comment #0) http://beefy14.nyi.freebsd.org/data/131amd64-quarterly/2b36c5c0b1b5/logs/u-boot-tools-2020.07.log shows the new build (started Fri Nov 18 05:16:51 UTC 2022) for quarterly was successful. It lists: cc -Wp,-MD,tools/.kwbimage.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCONFIG_FIT_SIGNATURE -DCONFIG_FIT_SIGNATURE_MAX_SIZE=0x10000000 -include ./include/compiler.h -idirafterinclude -idirafter./arch/sandbox/include -I./scripts/dtc/libfdt -I./tools -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -std=gnu99 -c -o tools/kwbimage.o tools/kwbimage.c echo "#include <../lib/md5.c>" >tools/lib/md5.c (No warnings or errors.) http://beefy16.nyi.freebsd.org/build.html?mastername=131amd64-default&build=0f24e88b3aa7 shows the Nov. 4 build for main (most recent) was successful. It lists: cc -Wp,-MD,tools/.kwbimage.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCONFIG_FIT_SIGNATURE -DCONFIG_FIT_SIGNATURE_MAX_SIZE=0x10000000 -include ./include/compiler.h -idirafterinclude -idirafter./arch/sandbox/include -I./scripts/dtc/libfdt -I./tools -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -std=gnu99 -c -o tools/kwbimage.o tools/kwbimage.c echo "#include <../lib/md5.c>" >tools/lib/md5.c (No warnings or errors.) These were poudriere bulk styles of builds. This suggests that your build environment has been polluted with something that interferes with the build. (Poudriere bulk builds avoid such pollution being involved.) You may need to list/investigate whatever else is installed on the system. -- You are receiving this mail because: You are the assignee for the bug.