error: 'sysinfo not supported on this platform' in FreeBSD

[wisonye]

Problem

Hi there, there is some problems when installing and running Rust in FreeBSD.
I've already tried that on my son's laptop.

When installing rust via the command show in official website:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

It prints out many error: 'sysinfo not supported on this platform' in FreeBSD. When I add some components, it also show that error like below:

---

After installing, can compile and run rust code with no any problem. But I installed cargo-watch as well,
and it delay a few seconds to detect the file change, no sure relate the above error or not :)

uname -a output in his laptop:

FreeBSD mike-bsd 13.0-CURRENT FreeBSD 13.0-CURRENT #0 main-c255460-g282381aa53a: Thu Dec 31 06:08:47 UTC 2020     [email protected]:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

Notes

Output of rustup --version:

rustup 1.23.1 (3df2264a9 2020-11-30)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.49.0 (e1884a8e3 2020-12-29)`

Output of rustup show:

Default host: x86_64-unknown-freebsd
rustup home:  /home/mike/.rustup

stable-x86_64-unknown-freebsd (default)
rustc 1.49.0 (e1884a8e3 2020-12-29)

[kinnison]

We use effective-limits which is currently on sys-info version 0.6. I think 0.7 introduces FreeBSD support. @rbtcollins what would be involved in updating effective-limits ?

[rbtcollins]

get an update PR for effective-limits that passes CI

[wisonye]

@rbtcollins Any update? :)

[rbtcollins]

I'm not working on this

[kinnison]

I have filed rbtcollins/effective-limits.rs#13 which, if it turns out okay will permit a future release of effective-limits to include freebsd support.

[wisonye]

I have filed rbtcollins/effective-limits.rs#13 which, if it turns out okay will permit a future release of effective-limits to include freebsd support.

👍 Thanks for doing that, and I take that as a solved answer, feel free to close this issue if needed.

[kinnison]

I think that this issue shouldn't be closed until the effective-limits release is done and we've updated rustup to use the new version.

[Freaky]

@wisonye Your cargo-watch delays are due to the notify crate using a fallback polling-based approach, basically running a walkdir every few seconds (notify-rs/notify#273).

I had a standalone proof-of-concept directory watcher using kqueue, but didn't take it very far.

[wisonye]

@wisonye Your cargo-watch delays are due to the notify crate using a fallback polling-based approach, basically running a walkdir every few seconds (notify-rs/notify#273).

I had a standalone proof-of-concept directory watcher using kqueue, but didn't take it very far.

Wow, thanks for the point out. The cargo-watch is a very handy tool for me, basically, open rust in vim and the cargo-watch at the same time. I'm lucky not happen on Arch and MacOS which it's my OS, the FreeBSD just my boy's study choice, but still hope that will happen one day 👍

[workingjubilee]

@rustbot label: +O-bsd

[Darksonn]

See also: #2774

[kinnison]

On the basis that the actual error has been fixed, I'm closing this, but we do want to update to a new effective-limits when one is released using a newer sysinfo.

[xcaptain]

rustup 1.24.3 still has this error, please release a new version soon, thanks!

[VladasZ]

It is still not fixed. Any updates or at least a workaround?

[jclulow]

Hi. What's the timeline on a new release (e.g., a 1.24.4) that includes this fix? It is the number one source of reported confusion we get from illumos users and I assume from users on other platforms like FreeBSD.

[kinnison]

@jclulow I've had a pretty mad year, but I'm starting to work through the bits left before I can do a release. My hope is "pretty soon" for an unquantifiable value of that.