Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > alt.comp.software.seamonkey > #184
| From | Richmond <richmond@criptext.com> |
|---|---|
| Newsgroups | alt.comp.software.seamonkey |
| Subject | Re: Error compiling on i686 |
| Date | 2021-05-09 13:31 +0100 |
| Organization | Frantic |
| Message-ID | <84sg2wytpw.fsf@example.com> (permalink) |
| References | (5 earlier) <ifneprFqtr2U1@mid.individual.net> <s77cc0$dde$1@gioia.aioe.org> <841rag16mb.fsf@example.com> <84wns8yvoh.fsf@example.com> <ifq2amFbntqU1@mid.individual.net> |
frg <frgrahl@gmx.net> writes: > Richmond wrote: >> Richmond <richmond@criptext.com> writes: >> >>> frg <frg@gmx.com> writes: >>> >>>> frg wrote: >>>>> Richmond wrote: >>>>>> Andrew <Doug@hyperspace.vogon.gov> writes: >>>>>> >>>>>>> Richmond wrote: >>>>>>>> Andrew <Doug@hyperspace.vogon.gov> writes: >>>>>>>> >>>>>>>>> Richmond wrote: >>>>>>>>>> I am getting errors. This is the first of many. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Compiling idna v0.1.4 >>>>>>>>>> Compiling mp4parse_capi v0.10.1 >>>>>>>>>> (/home/seamonkey/mozilla-253/media/mp4parse-rust/mp4parse_capi) >>>>>>>>>> error[E0432]: unresolved import `simd_funcs` >>>>>>>>>> --> >>>>>>>>>> /home/seamonkey/mozilla-253/third_party/rust/encoding_rs/src/x_user_defined.rs:16:13 >>>>>>>>>> >>>>>>>>>> | >>>>>>>>>> 16 | use simd_funcs::*; >>>>>>>>>> | ^^^^^^^^^^ maybe a missing crate `simd_funcs`? >>>>>>>>>> >>>>>>>>> >>>>>>>>> What distribution are you using? >>>>>>>> >>>>>>>> Debian 10. It is still compiling... >>>>>>>> >>>>>>> >>>>>>> From what I've read elsewhere, Seamonkey levels starting 2.53.6 >>>>>>> require Rust >= 1.47 to build. There is no such requirement for >>>>>>> execution. >>>>>>> The reason I asked what distribution you were using is that the one I >>>>>>> use (not Debian) may be about to move from Rust 1.43.1 for just this >>>>>>> reason, then you would have had the option of waiting. >>>>>> >>>>>> Did you get that from these minutes? >>>>>> >>>>>> https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2021-04-18 >>>>>> >>>>>> "Compilers have been updated for building the official versions starting >>>>>> with 2.53.7b1 >>>>>> >>>>>> "rust 1.47.0 is used for all releases." >>>>>> >>>>>> This doesn't say it is a minimum requirement, just that these versions >>>>>> have been used in official builds. That's the way I am reading it >>>>>> anyway. I am not building an official build. I am just trying to make >>>>>> one which works. I think the problem I am having is due to SS2 >>>>>> instructions. Hopefully the disable-rust-simd will solve it as far as I >>>>>> can tell this is supposed to make rust platform independent. >>>>>> >>>>> >>>>> The minimum version is 1.38 which is enforced but it might not >>>>> work. If this does not work I will probably set it to 1.47 to align >>>>> with official builds. >>>>> >>>>> FRG >>>> >>>> We needed to fix some new breakage with rust 1.52 and the minimum rust >>>> version of 2.53.8 will be 1.47. >>>> >>>> FRG >>> >>> I get this error: >>> >>> 3:26.09 /usr/bin/ld: >>> i686-unknown-linux-gnu/release/libgkrust.a(std-3b8f769dfbb7c401.std.1qzgk10u-cgu.14.rcgu.o): >>> warning: relocation against `__rust_probestack' in read-only section >>> `.text._ZN3std2io4util4copy17h713ecddbd4fa0d0dE' >>> 3:26.09 /usr/bin/ld: read-only segment has dynamic relocations >>> >>> rustc --version >>> rustc 1.41.1 >>> >>> >>> So I am going to try upgrading rust. >> >> ./rustup-init >> Illegal instruction >> >> I give up. It looks like rust is not a high level language, but an >> overrated assembler. >> > > It is a work in progress alpha level language. Beta would imply that > it is halfway feature complete but then we would not have breakage > almost every release... Would love to get rid of it tomorrow. > > Usually you can do > rustup default 1.47.0-x86_64-unknown-linux-gnu > > and then just need to install the i686 target. > I can't install the rustup command because of illegal instructions. Nor can I compile rust from source. So I think I must either stay with an old version of SM or move my mail to a newer computer.
Back to alt.comp.software.seamonkey | Previous | Next — Previous in thread | Next in thread | Find similar
Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-06 22:40 +0100
Re: Error compiling on i686 frg <frg@gmx.com> - 2021-05-07 01:32 +0200
Re: Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-08 09:19 +0100
Re: Error compiling on i686 Andrew <Doug@hyperspace.vogon.gov> - 2021-05-07 11:23 +0200
Re: Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-07 21:10 +0100
Re: Error compiling on i686 Andrew <Doug@hyperspace.vogon.gov> - 2021-05-08 13:10 +0200
Re: Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-08 12:41 +0100
Re: Error compiling on i686 frg <frgrahl@gmx.net> - 2021-05-08 14:34 +0200
Re: Error compiling on i686 frg <frg@gmx.com> - 2021-05-09 03:02 +0200
Re: Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-09 18:26 +0100
Re: Error compiling on i686 frg <frgrahl@gmx.net> - 2021-05-09 23:02 +0200
Re: Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-09 12:36 +0100
Re: Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-09 12:48 +0100
Re: Error compiling on i686 frg <frgrahl@gmx.net> - 2021-05-09 14:19 +0200
Re: Error compiling on i686 Richmond <richmond@criptext.com> - 2021-05-09 13:31 +0100
Re: Error compiling on i686 frg <frg@gmx.com> - 2021-05-09 17:41 +0200
Re: Error compiling on i686 Dirk Fieldhouse <surname@gmx.net.removethisandtherest.example.com> - 2021-05-09 23:39 +0100
Re: Error compiling on i686 frg <frg@gmx.com> - 2021-05-10 01:03 +0200
Re: Error compiling on i686 Gunther Nikl <gnikl.invalid@invalid.justmail.de> - 2021-05-10 14:42 +0200
Re: Error compiling on i686 Andrew <Doug@hyperspace.vogon.gov> - 2021-05-08 16:21 +0200
csiph-web