Date: Fri, 25 Nov 2022 16:16:02 +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: <CAFDf7UJ_1M%2BWFRZKxzLiY6by5fnwJsqePMuai_C7Qi7rMcJALA@mail.gmail.com> In-Reply-To: <D8C48CA3-665D-434E-AB9E-496451B0DA5B@yahoo.com> References: <96078C14-CBEB-4450-ACE1-EB0488DD1814.ref@yahoo.com> <96078C14-CBEB-4450-ACE1-EB0488DD1814@yahoo.com> <CAFDf7ULKuSUETZS4WLs3%2Bcepn94%2BnagY2OitNWoLP-JNjZUOGA@mail.gmail.com> <7AB31838-8D70-4D48-A1F8-2FE8C8E7AA0E@yahoo.com> <D8C48CA3-665D-434E-AB9E-496451B0DA5B@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000002db3e005ee4dd757 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ok, I'm a little lost... What you think about a short error message to send to upstream: --- 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`. --- with link to full log. Thanks Mark Millard <marklmi@yahoo.com> escreveu no dia quinta, 24/11/2022 =C3=A0(= s) 17:27: > On Nov 24, 2022, at 07:00, Mark Millard <marklmi@yahoo.com> wrote: > > > On Nov 24, 2022, at 03:03, Nuno Teixeira <eduardo@freebsd.org> wrote: > > > >> Hello Mark, > > Hello. > > >> I have compared some of errors/warnings with amd64 build logs and they > are present in there too. > > Interesting. > > >> 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-97d70ebd740964= f8/out/zstd/lib/decompress/huf_decompress_amd64.o" > >> > > ^^^^^ > > Well, in my older context, > > # grep "^#" > /wrkdirs/usr/ports/editors/lapce/work/lapce-0.2.1/cargo-crates/zstd-sys-2= .0.1+zstd.1.5.2/zstd/lib/decompress/huf_decompress_amd64.S > | grep -v "#define " > #include "../common/portability_macros.h" > #if defined(__ELF__) && defined(__GNUC__) > #endif > #if ZSTD_ENABLE_ASM_X86_64_BMI2 > #undef GET_NEXT_DELT > #undef DECODE_FROM_DELT > #undef DECODE > #undef RELOAD_BITS > #undef DECODE > #undef RELOAD_BITS > #endif > > The #endif is the last line of the file and, ignoring > comments and blank lines for the most part, the rest > of the file before/at the #if ZSTD_ENABLE_ASM_X86_64_BMI2 > is just: > > #include "../common/portability_macros.h" > > /* Stack marking > * ref: https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart > */ > #if defined(__ELF__) && defined(__GNUC__) > .section .note.GNU-stack,"",%progbits > #endif > > #if ZSTD_ENABLE_ASM_X86_64_BMI2 > > > Looks like the ZSTD_ENABLE_ASM_X86_64_BMI2 test would eliminate the > amd64 specifics in an aarch64 context, so they do not bother avoiding > the file. > > > >> --- > >> 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? > > > > Not at this point. I've got the system rebuilding the > > port so I can set up to look again. > > > >> . . . > > FYI: the better string for searching got: > > # find -s /wrkdirs/usr/ports/editors/lapce/ -name stderr -exec grep -l > "aborting due to" {} \; | less > > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/cap-fs-ext-10fe2c1f66453130/stderr > > /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 > > The first line of the output is new compared to before: > > # more > /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debu= g/build/cap-fs-ext-10fe2c1f66453130/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`. > > So, not a new type of error compared to the others. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --=20 Nuno Teixeira FreeBSD Committer (ports) --0000000000002db3e005ee4dd757 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Ok, I'm a little lost...</div><div><br></div><div= >What you think about a short error message to send to upstream:</div><div>= ---</div><div><span class=3D"gmail-im">error[E0554]: `#![feature]` may not = be used on the stable release channel<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[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`.</span></d= iv><div><span class=3D"gmail-im">---<br></span></div><div>with link to full= log.<br></div><div><br></div><div>Thanks<br></div></div><br><div class=3D"= gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Mark Millard <<a href= =3D"mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>> escreveu no dia qui= nta, 24/11/2022 =C3=A0(s) 17:27:<br></div><blockquote class=3D"gmail_quote"= style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p= adding-left:1ex">On Nov 24, 2022, at 07:00, Mark Millard <<a href=3D"mai= lto:marklmi@yahoo.com" target=3D"_blank">marklmi@yahoo.com</a>> wrote:<b= r> <br> > On Nov 24, 2022, at 03:03, Nuno Teixeira <<a href=3D"mailto:eduardo= @freebsd.org" target=3D"_blank">eduardo@freebsd.org</a>> wrote:<br> > <br> >> Hello Mark,<br> <br> Hello.<br> <br> >> I have compared some of errors/warnings with amd64 build logs and = they are present in there too.<br> <br> Interesting.<br> <br> >> I think I found a glitch at the end of arm64 log:<br> >> ---<br> >> [zstd-sys 2.0.1+zstd.1.5.2] running: "ar" "cq"= "/wrkdirs/usr/ports...<br> >> (...)<br> >> "/wrkdirs/usr/ports/editors/lapce/<br> >> work/target/aarch64-unknown-freebsd/release/build/zstd-sys-97d70eb= d740964f8/out/zstd/lib/decompress/huf_decompress_amd64.o"<br> >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =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> <br> Well, in my older context,<br> <br> # grep "^#" /wrkdirs/usr/ports/editors/lapce/work/lapce-0.2.1/car= go-crates/zstd-sys-2.0.1+zstd.1.5.2/zstd/lib/decompress/huf_decompress_amd6= 4.S | grep -v "#define "<br> #include "../common/portability_macros.h"<br> #if defined(__ELF__) && defined(__GNUC__)<br> #endif<br> #if ZSTD_ENABLE_ASM_X86_64_BMI2<br> #undef GET_NEXT_DELT<br> #undef DECODE_FROM_DELT<br> #undef DECODE<br> #undef RELOAD_BITS<br> #undef DECODE<br> #undef RELOAD_BITS<br> #endif<br> <br> The #endif is the last line of the file and, ignoring<br> comments and blank lines for the most part, the rest<br> of the file before/at the #if ZSTD_ENABLE_ASM_X86_64_BMI2<br> is just:<br> <br> #include "../common/portability_macros.h"<br> <br> /* Stack marking<br> =C2=A0* ref: <a href=3D"https://wiki.gentoo.org/wiki/Hardened/GNU_stack_qui= ckstart" rel=3D"noreferrer" target=3D"_blank">https://wiki.gentoo.org/wiki/= Hardened/GNU_stack_quickstart</a><br> =C2=A0*/<br> #if defined(__ELF__) && defined(__GNUC__)<br> .section .note.GNU-stack,"",%progbits<br> #endif<br> <br> #if ZSTD_ENABLE_ASM_X86_64_BMI2<br> <br> <br> Looks like the ZSTD_ENABLE_ASM_X86_64_BMI2 test would eliminate the<br> amd64 specifics in an aarch64 context, so they do not bother avoiding<br> the file.<br> <br> <br> >> ---<br> >> and zstd-sys-2.0.1+zstd.1.5.2/zstd/lib/common/xxhash.h:<br> >> #=C2=A0 if (defined(__aarch64__) || defined(__arm64__) || defined(= _M_ARM64) || defined(_M_ARM64EC)) \<br> >> <br> >> So I presume that this crate should be build on arm64/aarch64 but = don't understant why it calls:<br> >> "huf_decompress_amd64.o"<br> >> <br> >> Any clues?<br> > <br> > Not at this point. I've got the system rebuilding the<br> > port so I can set up to look again.<br> > <br> >> . . .<br> <br> FYI: the better string for searching got:<br> <br> # find -s /wrkdirs/usr/ports/editors/lapce/ -name stderr -exec grep -l &quo= t;aborting due to" {} \; | less<br> /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd/debug/= build/cap-fs-ext-10fe2c1f66453130/stderr<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> The first line of the output is new compared to before:<br> <br> # more /wrkdirs/usr/ports/editors/lapce/work/target/aarch64-unknown-freebsd= /debug/build/cap-fs-ext-10fe2c1f66453130/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> <br> So, not a new type of error compared to the others.<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> --0000000000002db3e005ee4dd757--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7UJ_1M%2BWFRZKxzLiY6by5fnwJsqePMuai_C7Qi7rMcJALA>