Date: Thu, 24 Nov 2022 11:03:16 +0000 From: Nuno Teixeira <eduardo@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: [zstd-sys 2.0.1+zstd.1.5.2] crate failing on arm64 Message-ID: <CAFDf7ULKuSUETZS4WLs3%2Bcepn94%2BnagY2OitNWoLP-JNjZUOGA@mail.gmail.com> In-Reply-To: <96078C14-CBEB-4450-ACE1-EB0488DD1814@yahoo.com> References: <96078C14-CBEB-4450-ACE1-EB0488DD1814.ref@yahoo.com> <96078C14-CBEB-4450-ACE1-EB0488DD1814@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <marklmi@yahoo.com> escreveu no dia quinta, 24/11/2022 =C3=A0(= s) 04:46: > Nuno Teixeira <eduardo_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 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 > --> <anon>:1:12 > | > 1 | #![feature(windows_by_handle)] > | ^^^^^^^^^^^^^^^^^ > > error[E0635]: unknown feature `windows_by_handle` > --> <anon>: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 > --> <anon>:1:12 > | > 1 | #![feature(windows_file_type_ext)] > | ^^^^^^^^^^^^^^^^^^^^^ > > error[E0635]: unknown feature `windows_file_type_ext` > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 > --> <anon>: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 <div dir=3D"ltr"><div>Hello Mark,</div><div><br></div><div>I have compared = some of errors/warnings with amd64 build logs and they are present in there= too.</div><div><br></div><div>I think I found a glitch at the end of arm64= log:</div><div>---</div><div>[zstd-sys 2.0.1+zstd.1.5.2] running: "ar= " "cq" "/wrkdirs/usr/ports...</div><div>(...)<br></div>= <div>=C2=A0"/wrkdirs/usr/ports/editors/lapce/<br>work/target/aarch64-u= nknown-freebsd/release/build/zstd-sys-97d70ebd740964f8/out/zstd/lib/decompr= ess/huf_decompress_<b>amd64</b>.o"</div><div>=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 ^^^^^<br></div><div>---<br></div><div>and zstd-sys-2.0.1+zs= td.1.5.2/zstd/lib/common/xxhash.h:</div><div># =C2=A0if (defined(__aarch64_= _) || defined(__arm64__) || defined(_M_ARM64) || defined(_M_ARM64EC)) \</di= v><div><br></div><div>So I presume that this crate should be build on arm64= /aarch64 but don't understant why it calls:</div><div>"huf_decompr= ess_<b>amd64</b>.o"</div><div><br></div><div>Any clues?<br></div><div>= <br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm= ail_attr">Mark Millard <<a href=3D"mailto:marklmi@yahoo.com">marklmi@yah= oo.com</a>> escreveu no dia quinta, 24/11/2022 =C3=A0(s) 04:46:<br></div= ><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border= -left:1px solid rgb(204,204,204);padding-left:1ex">Nuno Teixeira <<a hre= f=3D"http://eduardo_at_freebsd.org" rel=3D"noreferrer" target=3D"_blank">ed= uardo_at_freebsd.org</a>> wrote on<br> Date: Thu, 24 Nov 2022 00:33:24 UTC :<br> <br> > For some time I'm receiving errors from build servers about editor= s/lapce<br> > not building on arm64.<br> > <br> > From the log it seems [zstd-sys 2.0.1+zstd.1.5.2] crate failing.<br> > <br> > Is anybody with same problem?<br> > I need to be sure before open an issue at upstream.<br> > <br> > What I don't understad is that upstream provides aarch64 pre-compi= led<br> > binaries...<br> > <a href=3D"https://github.com/lapce/lapce/releases/tag/v0.2.4" rel=3D"= noreferrer" target=3D"_blank">https://github.com/lapce/lapce/releases/tag/v= 0.2.4</a><br> > <br> > <a href=3D"https://pkg-status.freebsd.org/ampere2/data/main-arm64-defa= ult/pf323e9d40f68_s41be508d31/logs/lapce-0.2.4.log" rel=3D"noreferrer" targ= et=3D"_blank">https://pkg-status.freebsd.org/ampere2/data/main-arm64-defaul= t/pf323e9d40f68_s41be508d31/logs/lapce-0.2.4.log</a><br> <br> <br> My ports tree is somewhat older but also produces the<br> unexplained "*** Error code 101" (as did the FreeBSD<br> build servers for the same version I'm testing here):<br> <br> # tail -20 /usr/local/poudriere/data/logs/bulk/main-CA72-default/2022-11-23= _18h50m22s/logs/errors/lapce-0.2.1.log<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= string_utils.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/ucp.h= <br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= ord2utf8.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= byte_order.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= fullinfo.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= compile.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= get.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= dfa_exec.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/<a hr= ef=3D"http://config.h.in" rel=3D"noreferrer" target=3D"_blank">config.h.in<= /a><br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= xclass.c<br> [libgit2-sys 0.13.4+1.4.2] cargo:rerun-if-changed=3Dlibgit2/deps/pcre/pcre_= globals.c<br> *** Error code 101<br> <br> Stop.<br> make: stopped in /usr/ports/editors/lapce<br> =3D>> Cleaning up wrkdir<br> =3D=3D=3D>=C2=A0 Cleaning for lapce-0.2.1<br> build of editors/lapce | lapce-0.2.1 ended at Wed Nov 23 19:20:37 PST 2022<= br> build time: 00:22:50<br> !!! build failure encountered !!!<br> <br> So may be the below will be suggestive/useful.<br> <br> <br> I'll note that the "*** Error code 101" ended up not being<br= > anyhwere near were the problems(!) actually were. So likely<br> for you the "zstd-sys 2.0.1+zstd.1.5.2" need not be one of<br> the actual failure places.<br> <br> <br> How I found the problems and what they look like . . .<br> <br> I did the bulk build with -w and expanded the tar:<br> <br> # mkdir -p /wrkdirs/usr/ports/editors/lapce<br> # tar -xpf /usr/local/poudriere/data/wrkdirs/main-CA72-default/default/lapc= e-0.2.1.tbz -C /wrkdirs/usr/ports/editors/lapce<br> <br> I then went exploring. What I eventually found is quickly shown<br> via:<br> <br> # find -s /wrkdirs/usr/ports/editors/lapce/ -name stderr -exec grep -l &quo= t;aborting due to previous error" {} \; | less<br> /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/cap-primitives-ed08064314a4640b/stderr<br> /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/cap-std-5acaec63374cb836/stderr<br> /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/io-extras-e83e1591d250cc25/stderr<br> /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/io-lifetimes-62b7366622512d7e/stderr<br> /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/system-interface-56dbb6efd7f0321e/stderr<br> <br> There could be non-empty stderr files with other text that are<br> also indications of failure. There are more stderr files. But<br> the other few that I looked at did not seem to be indicating<br> failures, more like informational/warning information.<br> <br> Text from some of the above stderr files:<br> <br> # less /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd= /debug/build/cap-primitives-ed08064314a4640b/stderr<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(windows_by_handle)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^<br> <br> error[E0635]: unknown feature `windows_by_handle`<br> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(windows_by_handle)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^<br> <br> error: aborting due to 2 previous errors<br> <br> Some errors have detailed explanations: E0554, E0635.<br> For more information about an error, try `rustc --explain E0554`.<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(windows_file_type_ext)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^<br> <br> error[E0635]: unknown feature `windows_file_type_ext`<br> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(windows_file_type_ext)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^<br> <br> error: aborting due to 2 previous errors<br> <br> Some errors have detailed explanations: E0554, E0635.<br> For more information about an error, try `rustc --explain E0554`.<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(io_error_more)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^<br> <br> error: aborting due to previous error<br> <br> For more information about this error, try `rustc --explain E0554`.<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(io_error_uncategorized)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^^<br= > <br> error: aborting due to previous error<br> <br> For more information about this error, try `rustc --explain E0554`.<br> <br> # less /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd= /debug/build/cap-std-5acaec63374cb836/stderr<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(can_vector)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^<br> <br> error: aborting due to previous error<br> <br> For more information about this error, try `rustc --explain E0554`.<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(seek_convenience)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^<br> <br> warning: the feature `seek_convenience` has been stable since 1.51.0 and no= longer requires an attribute to enable<br> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(seek_convenience)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^<br> =C2=A0 |<br> =C2=A0 =3D note: `#[warn(stable_features)]` on by default<br> <br> error: aborting due to previous error; 1 warning emitted<br> <br> For more information about this error, try `rustc --explain E0554`.<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(with_options)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^<br> <br> warning: the feature `with_options` has been stable since 1.58.0 and no lon= ger requires an attribute to enable<br> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(with_options)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^<br> =C2=A0 |<br> =C2=A0 =3D note: `#[warn(stable_features)]` on by default<br> <br> error: aborting due to previous error; 1 warning emitted<br> <br> For more information about this error, try `rustc --explain E0554`.<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:12<br> =C2=A0 |<br> 1 | #![feature(write_all_vectored)]<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^<br> <br> error: aborting due to previous error<br> <br> For more information about this error, try `rustc --explain E0554`.<br> <br> # less /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd= /debug/build/io-lifetimes-62b7366622512d7e/stderr<br> error[E0554]: `#![feature]` may not be used on the stable release channel<b= r> =C2=A0--> <anon>:1:1<br> =C2=A0 |<br> 1 | #![feature(rustc_attrs)]<br> =C2=A0 | ^^^^^^^^^^^^^^^^^^^^^^^^<br> <br> error: aborting due to previous error<br> <br> For more information about this error, try `rustc --explain E0554`.<br> warning: function `foo` is never used<br> =C2=A0--> <anon>:1:10<br> =C2=A0 |<br> 1 | const fn foo() { panic!() }<br> =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^<br> =C2=A0 |<br> =C2=A0 =3D note: `#[warn(dead_code)]` on by default<br> <br> warning: 1 warning emitted<br> <br> <br> <br> It looks like, for rust based builds, such a "search through<br> the stderr files" from a bulk -w like tar of the failure is<br> the basic technique needed to identify the actual problems<br> and where they were.<br> <br> =3D=3D=3D<br> Mark Millard<br> marklmi at <a href=3D"http://yahoo.com" rel=3D"noreferrer" target=3D"_blank= ">yahoo.com</a><br> <br> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g= mail_signature"><div dir=3D"ltr"><span style=3D"color:rgb(102,102,102)">Nun= o Teixeira<br>FreeBSD Committer (ports)</span></div></div> --000000000000d6d09d05ee355a5d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7ULKuSUETZS4WLs3%2Bcepn94%2BnagY2OitNWoLP-JNjZUOGA>