From nobody Wed Dec 21 13:41:07 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 4NcZN61nl9z1GwjK for ; Wed, 21 Dec 2022 13:41:10 +0000 (UTC) (envelope-from zseri.devel+fbsd@ytrizja.de) Received: from ytrizja.de (ytrizja.de [138.201.154.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4NcZN54LKVz49w6 for ; Wed, 21 Dec 2022 13:41:09 +0000 (UTC) (envelope-from zseri.devel+fbsd@ytrizja.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ytrizja.de header.s=2020 header.b=ASL1RtQB; spf=pass (mx1.freebsd.org: domain of zseri.devel+fbsd@ytrizja.de designates 138.201.154.11 as permitted sender) smtp.mailfrom=zseri.devel+fbsd@ytrizja.de; dmarc=pass (policy=reject) header.from=ytrizja.de Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ytrizja.de; s=2020; t=1671630067; 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=6TseFy8N2Qms7AGuEwO0PbKRKUK0Nh00Pnp//n51IvE=; b=ASL1RtQBrvZOsr4yjKDkZbocSACH/Ji7HeF5NxX9yMvW7QalOiGnmB0fXgjvDCGZMsfR2l B18t0fIWVu0oEcPayMsAK/t5TnjDh5eFpqoQK0DN6J2IPrmNM+iIoRcBm5OlSTpSYjzmqZ qTojXZBrZiJNK9JazymveTaYFlaT+MnEsFEZ0e3wopMXvrOTwtFRTlstcS5chEL+yDIJtL wDAjpy1AjalICSzNvw4G9mBvZnr5KQzFTO+oK1W795SjQ1mQC3+t6z0zLG+DL0fqg4NS7A jPdUNb8u7/JkbDA9JTh8mCQ8Wes/z+X3HgOMK8vWw1P9iRs8bZrhJkGjnTE5pQ== Date: Wed, 21 Dec 2022 14:41:07 +0100 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 Subject: Re: all_subdir_lib/libclang_rt build failure (libc++ ld error) Content-Language: en-US To: freebsd-current@FreeBSD.org References: From: Alain Zscheile In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.97 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.969]; DMARC_POLICY_ALLOW(-0.50)[ytrizja.de,reject]; R_SPF_ALLOW(-0.20)[+mx:c]; R_DKIM_ALLOW(-0.20)[ytrizja.de:s=2020]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@FreeBSD.org]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ZERO(0.00)[0]; ASN(0.00)[asn:24940, ipnet:138.201.0.0/16, country:DE]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TAGGED_FROM(0.00)[fbsd]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[ytrizja.de:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4NcZN54LKVz49w6 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hello, On 21.12.22 01:24, Mark Millard wrote: > Alain Zscheile wrote on > Date: Tue, 20 Dec 2022 23:12:40 UTC : > >> I encountered a build failure while trying to build fbsd' >> src.git commit ae521fda895ff0b5076904f08ec92e3c60d53701 > > That commit is from main: > > • git: ae521fda895f - main - stress2: Added link to problem found Peter Holm > >> with `make -j4 buildworld` on an FreeBSD 13.1 system. > > So this was some 13.1 variant building at ae521fda895f of > main [so: 14]. That was not obvious on a first read of the > report. Sort of a self-hosted version upgrade cross-build. > > For reference (example local installs): > > # find /usr/obj/DESTDIRs/*/ -name libc++.so.1 -exec ls -C1 {} \; | grep -v lib32 > /usr/obj/DESTDIRs/13S-amd64-poud-bulk_a/usr/lib/libc++.so.1 > /usr/obj/DESTDIRs/13_1R-amd64-poud-bulk_a/usr/lib/libc++.so.1 > /usr/obj/DESTDIRs/main-amd64-poud-bulk_a/lib/libc++.so.1 > > Note that only main has main-amd64-poud-bulk_a/lib/libc++.so.1 > and it does not have a main-amd64-poud-bulk_a/usr/lib/libc++.so.1 . > > As for lib32: > > # find /usr/obj/DESTDIRs/*/ -name libc++.so.1 -exec ls -C1 {} \; | grep lib32 > /usr/obj/DESTDIRs/13S-amd64-poud-bulk_a/usr/lib32/libc++.so.1 > /usr/obj/DESTDIRs/13_1R-amd64-poud-bulk_a/usr/lib32/libc++.so.1 > /usr/obj/DESTDIRs/main-amd64-poud-bulk_a/usr/lib32/libc++.so.1 > > So all 3 have *-amd64-poud-bulk_a/usr/lib32/libc++.so.1 and none > have a *-amd64-poud-bulk_a/lib32/libc++.so.1 . > > tmp/lib/libc++.so.1 would be a main [so: 14] style path. > tmp/usr/lib/libc++.so.1 would be a 13.1 style path. > > The build appears to have which type of context applies > confused. > > It is not clang that is the issue, it is that FreeBSD changed > the path used for libc++.so.1 . (main avoids needing more > mounts already being actie place when libc++.so.1 is used in > some common configurations, usr/lib/ not being available yet. thanks for the explanation. > Looks to me like whatever vintage/variant of 13.1 it was did "vintage" I upgraded to the latest stable/13 commit before attempting the jump to main. > not yet(?) have logic for making sure that it provides for > builds of main [so: 14] that have the new libc++.so.1 style > path. Nor did the main materials have logic to make it work > when built from an older context, such as a 13.1 context. > At least one of the two must happen to allow 13.1 to build > a 14. Having main [so: 14] deal with it, if possible, could > possibly also deal with 13.0 vintages/variants without > adjusting 13.0 materials. To somewhat fix it I ran: `make cleanworld`, then reran `make -j4 buildworld`, while that was in progress I created a symlink from .../tmp/usr/lib/libc++.so.1 to `../../lib/libc++.so.` which resulted in a successfully finishing build. Regards, Alain Zscheile