From nobody Sat Feb 12 19:34:16 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 16E3219BA16B for ; Sat, 12 Feb 2022 19:35:43 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4Jx11C08qWz3NDs; Sat, 12 Feb 2022 19:35:43 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1644694543; 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=gZhBMygzenNUx1M3Ye7PZmLEbhUmY6XnylFwGu5ZnVA=; b=u9z2y90kPhXeCRLIDfpAYLVtqqDT4BTET5DuF+ZcrokPZZsOcQcMKWtIfB6Whmt6whVZ5k fEIznaHquG27/6Anyc4fm5PkS4kipe68sQQI63JHhoIDFGKp18dAUGnCBnifyJ0bnn5Fh8 psQApsmeZTlMFGxrDJIE6sl3cupSbI3lFJztmd4nE4GfATChP+RMbAiRNdYpNKDCe9P5PJ tQlxuU+TbdG1UiNWuCYqiGxaK6Xqi4rnfgtjsPdsof5bQ73G/KuDJCbnXMHJ4Jk7pIpIzG Dl3BU88cmb1qDCoPffGMDjSpY2snwjntKbmjrt1/pS21Prukovt4eTXFXqsAbQ== Received: from localhost (unknown [IPv6:240b:11:220:fe00:a92b:e366:2068:45ac]) (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 4E0A92AD72; Sat, 12 Feb 2022 19:35:42 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Sun, 13 Feb 2022 04:34:16 +0900 (JST) Message-Id: <20220213.043416.312036094791123131.yasu@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Buildworld fails with external GCC toolchain From: Yasuhiro Kimura In-Reply-To: <116A6C73-6A06-4671-9C82-5D58A7F05018@FreeBSD.org> References: <20220212.050756.569441849093045289.yasu@FreeBSD.org> <116A6C73-6A06-4671-9C82-5D58A7F05018@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=1644694543; 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=gZhBMygzenNUx1M3Ye7PZmLEbhUmY6XnylFwGu5ZnVA=; b=UQnnqd1ES259obZSPHhrh0t6L32OtMeGI71Cv0q/2A6+Zv5OJkQxt2VPahz4KKo4a5xosR yqtFFhsrPPZeyVOgGsVe3wJkm48615pJmHiGGBtRgeqDUpkw9Y/Um/pb16nTEOqp1d+rTf hJp1Cu+t3kyefDoLVtwxN/WHTW7jJUKUn3Tgl5UlEl4EIoMbSp75YGApthktXH8jvZQ5A6 iZuX7frbqBg0DHhW7XmbAdLuJBVET0f0E6gWDHmZSVv0JxgyBMFUqyRDyzb69OL6PZS8EB 80WWwvYPN4/L8jhU1hzqRg555ms0nkL1MktXgRlETFpodL2/7SyrvU7fP9qfmg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1644694543; a=rsa-sha256; cv=none; b=qxM/kLC6o7ibKSU/lBONyoqu/r39t5q+Cf/Iaa5K248uOiQpYW5c6fSsvXGtrrONZist33 bylpPMR36X+uv/itDyPafpC0Zw50rH/y70Hc0gW4QC62HY2PxyZR4C0zCEv262ArkM4QQ4 QoFWcksw+8wRu7OHZIMcfpoo5M6r2GvgAXMduFrJdTAiKtgJ+3SSGggwrQCQneKOm5khRO /v4G7JUCBdPStvI9gcmWaztZkHYb3IMeku6tfS1aVOs9OMLHqLwXMeqMr+IhhNMaR2bASh bJpl0LHXOQrnmJdiIIbvlRlbAKTyIaTnvX/PfWI3AbCYtiYeoVl3jlIQn2CEmA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N From: Dimitry Andric Subject: Re: Buildworld fails with external GCC toolchain Date: Fri, 11 Feb 2022 22:53:44 +0100 > 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. --- Yasuhiro Kimura