-
Notifications
You must be signed in to change notification settings - Fork 355
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
Original docker build had clear-execstack and stripping - new one does not have #311
Comments
Yeah, I have a point about it on my todo list. Thanks for mentioning. |
@drywolf thanks I may also contribute but now I really want to fix #306 as well, following fixes for #310 and #308. Docker builds: Our warning in PROD:
|
@matiwinnetou Thanks for the hints. |
@drywolf Yeah indeed, I have to confess I changed my mind mostly due to issues with linking GCLIB library. We had exception in our integration system where we run debian jessie in our legacy integration system and we ran into linking issues. Previous build system from @irbull was based on Debian Jessie. Ubuntu 16.04 LTS is already a stretch goal but our new setup with new infrastructure supports docker containers so in theory we can pick newer distrubutions for individual applications. CMake will have to be sadly installed manually or we find some backport in Ubuntu 16.04 LTS. Do you know if when using other software like maven we can piggy back on distro's software rather than installing own versions? |
"Stripped and non-stripped symbols for some / all platforms (this reduces the size, but makes debugging harder), I think this should be a configuration param to python script. We probably would not want to strip symbols now because library is not 100% stable yet and it really help to have more debugging info now. |
- register atexit events before cross-builds are started - switched linux & android docker images to Ubuntu Xenial LTS (see eclipsesource#311) - cleaned up and documented switch-to-winrm-plugin that is used in win32:vagrant builds
- register atexit events before cross-builds are started - switched linux & android docker images to Ubuntu Xenial LTS (see eclipsesource#311) - cleaned up and documented switch-to-winrm-plugin that is used in win32:vagrant builds
- register atexit events before cross-builds are started - switched linux & android docker images to Ubuntu Xenial LTS (see eclipsesource#311) - cleaned up and documented switch-to-winrm-plugin that is used in win32:vagrant builds
- register atexit events before cross-builds are started - switched linux & android docker images to Ubuntu Xenial LTS (see #311) - cleaned up and documented switch-to-winrm-plugin that is used in win32:vagrant builds
- register atexit events before cross-builds are started - switched linux & android docker images to Ubuntu Xenial LTS (see #311) - cleaned up and documented switch-to-winrm-plugin that is used in win32:vagrant builds
We are getting warnings that J2V8 has been complied without execstack -c.
from original docker docker/Dockerfile.linux:
@drywolf shall we include this in new build system?
The text was updated successfully, but these errors were encountered: