-
Notifications
You must be signed in to change notification settings - Fork 15
Exclude libc / libm / ld-linux from the tarball #496
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
Conversation
|
To believe me: will happily show that |
|
When I build DDS with this, then the agent fails to start with: And if I run it in lightweight mode, then not even the DDSWorker.sh gets shipped to the node and nothing can start. |
|
@lkrcal Is this on top of master or 3.13? |
|
On my box I get: Which I think it's what's expected no? ldd also report what I would expect as libraries: |
|
To me the patch makes perfect sense. What Lubos is getting is something else. I will check that too. |
One cannot simply ship libc and ld-linux.so and hope they will be picked up correctly. In particular, ld-linux will always be the one of the system, because it gets loaded first by the kernel, when the executable is not yet around. This means that the current approach fails when the shipped libc is not compatible with the system ld-linux. It's much safer to simply not ship libc at all and pickup the system version.