LLVM 3.2 came as a nice Christmas present. Just one minor question: I noticed that the version string (used to name the shared library etc.) is "3.2svn" instead of the expected "3.2". This violates our build system's expectations of what things are called. It would be easy for us to change, but I want to make sure this is not a mistake. I am fairly certain I downloaded the right tarball. How should we proceed? thanks, -Jeff
Jeff Bezanson <jeff.bezanson at gmail.com> writes:> LLVM 3.2 came as a nice Christmas present. Just one minor question: I > noticed that the version string (used to name the shared library etc.) > is "3.2svn" instead of the expected "3.2". This violates our build > system's expectations of what things are called. It would be easy for > us to change, but I want to make sure this is not a mistake. I am > fairly certain I downloaded the right tarball. How should we proceed?If you are building with CMake try editing the CMakeLists.txt file on the top level of the source tree and removing `svn' from set(PACKAGE_VERSION "${LLVM_VERSION_MAJOR}.${LLVM_VERSION_MINOR}svn") Filing a bug report explaining the problem would be useful for avoiding the same mistake on the next release.
On Tue, Dec 25, 2012 at 2:21 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:> Filing a bug report explaining the problem would be useful for avoiding > the same mistake on the next release.Better yet, add to <http://llvm.org/docs/HowToReleaseLLVM.html> (or at least mention it in the bug report so that it will be updated). -- Sean Silva
Seemingly Similar Threads
- [LLVMdev] 3.2 version string
- [LLVMdev] [PATCH] CMake: Use LLVM_VERSION_SUFFIX instead of hardcoded "svn" string
- [LLVMdev] [PATCH] CMake: Use LLVM_VERSION_SUFFIX instead of hardcoded "svn" string
- Understanding the version handling in LLVM/Clang/LLD
- 10.0.1-rc1 release has been tagged