similar to: [7.0.0 Release] rc3 has been tagged

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) x64 Native Tools Command Prompt for VS 2017 directory structure: test     llvm <-- git clone https://github.com/llvm-mirror/llvm, git checkout release_70       tools         clang <-- git clone https://github.com/llvm-mirror/clang, git checkout

Dear testers, The final version of 7.0.0 has been tagged from the branch at r342370. It is identical to rc3 modulo release notes and docs changes. Please build the final binaries and upload to the sftp. For those following along: this means 7.0.0 is done, but it will take a few days to get all the tarballs ready and published on the web page. I will send the announcement once everything is

> Have you tried compiling it yourself? I just installed git for the first time and downloaded all of the latest source code packages directly from the site. I'm getting the following every time I try to (re)build any of the projects: 1>------ Build started: Project: opus, Configuration: Release Win32 ------ 1> fatal: Not a git repository: 'C:\My

I just recently found that opus_multistream_encode_float is returning -1 (OPUS_BAD_ARG) with the libopus 1.1 build but works just fine with the libopus 1.0.1 and libopus 1.1-beta builds. I tried using opus_multistream_encoder_create and opus_multistream_surround_encoder_create. Tried with coupled and uncoupled quadraphonic and uncoupled stereo encodes. I'm dynamically loading the libopus

Dear testers, 7.0.0-rc2 was just tagged (from branch revision r340437). There have been a bunch of merges since rc1, and hopefully many of the issues with the previous candidate are fixed in this one. Please run the test script, share the results, and upload binaries. I will publish source tarballs, docs, and binaries on the web page once they're ready. Thanks, Hans

Hans, Am 06.03.2017 um 23:25 schrieb Hans Wennborg: > The mailing list thread you linked to talkes about > "multi-configuration generators", such as MSBuild. Have you tried > building with ninja (https://ninja-build.org/) instead? I now tried the ninja build, and that was successful, so I have a workaround. I still would like to know whether I made a mistake with the

Hello everyone, It took a bit longer than planned, but Release Candidate 3 is now here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at 3a843031a5 and contains 95 commits since the previous release candidate. If no new problems arise, this is what the final release will look like. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc3 and

Hello everyone, After some delay, the llvmorg-11.0.0-rc3 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc3 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc3 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725 Release testers:

Hello again, We had to pick up another bug fix, so here is another release candidate: llvmorg-11.0.0-rc5 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc5 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc5 Pre-built binaries will be added as they become ready. Please file reports for any bugs you find as blockers of

Hello everyone, A little less than a week after rc3, the llvmorg-11.0.0-rc4 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc4 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc4 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725

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

On Wed, Mar 8, 2017 at 10:34 AM, Stephan Mühlstrasser <stephan.muehlstrasser at web.de> wrote: > Hans, > > Am 06.03.2017 um 23:25 schrieb Hans Wennborg: >> >> The mailing list thread you linked to talkes about >> "multi-configuration generators", such as MSBuild. Have you tried >> building with ninja (https://ninja-build.org/) instead? > >

Hi, I've just tagged 7.0.1-rc3. This will hopefully be the last release candidate. Please test and report results. Thanks, Tom

Dear testers, 7.0.0-rc1 was just tagged (from the branch at r338847). It's early in the release process, but I'd like to find out what the status is of the branch on our various platforms. Please run the test script, share the results, and upload binaries. Thanks, Hans

Hi, I'm trying to do a build and install on Windows 10 with Visual Studio 2015 Community Edition for the X86 and ARM targets, from the current release_40 branch. While compilation completes without error, the INSTALL target fails with the following error: 54> CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file): 54> file INSTALL cannot find 54>

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm still hoping for more release notes, though). I'm hoping we can get to

Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues remain. I know we're a little bit behind schedule, but hopefully we can get to 'final'

On Fri, Aug 3, 2018 at 3:38 PM, <paul.robinson at sony.com> wrote: > Hi Hans, > > I was just trying to push a release note about DWARF v5 support. I did: > git checkout release_70 # in the monorepo > git commit <update to llvm/docs/ReleaseNotes.rst> > git llvm push > but that fails. How do you want to do release notes? I'm not familiar with "git

Dear testers, My list of blockers is empty, and there were no new problems discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1]. Please build the final binaries and upload to the sftp. For others following along: yes, this means 3.8.0 is complete, but it takes a couple of days to get the source and binary tarballs built. I will send the release announcement when everything's

Dear testers, 8.0.0-rc3 was just tagged from the release_80 branch at r355015. We're running a little behind schedule now, but I think we're also close to be able to call this done. Please take a close look at this release candidate. Unless anything bad comes up, this is probably very similar to what the final release will look like. Testers, please run the test script, share your