-
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
Cross building doesn't work for alpine3.7 #20
Comments
@TeBoring , @nicolasnoble Have you been able to solve the compatibility issue between Alpine linux and binary gems for protobuf? |
In our continuous test, we found ruby 2.5.0 has internal error that can cause protobuf's test to fail on segment fault. |
rake-compiler doesn't recognize 2.5 as a version spec, but only 2.5.0 in RUBY_CC_VERSION. On the other hand, only the the header files of the cross ruby version are relevant, since the libruby.dll file of the cross build is replaced by the libruby.dll of the runtime ruby version, later on. That's why there's usually no need to update minor versions of the cross rubies. Do you know whether the segfault is related to the header files? If so I'll have to find a way to update cross rubies, without breaking 3-part version specs of dependent projects. |
Sorry, I don't know if it's the header file that caused the problem. |
Changing |
The gem built by the new docker image still doesn't work. |
docker-library/ruby#196 |
I noticed that the gem we built using rake-compiler-dock is linking against glibc. |
musl and glibc are both named the same way in the filesystem, and are nearly interchangeable. Emphasis on nearly. It's possible if difficult to build binaries that work for both, but it's honestly a lot of work. The fault here really lies in the |
Nokogiri is running fine on Alpine, but required a change to |
I used this docker to build gem for protobuf. However, when running the linux gem on alpine3.7 docker, there is segmentation fault. If I build the gem on alpine 3.7 directly, there is no segmentation fault.
For more details see protocolbuffers/protobuf#4460
The text was updated successfully, but these errors were encountered: