similar to: will 3.8.1 ever really have release tarballs?

If you are on glibc-2.24, did you patch it with the fix 24e2b1cede1952d7d4411a3cafd25dd8593dab9f that revert commits 80f87443eed17838fe453f1f5406ccf5d3698c25 and a824d609581d5ee7544aabcbbc70e8da44b2b5b6? I had to do that since it broke go, gcc, and clang address sanitizers without the patch. On 9/12/16, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 11 September

Has it been decided to skip 3.7.1 and just wait until 3.8.0? I keep checking but never see any update on the web site to allow downloading 3.7.1 tar files.

Hello testers, 5.0.0-rc4 was just tagged. There were very few changes after rc3, and if nothing unexpected comes up, this is what the final release will look like. Please test and let me know if there are any issues. Cheers, Hans

Maybe it's just the holidays... AFAIK, all the packages were tested and uploaded. On 29 December 2015 at 22:44, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Got to admit, I'm curious too. I have finished migrating to the v3.7.1-final tags, and I'm waiting for the green light :-) > > MartinO > > -----Original Message----- >

Hello everyone, There's plenty of time before the release process starts, but I'd like to begin the schedule discussion. For the September release we usually branch mid-July. However, this year my vacation runs a little later, so a good branch date for me would be the 1st of August. Proposal: - 1 August 2018: Branch; RC1 soon after - 22 August 2018: RC2; all lose ends should be tied up

On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> 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 tested successfully. :) They'll be announced in the

On Sun, Jun 26, 2016 at 2:48 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev > <llvm-dev at lists.llvm.org> 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

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

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

Sedat, 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. On Sun, Jun 26, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > Hi Tom, Hi Anton, > > the first I had in mind was... > "Another (LLVM/CLang) realease - a new drama!"

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

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

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 Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ 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

Hi Samba world, Have been struggling with this for the past 10 days, we are running Samba 3.0.22 on VCS zone, we have end users saving files onto Samba mapped drive, and complained that it 5mins to save 300 files, now it takes 30 mins. There is recently a change in the topology. Before Enduser ----------- samba mapped -------------- server (local attached storage)

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

Hi, I've tagged 3.8.1-final, so testers can start building the final binaries. -Tom

Hello everyone, The release branch for LLVM 9 and its sub-projects was just created from trunk at r366426, and the trunk version was subsequently bumped to 10.0.0. Release blockers are tracked by https://llvm.org/PR42474 Please mark any bugs, old or new, that need to be fixed before the release as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and

Problem: Flash on X100P does not flash. Phone line has Call Transfer. With this line plugged into a regular phone, it can receive a phone call. Then, depress the hook momentarily, release. Dialtone is now available. Dial a different number. Call is answered. Hook Flash again, now in a three way call. Hang up. The other two parties are still in communication. Now, plug same line into the X100P.