-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeBSD cycle detected when const-evaluating #157
Comments
I tried the following quick hack to bypass build.rs: -#[cfg(any(target_os = "windows", target_os = "macos"))]
+#[cfg(any(target_os = "windows", target_os = "macos", target_os = "freebsd"))]
fn get_ioctl_data() {}
-#[cfg(not(any(target_os = "windows", target_os = "macos")))]
+#[cfg(not(any(target_os = "windows", target_os = "macos", target_os = "freebsd")))]
fn get_ioctl_data() {
let ioctl_dir = Path::new(&env::var("OUT_DIR").unwrap()).join("ioctl-data"); Compilation proceeded even further but it still produces an error:
So unfortunately I don't think there is a quick-fix. Currently FreeBSD is compiled as if it were Linux, but FreeBSD doesn't have an ioctl parallel to |
@nabijaczleweli You mentioned over in #158
Can you clarify which part is "incredibly annoying" about porting this from C++ to Rust? Is it the fact that macro-expanding requires invoking cc in build.rs? I'm wondering if perhaps we could pre-expand it to a constant and trust that the constant is unlikely to change. If you take a look at git-blame for FreeBSD's |
"Closes:" tag closed the PR but not the issue? Must be a wednesday in githubland. Anyway, try with current develop (at least be7de13)? |
Excellent, be7de13 works for me, thanks for looking into this! |
Released in |
I get the following error both when running
cargo install https
andgit clone ... && cd http && cargo build
(i.e. latest commit on master branch)I'm not exactly sure what your build.rs is doing, but FreeBSD has the function getbsize which might be helpful here?
Meta
rustc --version --verbose
:cargo --version --verbose
uname -imrs
The text was updated successfully, but these errors were encountered: