- 01 Aug, 2018 1 commit
-
-
Adam Cozzette authored
This was fairly straightforward using the existing build-protoc.sh script. The only problem I ran into was that the x86 Docker builds create output directories owned by root, which caused some permission issues. Fortunately it was easy to get around that just by doing those Docker builds last.
-
- 30 Jul, 2018 1 commit
-
-
Adam Cozzette authored
I made a few small fixes to the documentation related to publishing protoc artifacts: - The target directory for Mac should be called osx instead of macos. - There needs to be a directory for aarch_64. - We need to avoid calling "mvn clean" inside the protoc-artifacts directory, since that will delete the contents of the target/ subdirectory.
-
- 27 Jul, 2018 1 commit
-
-
Adam Cozzette authored
-
- 17 Jul, 2018 2 commits
-
-
Eric Anderson authored
This avoids the need to use "yum update && yum upgrade" in the container to be able to contact GitHub, which requires TLS 1.2[1]. I have verified that binaries built with this container still run in the previous container; no errors like "/lib64/libc.so.6: version `GLIBC_2.14' not found", which occur if using too new of a glibc when compiling. CentOS 6.6 has glibc version 2.12 release 1.209.el6. CentOS 6.9 has glibc version 2.12 release 1.149.el6. Both would upgrade to release 1.212.el6 via "yum update && yum upgrade". 1. https://githubengineering.com/crypto-deprecation-notice/
-
Adam Cozzette authored
Now that we depend on C++11, we need at least GCC 4.8 instead of 4.7. This change updates the Docker setup to continue using CentOS 6.6 but with GCC 4.8. I also added libm to the whitelist for dynamically linked libraries for the ARM64 protoc binary.
-
- 16 Jul, 2018 3 commits
-
-
Feng Xiao authored
-
Feng Xiao authored
1. Changed maven script to only do artifact uploading and removed build script invocation from it. We didn't use maven to invoke the build script before (we built protoc manually and editted pom.xml to only do uploading for previous releases), and will not use it in the future (we will use kokoro to build artifacts). 2. Cleaned up build-protoc.sh and README.md: removed the part about using maven to build and listed supported platforms explicitly.
-
Feng Xiao authored
-
- 13 Jul, 2018 1 commit
-
-
Feng Xiao authored
1. Changed maven script to only do artifact uploading and removed build script invocation from it. We didn't use maven to invoke the build script before (we built protoc manually and editted pom.xml to only do uploading for previous releases), and will not use it in the future (we will use kokoro to build artifacts). 2. Cleaned up build-protoc.sh and README.md: removed the part about using maven to build and listed supported platforms explicitly.
-
- 07 Jul, 2018 2 commits
-
-
nashimus authored
-
Eric Anderson authored
This avoids the need to use "yum update && yum upgrade" in the container to be able to contact GitHub, which requires TLS 1.2[1]. I have verified that binaries built with this container still run in the previous container; no errors like "/lib64/libc.so.6: version `GLIBC_2.14' not found", which occur if using too new of a glibc when compiling. CentOS 6.6 has glibc version 2.12 release 1.209.el6. CentOS 6.9 has glibc version 2.12 release 1.149.el6. Both would upgrade to release 1.212.el6 via "yum update && yum upgrade". 1. https://githubengineering.com/crypto-deprecation-notice/
-
- 06 Jul, 2018 1 commit
-
-
Adam Cozzette authored
Now that we depend on C++11, we need at least GCC 4.8 instead of 4.7. This change updates the Docker setup to continue using CentOS 6.6 but with GCC 4.8. I also added libm to the whitelist for dynamically linked libraries for the ARM64 protoc binary.
-
- 14 May, 2018 1 commit
-
-
Jisi Liu authored
-
- 02 Apr, 2018 1 commit
-
-
Paul Yang authored
* Fix setup.py for windows build. * Bump version number to 3.5.2 * Cat the test-suite.log on errors for presubits
-
- 29 Mar, 2018 3 commits
-
-
Eric Anderson authored
ENTRYPOINT is used even when other commands are specified on the "docker run" command line. This allows running one-off commands in the docker image (especially combined with volume binding with the host) with the correct environment variables.
-
Eric Anderson authored
This is just better Dockerfile hygene as it produces smaller resulting images with fewer useless files.
-
Eric Anderson authored
It is a bad idea to check out code into the docker image, as it will be out-of-date. It is better to have the image just be the environment, and let any scripts that need source check them out themselves. This fixes #4419 in that it allows the image to build again, albeit users would need to use wget to grab the source of the version of protobuf they wish.
-
- 22 Mar, 2018 1 commit
-
-
pravin-dsilva authored
-
- 06 Mar, 2018 1 commit
-
-
Bo Yang authored
-
- 05 Jan, 2018 1 commit
-
-
Jisi Liu authored
-
- 19 Dec, 2017 1 commit
-
-
Jisi Liu authored
-
- 13 Nov, 2017 2 commits
- 10 Nov, 2017 2 commits
- 02 Nov, 2017 1 commit
-
-
Jisi Liu authored
-
- 14 Sep, 2017 1 commit
-
-
Jisi Liu authored
-
- 15 Aug, 2017 4 commits
- 24 Jul, 2017 1 commit
-
-
Jisi Liu authored
-
- 18 Jul, 2017 1 commit
-
-
Daniel Taylor authored
Ran into an issue today where a machine had the `protoc` compiler but not the include files. Took a while to sort out, and this added note to the README included in every zip should help.
-
- 05 Jul, 2017 1 commit
-
-
Eric Anderson authored
The update 45 download process no longer works, as it requires a login to access the old build.
-
- 21 Jun, 2017 1 commit
-
-
Bo Yang authored
-
- 11 May, 2017 1 commit
-
-
Łukasz Strzałkowski authored
This is a workaround (https://github.com/moby/moby/issues/10180#issuecomment-190429512) the docker issue (https://github.com/moby/moby/issues/10180) which breaks protoc-artifacts build process with following error ```Rpmdb checksum is invalid: dCDPT(pkg checksums): devtoolset-1.1-elfutils.x86_64 0:0.154-6.el6 - u The command '/bin/sh -c yum clean all && yum install -y devtoolset-1.1 devtoolset-1.1-libstdc++-devel devtoolset-1.1-libstdc++-devel.i686' returned a non-zero code: 1``` https://github.com/moby/moby/issues/10180#issuecomment-190429512
-
- 08 May, 2017 1 commit
-
-
Feng Xiao authored
-
- 06 Apr, 2017 1 commit
-
-
Feng Xiao authored
-
- 28 Feb, 2017 2 commits
-
-
Sebastian Schuberth authored
The first is the newer name, which is also more telling.
-
Sebastian Schuberth authored
The "New BSD License" is the "3-Clause BSD License", but the links were pointing to the "2-Clause BSD License".
-