similar to: Any documentation on how the official packages are being built?

Hi Oliver, If you look at http://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library that lists the tools and minimum version required. There is some documentation for how to build a release: http://llvm.org/docs/ReleaseProcess.html For the official windows builds, Hans Wennborg provides the batch file used to create any given upload when he reports on the

Hello! AppLocker is a newer technique which allows users to control access to certain programs and it was introduced in Windows 2008 Server and Windows 7 (clients). I wonder does SAMBA 4 support it? Thank you! -- View this message in context: http://samba.2283325.n4.nabble.com/Does-SAMBA4-Support-AppLocker-in-Group-Policies-tp4206013p4206013.html Sent from the Samba - General mailing list

I see that some of the announcements of binaries for Windows include the script using for compiling. Is there anything similar (or some other form of documentation) for the binaries distributed on http://releases.llvm.org/download.html for other platforms? (I'm particularly interested in Ubuntu) Thanks, Maurizio -------------- next part -------------- An HTML attachment was scrubbed...

Hi, I have just tagged the first release candidate for the 3.4.1 release, so testers may begin testing. Please refer to http://llvm.org/docs/ReleaseProcess.html for information on how to validate a release. If you have any questions or need something clarified, just email the list. For the 3.4.1 release we want to compare test results against 3.4-final. I have added support to the

Hi, Looks ok for native MIPS, I have two failures on debian8: Failing Tests (2): XRay-x86_64-linux :: TestCases/Linux/argv0-log-file-name.cc XRay-x86_64-linux :: TestCases/Linux/fixedsize-logging.cc I'll investigate these failures. Otherwise looks ok. I've uploaded the binaries. 9d5a389c20eb5b3071e6a0504b7cf87d clang+llvm-4.0.0-rc1-mipsel-linux-gnu.tar.xz

Hi, I have tagged the 3.6.1-rc1 so testing can begin. We can always use more testers, so if you are interested in helping, let me know. Instructions for validating an LLVM release can be found here: http://llvm.org/docs/ReleaseProcess.html Reminder: We are using 3.6.0 as our baseline for regression testing. Thanks, Tom

Hi, 3.5.1-rc1 has been tagged, so it is time to begin testing. We can always use more testers, so if you would like to volunteer, let me know. For those that are new to testing, please review the documentation for how validate a new release: http://llvm.org/docs/ReleaseProcess.html Remember that when we check for regressions we want to compare the test results of 3.5.1-rc1 with 3.5.0-final.

Dear testers, The final version of 3.9.0 was just tagged (from the 3.9 branch at r280312). There were no changes after rc3. This took a little longer than expected, but on the up side that means it's had more time to be tested. Please build the final binaries and upload to the sftp. For others following along: this means 3.9.0 is complete, but it will take a few days to get the tarballs

Vedant, Thanks for building the packages before. Could you detail what's required to build these binaries on macOS so that someone else could replicate it? Thanks, Tobias On Mon, Oct 14, 2019 at 8:29 PM Vedant Kumar via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Gio, > > I prepared the macOS packages for the past few releases, but have less time to keep up with

Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom

Thanks! Can you post the sha1's for the files you uploaded? Windows and Mac look good. Uploaded: ca26fbfabb54ac1f70776ab3a5503313ec518f18 clang+llvm-3.9.0-rc2-x86_64-apple-darwin.tar.xz 26d616e1355dc0802f90babbd5ea0b72abc0c0bb LLVM-3.9.0-rc2-win32.exe 42363aeaff395d442f418d77b542a088b5b0658b LLVM-3.9.0-rc2-win64.exe Thanks, Hans On Fri, Aug 19, 2016 at 9:22 AM, Diana Picus <diana.picus

Hi, I've created the 3.9.1-final tag no changes from -rc3. Testers can begin uploading binaries now. -Tom

Hi, I have tagged 3.9.1-rc3. The only differences from -rc2 were a few bug fixes for ARM/AARCH64, so if you aren't testing either of these I think it's safe to take this -rc off and what for -final. I'm hoping to do -final next week after I get the ARM test results. Thanks, Tom

We're very very close to the final release. Source and binaries for LLVM-3.9.0-rc3 are available at http://llvm.org/pre-releases/3.9.0/#rc3 This release candidate is almost the same as rc2, with the following additional commits: r279224 - Minor change to OpenCL release notes r279260 - [lld] Add a note that 3.9 is a major milestone for us r279468, r279474 - Fix gather-root.ll SLP vectorizer

Hi, No major issues seen so far for mips. Binaries uploaded. SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)= 6e4fab79cc341a9084dab94cced108daff39fcde14a11e8d7ae454e9f92cb77c SHA256(clang+llvm-6.0.0-rc3-mips-linux-gnu.tar.xz)= 54887a039d3d7ccff17a0c7245f4c9d778a1c22f96b619db554849da55293d61 SHA256(clang+llvm-6.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz)=

Hello everyone, Source, binaries and docs for LLVM-5.0.0-rc2 are now available at http://prereleases.llvm.org/5.0.0/#rc2 (I'll add more binaries as they become available.) Please try it out, run tests, builds your favourite projects and file bugs about anything that needs to be fixed (including docs!), marking them blockers of http://llvm.org/pr33849. Cheers, Hans

Hi, I've tagged the final version of 3.7.1. There is no difference from 3.7.1-rc2, so testers just need to build the packages no testing is required. -Tom

Hi Hans, I'm seeing one unexpected failure: libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp Test logs show: Standard Error: -- terminating with uncaught exception of type std::length_error: basic_string -- but only on my big endian MIPS machine. I have filed PR36373 for the above failure. I've looked at the failures

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