From nobody Thu Nov 24 11:03:16 2022 X-Original-To: freebsd-ports@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 4NHw8d2Pwvz4hvDt for ; Thu, 24 Nov 2022 11:03:29 +0000 (UTC) (envelope-from eduardo@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 4NHw8d2DXBz3y1v for ; Thu, 24 Nov 2022 11:03:29 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1669287809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/oa2D9v1TaOKaH16bh/n1g8BZFO9+yb0uEvKCS2b7ns=; b=QwwEOAjDDmilVTKnCdc1mTY0sMjoRRCiLiWM+O8lrooEm5/vs/E6kk6lY4BxPytfgfLqU8 t01OYdFbH+NegCkyevQp4I5wkOnntcVvVh0avjRjrmKqMMOfYOqf/pvpGhC0NOoJmcEjZs a6xyC8GuwqVacoygXAI/KfFfXTlCOPohzhumRuCLVIgfjzRhQVogagABsM9I50TH4oQwOC 4WXDCxiTLtEYOOL7Qr6cTyYPD5xAE2c6Rc4XfAkM5uMOvX4AKPMceSnT1JxVuGny5i+BKW 4GZ7uENhAsf25cKPkNUqfxPHp25uw1n/4YyVOXpsSzRBj6aQ5/kcBDPm4c4mvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1669287809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/oa2D9v1TaOKaH16bh/n1g8BZFO9+yb0uEvKCS2b7ns=; b=ebvMHkIoRobtuYODmC37UhsaiWmlNNzl4ZZMXuEZcmBNvTmBsnKILzZUrJ7VwHf+vhuEqD 3HOBxVPBE4RQOx4JX2UW07nJtJsG598k7QOcs58pDKDWXNvsaCkgizqaCkqA82QDJRAX2L xmw5C6k794De5MxYoC2O2+UEIysEXfaFtlJT+vZl0pHwpaaAkqrGfimNHRQjPUdqbC6iRW MVTLhthE8RLZBtBbt5Ts8yEVMQt68OL6wKqVawyZ9NyN7+5R6qxTRmBvDGTieGqMgmmO+Y y4PfA4wtA61iZCmU8ziTYQPGXAyjmbGWKt+KiPnXyySopvvBIxR7h2MJYbRWrA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1669287809; a=rsa-sha256; cv=none; b=tTNEFCGT5SHH7/h0LF7uHeJbxsE8YQLipXCda28r/80gJW5ggEciJj7yHHTVIrhz/dNfig SeXO/8zURJAFXsfc+SW8pM4dO60Z0968gfIpkzf4mRfh0HOPHI+BfCnmD60IClSXu0OOaS fuenWTPRgpIurhZLAVRh016gKdkQky0V1YoiYDVMXW+fQRPGhpoE5snKy9TCvhVdafSsIu x/nrpHQVm1drYtGyjkTx3KmQydDqUYKaU/d4GtVqcm30UXuqcG2xmRp/cZ7bRAjGG62HJ5 j5AmlSGlmpoq++pJFE+KZQf8eyoc527/pLfOg+X2mPTCKhXNbeuuP6JY2+yUgA== Received: from mail-ua1-f45.google.com (mail-ua1-f45.google.com [209.85.222.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4NHw8d11qPzJDQ for ; Thu, 24 Nov 2022 11:03:29 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-ua1-f45.google.com with SMTP id x24so484365uaf.4 for ; Thu, 24 Nov 2022 03:03:29 -0800 (PST) X-Gm-Message-State: ANoB5pljPVUy2BraywXBoqmS0VFI8JhI98vjfdfy3fCX5cezJSU/G3VS upp0+N3evODbpM3oYxjP5KayPPNEr+ATRnv8u/w= X-Google-Smtp-Source: AA0mqf6kXO9Rxaxj2dbpASuXd0z2vAp2H33w8/2fOi4RabcGJp0LAhfzMPZHsieikg5Hv804IVlUa13bujekGaTEDyM= X-Received: by 2002:a9f:2105:0:b0:3d2:a014:b043 with SMTP id 5-20020a9f2105000000b003d2a014b043mr8398753uab.13.1669287808256; Thu, 24 Nov 2022 03:03:28 -0800 (PST) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <96078C14-CBEB-4450-ACE1-EB0488DD1814.ref@yahoo.com> <96078C14-CBEB-4450-ACE1-EB0488DD1814@yahoo.com> In-Reply-To: <96078C14-CBEB-4450-ACE1-EB0488DD1814@yahoo.com> From: Nuno Teixeira Date: Thu, 24 Nov 2022 11:03:16 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [zstd-sys 2.0.1+zstd.1.5.2] crate failing on arm64 To: Mark Millard Cc: FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000d6d09d05ee355a5d" X-ThisMailContainsUnwantedMimeParts: N --000000000000d6d09d05ee355a5d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Mark, I have compared some of errors/warnings with amd64 build logs and they are present in there too. I think I found a glitch at the end of arm64 log: --- [zstd-sys 2.0.1+zstd.1.5.2] running: "ar" "cq" "/wrkdirs/usr/ports... (...) "/wrkdirs/usr/ports/editors/lapce/ work/target/aarch64-unknown-freebsd/release/build/zstd-sys-97d70ebd740964f8= /out/zstd/lib/decompress/huf_decompress_ *amd64*.o" ^^^^^ --- and zstd-sys-2.0.1+zstd.1.5.2/zstd/lib/common/xxhash.h: # if (defined(__aarch64__) || defined(__arm64__) || defined(_M_ARM64) || defined(_M_ARM64EC)) \ So I presume that this crate should be build on arm64/aarch64 but don't understant why it calls: "huf_decompress_*amd64*.o" Any clues? Mark Millard escreveu no dia quinta, 24/11/2022 =C3=A0(= s) 04:46: > Nuno Teixeira wrote on > Date: Thu, 24 Nov 2022 00:33:24 UTC : > > > For some time I'm receiving errors from build servers about editors/lap= ce > > not building on arm64. > > > > From the log it seems [zstd-sys 2.0.1+zstd.1.5.2] crate failing. > > > > Is anybody with same problem? > > I need to be sure before open an issue at upstream. > > > > What I don't understad is that upstream provides aarch64 pre-compiled > > binaries... > > https://github.com/lapce/lapce/releases/tag/v0.2.4 > > > > > https://pkg-status.freebsd.org/ampere2/data/main-arm64-default/pf323e9d40= f68_s41be508d31/logs/lapce-0.2.4.log > > > My ports tree is somewhat older but also produces the > unexplained "*** Error code 101" (as did the FreeBSD > build servers for the same version I'm testing here): > > # tail -20 > /usr/local/poudriere/data/logs/bulk/main-CA72-default/2022-11-23_18h50m22= s/logs/errors/lapce-0.2.1.log > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_string_utils.c > [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/ucp= .h > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_ord2utf8.c > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_byte_order.c > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_fullinfo.c > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_compile.c > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_get.c > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_dfa_exec.c > [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/ > config.h.in > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_xclass.c > [libgit2-sys 0.13.4+1.4.2] > cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_globals.c > *** Error code 101 > > Stop. > make: stopped in /usr/ports/editors/lapce > =3D>> Cleaning up wrkdir > =3D=3D=3D> Cleaning for lapce-0.2.1 > build of editors/lapce | lapce-0.2.1 ended at Wed Nov 23 19:20:37 PST 202= 2 > build time: 00:22:50 > !!! build failure encountered !!! > > So may be the below will be suggestive/useful. > > > I'll note that the "*** Error code 101" ended up not being > anyhwere near were the problems(!) actually were. So likely > for you the "zstd-sys 2.0.1+zstd.1.5.2" need not be one of > the actual failure places. > > > How I found the problems and what they look like . . . > > I did the bulk build with -w and expanded the tar: > > # mkdir -p /wrkdirs/usr/ports/editors/lapce > # tar -xpf > /usr/local/poudriere/data/wrkdirs/main-CA72-default/default/lapce-0.2.1.t= bz > -C /wrkdirs/usr/ports/editors/lapce > > I then went exploring. What I eventually found is quickly shown > via: > > # find -s /wrkdirs/usr/ports/editors/lapce/ -name stderr -exec grep -l > "aborting due to previous error" {} \; | less > > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/cap-primitives-ed08064314a4640b/stderr > > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/cap-std-5acaec63374cb836/stderr > > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/io-extras-e83e1591d250cc25/stderr > > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/io-lifetimes-62b7366622512d7e/stderr > > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/system-interface-56dbb6efd7f0321e/stderr > > There could be non-empty stderr files with other text that are > also indications of failure. There are more stderr files. But > the other few that I looked at did not seem to be indicating > failures, more like informational/warning information. > > Text from some of the above stderr files: > > # less > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/cap-primitives-ed08064314a4640b/stderr > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(windows_by_handle)] > | ^^^^^^^^^^^^^^^^^ > > error[E0635]: unknown feature `windows_by_handle` > --> :1:12 > | > 1 | #![feature(windows_by_handle)] > | ^^^^^^^^^^^^^^^^^ > > error: aborting due to 2 previous errors > > Some errors have detailed explanations: E0554, E0635. > For more information about an error, try `rustc --explain E0554`. > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(windows_file_type_ext)] > | ^^^^^^^^^^^^^^^^^^^^^ > > error[E0635]: unknown feature `windows_file_type_ext` > --> :1:12 > | > 1 | #![feature(windows_file_type_ext)] > | ^^^^^^^^^^^^^^^^^^^^^ > > error: aborting due to 2 previous errors > > Some errors have detailed explanations: E0554, E0635. > For more information about an error, try `rustc --explain E0554`. > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(io_error_more)] > | ^^^^^^^^^^^^^ > > error: aborting due to previous error > > For more information about this error, try `rustc --explain E0554`. > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(io_error_uncategorized)] > | ^^^^^^^^^^^^^^^^^^^^^^ > > error: aborting due to previous error > > For more information about this error, try `rustc --explain E0554`. > > # less > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/cap-std-5acaec63374cb836/stderr > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(can_vector)] > | ^^^^^^^^^^ > > error: aborting due to previous error > > For more information about this error, try `rustc --explain E0554`. > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(seek_convenience)] > | ^^^^^^^^^^^^^^^^ > > warning: the feature `seek_convenience` has been stable since 1.51.0 and > no longer requires an attribute to enable > --> :1:12 > | > 1 | #![feature(seek_convenience)] > | ^^^^^^^^^^^^^^^^ > | > =3D note: `#[warn(stable_features)]` on by default > > error: aborting due to previous error; 1 warning emitted > > For more information about this error, try `rustc --explain E0554`. > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(with_options)] > | ^^^^^^^^^^^^ > > warning: the feature `with_options` has been stable since 1.58.0 and no > longer requires an attribute to enable > --> :1:12 > | > 1 | #![feature(with_options)] > | ^^^^^^^^^^^^ > | > =3D note: `#[warn(stable_features)]` on by default > > error: aborting due to previous error; 1 warning emitted > > For more information about this error, try `rustc --explain E0554`. > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:12 > | > 1 | #![feature(write_all_vectored)] > | ^^^^^^^^^^^^^^^^^^ > > error: aborting due to previous error > > For more information about this error, try `rustc --explain E0554`. > > # less > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/io-lifetimes-62b7366622512d7e/stderr > error[E0554]: `#![feature]` may not be used on the stable release channel > --> :1:1 > | > 1 | #![feature(rustc_attrs)] > | ^^^^^^^^^^^^^^^^^^^^^^^^ > > error: aborting due to previous error > > For more information about this error, try `rustc --explain E0554`. > warning: function `foo` is never used > --> :1:10 > | > 1 | const fn foo() { panic!() } > | ^^^ > | > =3D note: `#[warn(dead_code)]` on by default > > warning: 1 warning emitted > > > > It looks like, for rust based builds, such a "search through > the stderr files" from a bulk -w like tar of the failure is > the basic technique needed to identify the actual problems > and where they were. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --=20 Nuno Teixeira FreeBSD Committer (ports) --000000000000d6d09d05ee355a5d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Mark,

I have compared = some of errors/warnings with amd64 build logs and they are present in there= too.

I think I found a glitch at the end of arm64= log:
---
[zstd-sys 2.0.1+zstd.1.5.2] running: "ar= " "cq" "/wrkdirs/usr/ports...
(...)
=
=C2=A0"/wrkdirs/usr/ports/editors/lapce/
work/target/aarch64-u= nknown-freebsd/release/build/zstd-sys-97d70ebd740964f8/out/zstd/lib/decompr= ess/huf_decompress_amd64.o"
=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 ^^^^^
---
and zstd-sys-2.0.1+zs= td.1.5.2/zstd/lib/common/xxhash.h:
# =C2=A0if (defined(__aarch64_= _) || defined(__arm64__) || defined(_M_ARM64) || defined(_M_ARM64EC)) \

So I presume that this crate should be build on arm64= /aarch64 but don't understant why it calls:
"huf_decompr= ess_amd64.o"

Any clues?
=

Mark Millard <marklmi@yah= oo.com> escreveu no dia quinta, 24/11/2022 =C3=A0(s) 04:46:
Nuno Teixeira <ed= uardo_at_freebsd.org> wrote on
Date: Thu, 24 Nov 2022 00:33:24 UTC :

> For some time I'm receiving errors from build servers about editor= s/lapce
> not building on arm64.
>
> From the log it seems [zstd-sys 2.0.1+zstd.1.5.2] crate failing.
>
> Is anybody with same problem?
> I need to be sure before open an issue at upstream.
>
> What I don't understad is that upstream provides aarch64 pre-compi= led
> binaries...
> https://github.com/lapce/lapce/releases/tag/v= 0.2.4
>
> https://pkg-status.freebsd.org/ampere2/data/main-arm64-defaul= t/pf323e9d40f68_s41be508d31/logs/lapce-0.2.4.log


My ports tree is somewhat older but also produces the
unexplained "*** Error code 101" (as did the FreeBSD
build servers for the same version I'm testing here):

# tail -20 /usr/local/poudriere/data/logs/bulk/main-CA72-default/2022-11-23= _18h50m22s/logs/errors/lapce-0.2.1.log
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= string_utils.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/ucp.h=
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= ord2utf8.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= byte_order.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= fullinfo.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= compile.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= get.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= dfa_exec.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/config.h.in<= /a>
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= xclass.c
[libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= globals.c
*** Error code 101

Stop.
make: stopped in /usr/ports/editors/lapce
=3D>> Cleaning up wrkdir
=3D=3D=3D>=C2=A0 Cleaning for lapce-0.2.1
build of editors/lapce | lapce-0.2.1 ended at Wed Nov 23 19:20:37 PST 2022<= br> build time: 00:22:50
!!! build failure encountered !!!

So may be the below will be suggestive/useful.


I'll note that the "*** Error code 101" ended up not being anyhwere near were the problems(!) actually were. So likely
for you the "zstd-sys 2.0.1+zstd.1.5.2" need not be one of
the actual failure places.


How I found the problems and what they look like . . .

I did the bulk build with -w and expanded the tar:

# mkdir -p /wrkdirs/usr/ports/editors/lapce
# tar -xpf /usr/local/poudriere/data/wrkdirs/main-CA72-default/default/lapc= e-0.2.1.tbz -C /wrkdirs/usr/ports/editors/lapce

I then went exploring. What I eventually found is quickly shown
via:

# find -s /wrkdirs/usr/ports/editors/lapce/ -name stderr -exec grep -l &quo= t;aborting due to previous error" {} \; | less
/wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/cap-primitives-ed08064314a4640b/stderr
/wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/cap-std-5acaec63374cb836/stderr
/wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/io-extras-e83e1591d250cc25/stderr
/wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/io-lifetimes-62b7366622512d7e/stderr
/wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/system-interface-56dbb6efd7f0321e/stderr

There could be non-empty stderr files with other text that are
also indications of failure. There are more stderr files. But
the other few that I looked at did not seem to be indicating
failures, more like informational/warning information.

Text from some of the above stderr files:

# less /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd= /debug/build/cap-primitives-ed08064314a4640b/stderr
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(windows_by_handle)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^

error[E0635]: unknown feature `windows_by_handle`
=C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(windows_by_handle)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0554, E0635.
For more information about an error, try `rustc --explain E0554`.
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(windows_file_type_ext)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^

error[E0635]: unknown feature `windows_file_type_ext`
=C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(windows_file_type_ext)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0554, E0635.
For more information about an error, try `rustc --explain E0554`.
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(io_error_more)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(io_error_uncategorized)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^^
error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.

# less /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd= /debug/build/cap-std-5acaec63374cb836/stderr
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(can_vector)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(seek_convenience)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^

warning: the feature `seek_convenience` has been stable since 1.51.0 and no= longer requires an attribute to enable
=C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(seek_convenience)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^
=C2=A0 |
=C2=A0 =3D note: `#[warn(stable_features)]` on by default

error: aborting due to previous error; 1 warning emitted

For more information about this error, try `rustc --explain E0554`.
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(with_options)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^

warning: the feature `with_options` has been stable since 1.58.0 and no lon= ger requires an attribute to enable
=C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(with_options)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^
=C2=A0 |
=C2=A0 =3D note: `#[warn(stable_features)]` on by default

error: aborting due to previous error; 1 warning emitted

For more information about this error, try `rustc --explain E0554`.
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:12
=C2=A0 |
1 | #![feature(write_all_vectored)]
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.

# less /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd= /debug/build/io-lifetimes-62b7366622512d7e/stderr
error[E0554]: `#![feature]` may not be used on the stable release channel =C2=A0--> <anon>:1:1
=C2=A0 |
1 | #![feature(rustc_attrs)]
=C2=A0 | ^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.
warning: function `foo` is never used
=C2=A0--> <anon>:1:10
=C2=A0 |
1 | const fn foo() { panic!() }
=C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^
=C2=A0 |
=C2=A0 =3D note: `#[warn(dead_code)]` on by default

warning: 1 warning emitted



It looks like, for rust based builds, such a "search through
the stderr files" from a bulk -w like tar of the failure is
the basic technique needed to identify the actual problems
and where they were.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com



--
Nun= o Teixeira
FreeBSD Committer (ports)
--000000000000d6d09d05ee355a5d--