similar to: [7.0.0 Release] rc1 has been tagged

On Sun, Aug 5, 2018 at 5:49 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 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

The raspberry Pi2 is an armv7a chip (Cortex-A7), the first stage builds fine with the native g++ (if not a little slowly at 10+ hours), but it crashes at some point with this command line: Program arguments: /home/ben/development/llvm/3.6.0/rc2/Phase2/Release/llvmCore-3.6.0-rc2.install/bin/clang -cc1 -triple armv7-unknown-linux-gnueabihf -emit-obj -disable-free -disable-llvm-verifier

Dear testers, 4.0.0-rc1 was just tagged from the branch, with r292377. There are still open merge requests and bugs, but I'd like to get the testing started to see what issues come up. Please build, test, and upload binaries to the sftp. Let me know how it goes. I'll upload source, docs, and your binaries to the web site once their ready. Thanks, Hans

Hi, We have an upcoming project to migrate Samba first into a new Hardware then the AD migration. Our hardware is old and we need to migrate. Please allow me to explain the current setup - Server : Physical - OS: Ubuntu 14.04 running Samba 4.0.0. Even though it is running Samba 4, we are using configs from Samba3. - Roles: DC, DNS , DHCP and Shares - Database: TDB - DNS: BIND9 - Clients: Mix of

Dear WizaRds, I am struggling with the use of twophase in package survey. My goal is to compute a simple example in two phase sampling: phase 1: I sample n1=1000 circuit boards and find 80 non functional phase 2: Given the n1=1000 sample I sample n2=100 and find 15 non functional. Let's say, phase 2 shows this result together with phase 1: ...................phase1........

On Tue, 2018-02-20 at 18:11 +1000, Rob Thoman via samba wrote: > Hi Guys, > Have not had any feedback on this. I found the following article but not > sure if it is valid > > Here is what we are planning, high level > Phase1: > > - Add a new Samba 4 server (VM in a new hardware). Join it to the existing > domain > - Promote this server as DC in the Samba 3

Phase1 fails to build on openSUSE 13.2, can anyone see what's wrong from this log file? On Tue, Jan 26, 2016 at 5:45 AM, Hans Wennborg via cfe-dev < cfe-dev at lists.llvm.org> wrote: > On Sun, Jan 24, 2016 at 2:48 PM, Brian Cain <brian.cain at gmail.com> wrote: > > > > On Thu, Jan 21, 2016 at 9:52 PM, Brian Cain <brian.cain at gmail.com> > wrote: >

Hello everyone, It took a bit longer than planned due to master being a somewhat unstable at the branch point, but Release Candidate 1 has now been tagged as llvmorg-10.0.0-rc1. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc1 Pre-built binaries will be added there as they become available. Please file bug reports for any issues you find as blockers of

Hello testers, 4.0.0-rc2 was just tagged from the branch at r294535. There are still open relase blocking bugs and merge requests, so this will not be the last release candidate, but we've had a lot of merges since the last one, and I'd like to see what the testing looks like. The test-release.sh script was updated to also include lld. Make sure you're using the latest version of

On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 4.0.0-rc2 was just tagged from the branch at r294535. > > Building on FreeBSD 10 at least didn't crash this time, and lld built just fine. :) I uploaded the following: >

Hi sir, I have built the test suits in following steps: 0. $cd LLVM_GCC_DIR; $gunzip --stdout llvm-gcc-4.2-*version*-* platform*.tar.gz | tar -xvf - 1. $cd SRC_DIR/llvm-2.8/projects 2. $svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite 3.$cd OBJ_DIR; 4. $SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols

My thought was that its reasonable to expect no warnings when building from bootstrap (as you say) and the last release of Clang. Generally, I think we should work around warnings in the last release of Clang if only for the convenience of folks using that release to build stage1 and using Werror. Certainly, we tend to fix warnings even from earlier Clang versions and from GCC in order to keep

rc1 did not exhibit this mismatch. A repeat of the rc2 build repeated the mismatch. I diff'd the disassembly between phase 2 and phase 3 and the difference is the same on both builds. The difference follows: # diff x86isel_p{2,3}.s 2c2 < Phase2/Release/llvmCore-8.0.0-rc2.obj/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir/X86ISelLowering.cpp.o: file format elf64-x86-64 --- >

On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think having -Werror bots is a good idea, at least when self hosting. > Non-self-hosting -Werror (i.e. with older versions of Clang, or with GCC, > etc.) might also be useful, but I'm less sure (since we can't fix those > warnings if the warning is the problem). On Tue, Mar

Hi all, Our customer wants to install a VPN server on Centos 5 box. This is what the remote site says. pls read below. We now have the new firewall & router installed in our office, that supports a secure VPN connection. We need to enter your Peer IP and your Private IP in our device. They indicated xxxx.xxxx.xxxx/24 as format for the Private IP. The settings you need to know at our end

I just changed this build on green dragon to warn and email if warnings are found in the console log: http://lab.llvm.org:8080/green/job/clang-stage1-cmake-RA_build/ > On Mar 22, 2016, at 6:24 PM, David Jones via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, Mar 22, 2016 at 5:06 PM Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at

Hi, I am new to ipsec and trying to connect my bsd server with win 2000. I have succeeded to tunnel using pre-shared key. But regarding certificate , I failed to get success. The following are configuration : racoon.conf path certificate "/usr/local/openssl/certs" ; # "log" specifies logging level. It is followed by either "notify",

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

Am 09.01.24 um 09:14 schrieb Thomas Hellstr?m: > Hi, Christian > > On Tue, 2024-01-09 at 08:47 +0100, Christian K?nig wrote: >> Hi guys, >> >> I'm trying to make this functionality a bit more useful for years now >> since we multiple reports that behavior of drivers can be suboptimal >> when multiple placements be given. >> >> So basically

Dear testers, Start your engines; 6.0.0-rc1 was just tagged. I know there are still open blockers and it's early in the process in a way, but I'd like to find out where we are. Please run the test script, let me know the results, and upload binaries. Thanks, Hans