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
Add mips64el-linux support #359
Comments
Attach file failed. the below is file contents. rbx.platform.typedef.__u_char = uchar |
I don't have access to a mips machine to test this. I'll try getting something together with qemu. I'm pretty sure more changes are necessary than just adding a types.conf. At least platform.rb will need updating as well. It would be great if you could put this all into a pull request and add the other necessary changes. |
It seems there is nothing about mips in platform.rb, so it may not needed. My mips64el porter box was broken few days ago, when it is ok, I will let On Fri, Aug 1, 2014 at 3:43 AM, tduehr notifications@github.com wrote:
YunQiang Su |
platform.rb contains the logic to select the right types and set the arch constants, changes will be needed. |
as far as I can tell, platform.rb contains a few special cases, but it should 'just' work on most Linux architectures. The mips* variants that already exist are not special cased in platform.rb and work. |
Okay, then I just need to get a working VM running for this to test in the future. |
Can you give me your ssh key, I can provide you a porterbox with ssh. On Wed, Aug 13, 2014 at 1:12 AM, tduehr notifications@github.com wrote:
YunQiang Su |
I'd like to get a qemu VM running for testing each of the platforms we support so the rest of the team can easily perform testing as well. I'll send my ssh key for now. |
I'm building VMs for future testing currently. What hardware platform are you targeting? If you have time, what's the closest qemu or yocto machine I can use? |
Put the attached file as
lib/ffi/platform/mips64el-linux/types.conf
it is generated by
debian/rules gen_arch_config
from Debian package
.
The text was updated successfully, but these errors were encountered: