From nobody Mon Feb 14 23:26:00 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4C5C919CD504 for ; Mon, 14 Feb 2022 23:27:17 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JyL3T1mh1z3M7X; Mon, 14 Feb 2022 23:27:17 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1644881237; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mJXyGVoOTgrLeEE8K+e1lv/cC6M3nLsAEgxXsdGKP+w=; b=obzvT3S0xL18iQvC8y/L3FXCMpZ8ES5TFRDL2CM6X6XZIAsIBILi7czw/0knKfyGR8wjzT bkYQRyrXtepROTvIXGD6jQeMfscV+aoUP1ooGrI0fNzYgJstHFjAt6FCrBaPHiV8hrUbEg 4p63MnKinEMzuG6xlY7qz5QvvueaeAjmMJwe6Cq57HrmRcv0uldmv2kKccah5H7ajARjS6 xOtrumB3DpqqhliPbZ6rZJz2V/sZTty4ub4CS32zF8CYv3gGpvw5ZYRHsTBWIAktf/5mkg XO4k0aIbPeENCWssG5DkaEbKVm0KGX5HdsV8Xtdux1vygdX8UwPkgggYu6WL2w== Received: from localhost (unknown [IPv6:240b:11:220:fe00:1d2a:3996:f353:7c5d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: yasu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 7F84524D7A; Mon, 14 Feb 2022 23:27:16 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Tue, 15 Feb 2022 08:26:00 +0900 (JST) Message-Id: <20220215.082600.277857195136294442.yasu@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Buildworld fails with external GCC toolchain From: Yasuhiro Kimura In-Reply-To: References: <116A6C73-6A06-4671-9C82-5D58A7F05018@FreeBSD.org> <20220213.043416.312036094791123131.yasu@FreeBSD.org> X-Mailer: Mew version 6.8 on Emacs 29.0.50 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1644881237; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mJXyGVoOTgrLeEE8K+e1lv/cC6M3nLsAEgxXsdGKP+w=; b=vJOL/QzUt1PkjppilroC9kFBif4QDsTFmm5YpUSgvX76f2WnhxTHBXQJK5Yo58efZ4Nj44 w3g9+CVDYihOd/FbCgdoPwWPZJH+bw+aXWSYi2jiij+IS0ecZ0B+x77IgzlfydCfDOxOyD sLy+fG4hKIOmUfBSBavWJXGyt/yPF7t0Kqj0c9ZHeU75r242wgPSYCrTReR9US93tF6hEE O5IS1S1B6A/bD3KGk/lFxuJ7PaZCGDGyFQLDZMc5Le3TamiZeS/8S9F7G0qz81cmmnJq8k 0yyO0MwDMjLQLE2QYZXfU6NWJbruovvY0fn4EqdgtgxE5ReYZW06AQ5FJLu/aQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1644881237; a=rsa-sha256; cv=none; b=C3EdWHMVEbRBCXuS8KoC3ekHHTf+tAFoEFlnmponbFnwiTGXbHa+HQEjgL5ICcRS6YwzeY BxwkEPeDyMcyQYZgH9v+702eMngNir17FLadNjFZT914chg4DFnWk9Y1luEnBq/faFDJFR snVG0/uxpT/iBA0eZOdZ9KenLRy5tcLo07V1yzGwxsjBt+KiBHMDafQAXEKDxItpbR54C8 qDZO5ktGoMcu2e3p/8blP/4/K1pX8AtZotzA3NVIWVSxmwO/AzNHyzMYAR4baGF/oZbLKH /ORdDnk5Oe+5U1a6tIOscDIJwAZEcxThbHtwnNsmfgTO9kgoUo8OPVtpv4d8AQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N From: John Baldwin Subject: Re: Buildworld fails with external GCC toolchain Date: Mon, 14 Feb 2022 10:46:29 -0800 >>> Not really, the gcc 9 build has been broken for months, as far as I >>> know. >>> >>> See also: https://ci.freebsd.org/job/FreeBSD-main-amd64-gcc9_build/ >>> >>> The last build(s) show a different error from yours, though: >>> >>> /workspace/src/tests/sys/netinet/libalias/util.c: In function >>> 'set_udp': >>> /workspace/src/tests/sys/netinet/libalias/util.c:112:2: error: >>> converting a packed 'struct ip' pointer (alignment 2) to a 'uint32_t' >>> {aka 'unsigned int'} pointer (alignment 4) may result in an unaligned >>> pointer value [-Werror=address-of-packed-member] >>> 112 | uint32_t *up = (void *)p; >>> | ^~~~~~~~ >>> In file included from >>> /workspace/src/tests/sys/netinet/libalias/util.h:37, >>> from /workspace/src/tests/sys/netinet/libalias/util.c:39: >>> /workspace/src/sys/netinet/ip.h:51:8: note: defined here >>> 51 | struct ip { >>> | ^~ >>> >>> -Dimitry >>> >> Thanks for information. I went back the commit history of main branch >> about every month and check if buildworld succeeds with GCC. But it >> didn't succeed even if I went back about a year. And devel/binutils >> port was update to 2.37 on last August. So I suspect external GCC >> toolchain doesn't work well after binutils is updated to current >> version. > > I have amd64 world + kernel building with GCC 9 and the only remaining > open review not merged yet is https://reviews.freebsd.org/D34147. > > It is work to keep it working though and I hadn't worked on it again > until recently. Thanks for letting me know. I tried patch of the review and confirmed both buildworld and buildkernel succeed with GCC 9 and binutils 2.37. So I reached start point now and can test binutils 2.38. --- Yasuhiro Kimura