Skip to content

Adding dl_iterate_phdr function to uclibc #1967

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

Merged
merged 1 commit into from
Nov 2, 2020
Merged

Conversation

tsidea
Copy link
Contributor

@tsidea tsidea commented Oct 31, 2020

Adding dl_iterate_phdr function and related structs and types to the
uclibc module as per the file include/link.h found in the uClibc-ng
repository as of version 1.0.36. This is necessary in order for rust to
work with a new target armv7-unknown-linux-uclibceabihf.

Adding dl_iterate_phdr function and related structs and types to the
uclibc module as per the file include/link.h found in the uClibc-ng
repository as of version 1.0.36. This is necessary in order for rust to
work with a new target armv7-unknown-linux-uclibceabihf.
@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @JohnTitor (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@tsidea
Copy link
Contributor Author

tsidea commented Oct 31, 2020

The only problem I have is that I couldn't figure out how to cross compile libc-test for the new target armv7-unknown-linux-uclibceabihf I have created locally. I managed however to compile std and my own project for this new target. I even compiled my project's tests for this new target, but not libc-test. Actually, I tried cross compiling libc-test for armv7-unknown-linux-gnueabihf as well, which is an existing target and I couldn't do that either.

Copy link
Member

@JohnTitor JohnTitor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Comment on lines +338 to +342
// As of uClibc 1.0.36, the following fields are
// gated behind a "#if 0" block which always evaluates
// to false. So I'm just commenting these out and if uClibc changes
// the #if block in the future to include the following fields, these
// will probably need including here. tsidea
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@JohnTitor
Copy link
Member

The only problem I have is that I couldn't figure out how to cross compile libc-test for the new target armv7-unknown-linux-uclibceabihf I have created locally. I managed however to compile std and my own project for this new target. I even compiled my project's tests for this new target, but not libc-test. Actually, I tried cross compiling libc-test for armv7-unknown-linux-gnueabihf as well, which is an existing target and I couldn't do that either.

libc-test for ARM targets needs to be run on qemu via Docker IIRC. You could see some other targets using qemu and Docker.

@JohnTitor
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Nov 2, 2020

📌 Commit f3aab7a has been approved by JohnTitor

@bors
Copy link
Contributor

bors commented Nov 2, 2020

⌛ Testing commit f3aab7a with merge 338eebb...

@bors
Copy link
Contributor

bors commented Nov 2, 2020

☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing 338eebb to master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants