Hello,
Le 30/08/2019 à 18:38, Hans Wennborg via Release-testers a écrit :
Hello everyone,
9.0.0-rc3 was tagged today from the release_90 branch at r370450. In
the Git monorepo, it's tagged as llvmorg-9.0.0-rc3.
I experienced an issue with lto. Initially not clang related but might be.
For a f
Le 14/08/2019 à 10:14, Hans Wennborg via Release-testers a écrit :
Hello everyone,
9.0.0-rc2 was tagged yesterday from the release_90 branch at r368683.
In the Git monorepo it's available as the llvmorg-9.0.0-rc2 tag.
[...]
Release testers: please start your engines, run the script, share yo
Le 14/03/2019 à 18:48, Michał Górny via Release-testers a écrit :
On Tue, 2019-03-12 at 12:16 +0100, Hans Wennborg via Release-testers
wrote:
Dear testers,
8.0.0-rc5 was just tagged from the release_80 branch at r355909.
This is identical to rc4 with the addition of r355743. Hopefully it is th
Le 24/01/2019 à 01:49, Hans Wennborg via Release-testers a écrit :
Dear testers,
8.0.0-rc1 was just tagged (from the branch at r351980).
Looks good on Debian & Ubuntu (Disco) on all supported archs (still
waiting for mipsel & mipsel64 but I am confident):
https://buildd.debian.org/status/p
Le 20/12/2018 à 01:23, Tom Stellard via Release-testers a écrit :
Hi,
I've tagged the 7.0.1 final release. Testers may begin uploading binaries.
Uploaded in Debian with a stage2 build (piouf, wasn't trivial). All
green on the official arch:
https://buildd.debian.org/status/package.php?p=l
Le 17/09/2018 à 13:41, Hans Wennborg via Release-testers a écrit :
> 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
Le 10/09/2018 à 16:12, Hans Wennborg via Release-testers a écrit :
> Dear testers,
>
> 7.0.0-rc3 was just tagged (from branch revision r341805).
>
> No further release candidates are currently planned, so this is a
> release candidate in the real sense: unless any serious issues
> surface, this i
Hello,
Le 23/08/2018 à 01:59, Hans Wennborg via Release-testers a écrit :
> 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.
>
> Plea
Hello,
On 02/03/2018 13:17, Hans Wennborg via Release-testers wrote:
> Dear testers,
>
> The final version of 6.0.0 has just been tagged from the branch after
> r326550. It has the same contents as -rc3 modulo release notes and one
> small x86 fix (r326393).
>
> Please build the final binaries a
Hello,
On 07/02/2018 21:51, Hans Wennborg via Release-testers wrote:
> Dear testers,
>
> There's been a lot of merges since rc1, and hopefully the tests are in
> a better state now.
>
> 6.0.0-rc2 was just tagged, after r324506.
>
> Please test, let me know how it goes, and upload binaries.
Loo
Hello
I am not sure to understand how this relates to the 5.0.0 work?
For now, it is broken because of a gcc bug:
https://bugs.llvm.org/show_bug.cgi?id=34150
I am planning to upgrade the gcc version to 4.9 to workaround this
issue. Probably this week.
Sylvestre
Le 28/08/2017 à 09:40, Andrew
All green in Debian:
https://buildd.debian.org/status/package.php?p=llvm-toolchain-5.0
Except that I had to force the usage of gcc 6 instead gcc 7 because of
https://bugs.llvm.org/show_bug.cgi?id=34140
(other versions are also affected)
S
Le 11/08/2017 à 04:00, Hans Wennborg via Release-test
Hello,
I am experiencing a build issue with clang tools extra that I reported here:
https://bugs.llvm.org/show_bug.cgi?id=33970
Does it ring a bell?
Thanks
S
Le 27/07/2017 à 00:41, Hans Wennborg via Release-testers a écrit :
> Dear testers,
>
> 5.0.0-rc1 has just been tagged.
>
> Please bui
Le 09/03/2017 à 01:52, Hans Wennborg via Release-testers a écrit :
> Dear testers,
>
> The final version of 4.0.0 was just tagged (from the 4.0 branch at
> r297335). There were no changes after rc4.
>
> Please build the final binaries and upload to the sftp.
>
> For others following along: this mea
Le 02/03/2017 à 20:47, Hans Wennborg via Release-testers a écrit :
> Hello testers,
>
> 4.0.0-rc3 was just tagged from the branch at r296762.
>
> This is a release candidate in the real sense: if no major issues show
> up with this one, it is the version that will be released.
>
> Please let me kno
Le 24/01/2017 à 00:01, Hans Wennborg via Release-testers a écrit :
> Source, binaries and docs for LLVM-4.0.0-rc1 are now available at
> http://www.llvm.org/pre-releases/4.0.0/#rc1
>
> Please try it out, run tests, build your favourite projects and file
> bugs about anything that doesn't work and n
Le 18/01/2017 à 16:45, Hans Wennborg via Release-testers a écrit :
> 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
Hello
Recently (couple of weeks), the generation of the apt.llvm.org packages
is failing because some lldb binaries are sometime no longer generated
For example, on debian unstable, the following files are no longer
generated:
usr/lib/llvm-4.0/bin/lldb-server
usr/lib/llvm-4.0/bin/lldb-argdumper
Hello,
For the debian packaging, I am using -DLLVM_LINK_LLVM_DYLIB=ON
I have been experiencing the same issue as David here:
http://lists.llvm.org/pipermail/lldb-dev/2016-March/009925.html
lldb 3.8.1 hangs when running an application.
I haven't been able to find the fix so that I could backpor
Le 19/08/2016 à 03:51, Hans Wennborg via Release-testers a écrit :
Dear testers,
3.9.0-rc2 was just tagged from the 3.9 branch at r279183.
This is a release candidate in the very real sense that if nothing new
comes up, this is be what the final release looks like. There are
currently no open r
Hello,
Lately, I haven't been able to link lldb because it uses too much memory:
/usr/bin/ld: final link failed: Memory exhausted
As reported here:
https://llvm.org/bugs/show_bug.cgi?id=27237
(yes, I use shared libraries)
Any workaround?
Thanks,
Sylvestre
PS: please cc me !
_
Le 20/01/2016 00:47, Hans Wennborg a écrit :
> Dear testers,
>
> Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at
> r258223. (It took a little longer than I'd planned, sorry about that.)
>
> There are still a bunch of open merge requests and bug reports, but I
> wanted to get th
What about creating a release management mailing list ?
The testers are usually the same (hello folks!) :)
Sylvestre
Le 20/01/2016 00:55, Hans Wennborg a écrit :
> (cc'ing non-legacy llvm-dev this time; apologies if you get this
> twice. Please don't reply-all to the first one.)
>
> On Tue, Jan 1
I am experiencing a similar issue with the 3.7 branch on all Ubuntu version:
https://llvm.org/bugs/show_bug.cgi?id=24912
Debian works fine.
Does it ring a bell?
Sylvestre
Le 22/09/2015 18:01, Todd Fiala via lldb-dev a écrit :
> Hey all,
>
> On the Linux build bot, I'm seeing at least one test hun
Le 28/08/2015 03:46, Hans Wennborg a écrit :
> On Wed, Aug 26, 2015 at 4:43 PM, Hans Wennborg wrote:
>> 3.7.0-rc4 has just been tagged. It is identical to rc3, plus:
>>
>> - r245902: Revert r245355: change of clang-tools-extra symlink in the
>> release script
>> - r245947: Merge of r245927: Fix LL
Le 21/08/2015 02:51, Hans Wennborg a écrit :
> Hello everyone,
>
> 3.7-rc3 has just been tagged. Testers, please test, build binaries,
> upload to the sftp and report results to this thread.
>
Uploaded in Debian.
Works fine on the major archs
However, lldb fails to build on some archs. I reported b
26 matches
Mail list logo
