similar to: LLVM/Clang 8.0.0-rc1 source tarballs?

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 Tom, thanks and congrats for LLVM 10.0.1-rc1 release. [1] shows 2 assets. 10.0.0 RCs had a lot of more assets. I am missing the llvm-project-10.0.1rc1.tar.xz tarball. Will you provide them later or is there a new development/workflow decision I do not know of? BTW, the source zip and tar.gz tarballs show no sizes. I am using Mobile LTE/UMTS to download stuff from the Internet. For now I

On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/19/2020 09:05 PM, Sedat Dilek wrote: > > Hi Tom, > > > > thanks and congrats for LLVM 10.0.1-rc1 release. > > > > [1] shows 2 assets. > > 10.0.0 RCs had a lot of more assets. > > I am missing the llvm-project-10.0.1rc1.tar.xz tarball. > > > > Will

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

On Wed, May 20, 2020 at 11:12 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/20/2020 09:53 AM, Sedat Dilek wrote: > > On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > >> > >> On 05/19/2020 09:05 PM, Sedat Dilek wrote: > >>> Hi Tom, > >>> > >>> thanks and congrats for LLVM

> 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

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

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

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

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

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

Hi Tom, [1] does not list any 3.9.1rc2 pre-release tarballs, can you please upload? Thanks in advance. Regards, - Sedat - [1] http://www.llvm.org/pre-releases/

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

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

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

I’m happy to run them, although I’d appreciate a pointer to the appropriate documentation. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Tobias Hieta <tobias at plexapp.com> Date: Wednesday, September 30, 2020 at 11:15 AM To: Hans Wennborg <hans at chromium.org> Cc: llvm-dev <llvm-dev at

On Tue, Feb 17, 2015 at 1:55 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at gmx.de> wrote: >> Patch 1 adds a check for the compilers visibility macro to configure.ac. >> Patch 2 avoids redefined symbol errors in clang of the tls entry points. >> Based on a suggestion from Rafael Ávila de Espíndola