You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
warning: use of deprecated type alias `libc::time_t`: This type is changed to 64-bit in musl 1.2.0, we'll follow that change in the future release. See #1848 for more info.
--> vm/src/stdlib/time.rs:499:48
|
499 | tv_sec: time / (SEC_TO_NS as libc::time_t),
But the actual error which terminates the compilation is this:
error[E0063]: missing fields `sched_ss_init_budget`, `sched_ss_low_priority`, `sched_ss_max_repl` and 1 other field in initializer of `sched_param`
--> vm/src/stdlib/posix.rs:571:16
|
571 | Ok(libc::sched_param { sched_priority })
| ^^^^^^^^^^^^^^^^^ missing `sched_ss_init_budget`, `sched_ss_low_priority`, `sched_ss_max_repl` and 1 other field
For more information about this error, try `rustc --explain E0063`.
warning: `rustpython-vm` (lib) generated 9 warnings
...
For further context / background:
What I'm attempting to do is to get a recent python version over on the really ancient debian4 environment, which is also running in a 32-bit environment. The python version shipping there is 2.4.
At the moment I'm attempting to find a more recent alternative. I've seen that basic rust "hello world" cross-compiles work. But most other languages and ecosystems I've tested, no longer target or compile that really ancient environment. Even go-lang binaries targeting linux 32-bit fail with runtime panics on the environment, probably due to needing underlying linux system calls to be present, even though there is no actual libc dependency and the target binary is static. Target platform linux version is 2.6.30-1-686, and gcc version is 4.1.1
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I'm using rustc 1.61.0, and RustPython on git devel (currently f84b289). I'm running on Debian Unstable, on an amd64.
Was prompted by the compile to install musl-related compile utilities, so I have these versions installed from the Debian Unstable repo:
This command works as demonstrated:
cargo run --release demo.py
This command fails during compilation:
cargo run --target=i686-unknown-linux-musl --release demo.py
The error is during this compile step:
Compiling rustpython-compiler v0.1.2 (/home/david/dev/misc/github/RustPython/compiler/porcelain)
And there are a bunch of warnings like this:
But the actual error which terminates the compilation is this:
...
For further context / background:
What I'm attempting to do is to get a recent python version over on the really ancient debian4 environment, which is also running in a 32-bit environment. The python version shipping there is 2.4.
At the moment I'm attempting to find a more recent alternative. I've seen that basic rust "hello world" cross-compiles work. But most other languages and ecosystems I've tested, no longer target or compile that really ancient environment. Even go-lang binaries targeting linux 32-bit fail with runtime panics on the environment, probably due to needing underlying linux system calls to be present, even though there is no actual libc dependency and the target binary is static. Target platform linux version is 2.6.30-1-686, and gcc version is 4.1.1
The text was updated successfully, but these errors were encountered: