similar to: Tarballs for 3.9.1rc2 pre-release

On Sat, Dec 3, 2016 at 3:56 PM, Hahnfeld, Jonas <Hahnfeld at itc.rwth-aachen.de> wrote: > Hi Sedat, > > as already said multiple times for the past releases: The tarballs will be > uploaded once they are finished. The tagged version currently gets tested > which is done with an export from SVN AFAIK. > > Please just be patient and give the process some time, With the

Yeah, I see. You have an unusual development process seen from my POV. IMHO you can provide the tarballs before the "binaries" are uploaded which means "prebuilt binaries". That could increase the quality of developing when different arch/os maintainers give their OK. But for 7.0.0rc1 I see only prebuilt binaries for... * macOS * FreeBSD10 AMD64 * Windows (32-bit) * Windows

Please have a look at the dedicated mailing list: http://lists.llvm.org/pipermail/llvm-branch-commits/ 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

On Mon, Aug 27, 2018 at 10:30 AM, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: > On 2018-08-27 09:44, Sedat Dilek wrote: >> >> Yeah, I see. >> You have an unusual development process seen from my POV. > > > GNOME does the same, to pick one example: > https://wiki.gnome.org/ThreePointTwentynine > Tarballs are due on Monday, official release and announcement

Hi, I have seen you tagged 7.0.0rc2 in SVN, but [1] has no tarballs for downloading? Can you please provide them? Thanks in advance. Regards, - Sedat - [1] http://prereleases.llvm.org/7.0.0/#rc2 [2] https://lists.llvm.org/pipermail/llvm-branch-commits/2018-August/date.html

On Mon, Jun 27, 2016 at 9:12 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >>>> 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

The source tarball for clang-tools-extra-3.9.0.src.tar.xz is also missing as well from http://llvm.org/releases/3.8.1/. Jack On Tue, Jul 12, 2016 at 7:34 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > There is no compiler-rt v3.8.1 source tarball available on > <http://llvm.org/releases/3.8.1/>. > > - Sedat - > > On Mon, Jun 27, 2016 at

On Mon, Jun 27, 2016 at 9:39 AM, Hahnfeld, Jonas <Hahnfeld at itc.rwth-aachen.de> wrote: > Please have a look at the dedicated mailing list: > http://lists.llvm.org/pipermail/llvm-branch-commits/ > 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

Thanks for the information Tobias. - Sedat - On Thu, Jan 24, 2019 at 3:31 PM Tobias Hieta <tobias at plexapp.com> wrote: > > Sedat, > > In Hans announcement yesterday he pointed out that he would upload source tarballs as soon as possible: > > "I'll get the source tarballs and docs published as soon as possible, and binaries as they become available" >

Hi, unfortunately, my build somehow hangs when linking clang binary and my system is in an unusable state. My toolchain is clang-3.8, gold-1.11 and LLVMgold.so from binutils v2.26.1 (both selfmade) and LTO-flag is enabled. My buildsystem uses cmake-3.6.0 and ninja-1.7.1 (both prebuilt). I have 52 last steps left in my 3rd build. My Linux-kernel is v3.13.0-92 from official Ubuntu repositories.

On Mon, Jun 27, 2016 at 12:14 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 27 June 2016 at 07:00, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> Building with CMake sets the version-string correct whereas using >> autotools as build-system does not. > > Hi Sedat, > > This was reported earlier and it's unfortunate, but we don't support

Hi, first of all, congrats for the 8.0.0-rc1 pre-release. I have seen that this version was tagged yesterday. Can you provide pre-release source tarballs? Or did you dropped this idea? Thanks. Regards, - Sedat -

> 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

>>> 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: >>

On Mon, Jun 27, 2016 at 10:16 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Mon, Jun 27, 2016 at 12:14 PM, Renato Golin <renato.golin at linaro.org> wrote: >> On 27 June 2016 at 07:00, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>> Building with CMake sets the version-string correct whereas using >>> autotools as build-system

How big is your project? LTO eats RAM even faster than chrome. For example linking clang with LTO could take 16GB of ram. Have you tried using LTO on your project on that machine, or is it your first time? Piotr On Sat, Jul 23, 2016 at 2:42 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, Jul 21, 2016 at 12:01 PM, Sedat Dilek <sedat.dilek at

Hi Tom, Hi Anton, 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]

On 27 June 2016 at 07:00, Sedat Dilek <sedat.dilek at gmail.com> wrote: > Building with CMake sets the version-string correct whereas using > autotools as build-system does not. Hi Sedat, 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

On 3 December 2016 at 17:23, Hahnfeld, Jonas via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think you got that wrong: Tom announced the tagging, not the availability of > the release candidate. I think the confusing thing here is that the email was sent to llvm-dev and cfe-dev inviting people to test it. Maybe we should move to a schedule where the internal testing for the

Hi Tom, I followed a bit the mailing-list but still see no LLVM v3.7.1 tarballs. Can you pleas take care of this? In case of that i386 breakage do a new v3.7.2 release, please. Not sure if this has impact on x86_64 (AMD64)? Thanks. Regards, - Sedat - [1] https://llvm.org/bugs/show_bug.cgi?id=25920