-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Vxworks build error for current master branch. Need to update some source. #127084
Comments
Because it is both times referenced by the qualified rust/library/std/src/sys/pal/unix/process/process_vxworks.rs Lines 104 to 116 in 99f77a2
|
For the |
it seems originally @BaoshanPang was the maintainer of these targets. |
Remove unqualified form import of io::Error in process_vxworks.rs and fallback on remove_dir_impl for vxworks Hi all, This is to address issue rust-lang#127084. On inspections it was found that io::Error refrences were all of qualified form and there was no need to add a unqualified form import. Also to successfully build rust for vxworks, we need to fallback on the remove_impl_dir implementations. Thank you.
Why are there unsafe errors for unsafe blocks? If I add the whole fn as unsafe and remove unsafe blocks, I'm able to compile for vxworks. |
Rollup merge of rust-lang#127195 - biabbas:vxworks_cleanup, r=jhpratt Remove unqualified form import of io::Error in process_vxworks.rs and fallback on remove_dir_impl for vxworks Hi all, This is to address issue rust-lang#127084. On inspections it was found that io::Error refrences were all of qualified form and there was no need to add a unqualified form import. Also to successfully build rust for vxworks, we need to fallback on the remove_impl_dir implementations. Thank you.
The standard library denies all warnings in its build. One of the warnings the Rust compiler issues is "you added an |
But for vxworks somehow these are not disabled. Is this because we only build the libraries for vxworks. |
Somehow it thinks |
Pushed commits to build nightly for vxworks. Current stable source 1.79.0 can be built after applying this patch. |
Fix build failure on vxworks rust-lang#127084 PR to address issue rust-lang#127084 . 1. Skip `reset_segpipe` for vxworks 2. Return unimplemented error for vxworks from settimes and lchown 3. Temporarily skip dirfd for vxworks 4. Add allow unused unsafe on read_at and write_at functions in unix/fs.rs 5. Using cfg disable ON_BROKEN_PIPE_FLAG_USED and on_broken_pipe_flag_used() for vxworks 6. Remove old crate::syscommon::thread::min_stack() reference from process_vxworks.rs and update to set stack size of rtpthread Thank you.
…iaskrgr Rollup of 9 pull requests Successful merges: - rust-lang#126152 (size_of_val_raw: for length 0 this is safe to call) - rust-lang#127252 (Add edge-case examples to `{count,leading,trailing}_{ones,zeros}` methods) - rust-lang#127374 (Tweak "wrong # of generics" suggestions) - rust-lang#127457 (Make tidy fast without compromising case alternation) - rust-lang#127480 (Fix build failure on vxworks rust-lang#127084 ) - rust-lang#127733 (Replace some `mem::forget`'s with `ManuallyDrop`) - rust-lang#128120 (Gate `AsyncFn*` under `async_closure` feature) - rust-lang#128131 (Import `c_void` rather than using the full path) - rust-lang#128133 (Improve spans on evaluated `cfg_attr`s.) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#127480 - biabbas:vxworks, r=workingjubilee Fix build failure on vxworks rust-lang#127084 PR to address issue rust-lang#127084 . 1. Skip `reset_segpipe` for vxworks 2. Return unimplemented error for vxworks from settimes and lchown 3. Temporarily skip dirfd for vxworks 4. Add allow unused unsafe on read_at and write_at functions in unix/fs.rs 5. Using cfg disable ON_BROKEN_PIPE_FLAG_USED and on_broken_pipe_flag_used() for vxworks 6. Remove old crate::syscommon::thread::min_stack() reference from process_vxworks.rs and update to set stack size of rtpthread Thank you.
Hi all,
For target x86_64-wrs-vxworks, I'm not able to build rustc due to the following errors.
I'll be authoring some pr's to address some, but I have few doubts that I need help with. Thank you.
The text was updated successfully, but these errors were encountered: