the first I had in mind was...
"Another (LLVM/CLang) realease - a new drama!"
( See Byron Katie "The work". )
I know SVN is your 1st development platform.
Personally, I prefer Git and use the LLVM/Clang mirrors on GitHub.
Unfortunately, I am missing a "release_381" branch at all on the
GitHub repositories.
I looked through the llvm-commits [1] and I only see two emails with
the subject...
"Creating release candidate final from release_381 branch"
[test-suite] r273407 - Creating release candidate final from
release_381 branch Tom Stellard via llvm-commits
[lld] r273414 - Creating release candidate final from release_381
branch Tom Stellard via llvm-commits
So, how should I know which is the corresponding SVN-commit-id for
tagging myself in my local [llvm | clang | compiler-rt]
Git-repositories?
Which files have to be changed to get a correct version-string when
invoking "clang -v" or 'clang --version" (here: "3.8.1")?
( I had that problem with "3.8.0rc3" in my local Git repos, I got
displayed "3.8.0" as a version-string )
Do you have source-tarballs released?
If yes, can you point me to a URL?
Can you or Tom (as release-manager) answer why there were no
commit-ids (release_381 SVN branch) sent to llvm-commits ML?
Can you answer my question on how to set the version-string correct
when generating tarballs out of the release_38 Git branch?
( I generated source-tarballs out of my local Git repositories, see below. )
- Sedat -
[ INSTRUCTIONS: GENERATE TARBALLS OUT OF GIT REPOSITORY WITH GIT-ARCHIVE ]
[ Here: Release v3.8.1 and tagged Git-commit-ids ]
Can you answer my question on how to set the version-string correct
when generating tarballs out of the release_38 Git branch?
( I generated source-tarballs out of my local Git repositories, see below. )
[ llvm.src/CMakeLists.txt ]
...
if(NOT DEFINED LLVM_VERSION_MAJOR)
set(LLVM_VERSION_MAJOR 3)
endif()
if(NOT DEFINED LLVM_VERSION_MINOR)
set(LLVM_VERSION_MINOR 8)
endif()
if(NOT DEFINED LLVM_VERSION_PATCH)
set(LLVM_VERSION_PATCH 1)
endif()
if(NOT DEFINED LLVM_VERSION_SUFFIX)
set(LLVM_VERSION_SUFFIX "")
endif()
...
What you're probably missing is that 3.8.1 is made in release_38
branch. So, everything is there and already mirrored.
Source tarballs will be available upon the release.
Which are just coming, now that final has been tested successfully.
They'll be announced in the list and available here: LLVM Download Page
Thanks you both for your answers.
Can you or Tom (as release-manager) answer why there were no
commit-ids (release_381 SVN branch) sent to llvm-commits ML?
Please wait for the official release to happen, you will then find tarballs on
llvm.org. They will also contain correct version strings, though I haven't yet
tried building from the SVN branches directly. Maybe you need to use the SVN
tags, $ clang --version currently gives me "clang version 3.8.0
(tags/RELEASE_380/final)")
This was reported earlier and it's unfortunate, but we don't support
autotools build any more. The official releases are made using CMake
and most of the buildbots are using it.
Feel free to apply a patch on top of the release to change that if you
must build with autotools.
OK, I clicked the offline version of that ML on the main-page of
<llvm.org>, so I knew of it.
Anyway, I think most people use Git these days.
Please wait for the official release to happen, you will then find tarballs on
llvm.org. They will also contain correct version strings, though I haven't yet
tried building from the SVN branches directly. Maybe you need to use the SVN
tags, $ clang --version currently gives me "clang version 3.8.0
(tags/RELEASE_380/final)")
In the meantime I created source-tarballs out of my local Git repos
and built a llvm-toolchain v3.8.1 successfully.
I will test it with my local version of "llvmlinux-amd64" Linux-kernel.
It should be 145MB. I've just checked the copy I uploaded to the sftp server and it's the right size there so I guess it hasn't been fully transferred from there to the web server.
[ CCed all people who were involved in this thread ]
Hi Tom,
personally, I am interested to test the prebuilt-toolchains for
Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64.
The available toolchains are incomplete and thus useless.
Just as a fact: There is still no compiler-rt source-tarball available.
I know of Linux distributions which refuse to build and upload new
packages when there are no official tarballs around.
Can you please - as the release-manager of LLVM v3.8.1 - care of
uploading missing and/or incomplete source-tarballs and/or
prebuilt-toolchains?
( "Care" in the sense of you know whom to poke. )
