similar to: Proposition: 7.0 => 7 in library names

Displaying 20 results from an estimated 4000 matches similar to: "Proposition: 7.0 => 7 in library names"

2018 Mar 22
1
Proposition: 7.0 => 7 in library names
Hello, On 17/03/2018 15:22, Dimitry Andric wrote: > On 17 Mar 2018, at 14:48, Sylvestre Ledru via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Context: I have been packaging the llvm toolchain for Debian & Ubuntu >> and also providing these packages on https://apt.llvm.org/. >> One of the goal is to have different versions co-installable. For that,
2018 Mar 17
0
Proposition: 7.0 => 7 in library names
On 17 Mar 2018, at 14:48, Sylvestre Ledru via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Context: I have been packaging the llvm toolchain for Debian & Ubuntu > and also providing these packages on https://apt.llvm.org/. > One of the goal is to have different versions co-installable. For that, > I am renaming the binaries and libraries. > > Now, as we are not
2016 Mar 29
6
Status of the official LLVM APT repositories
Hi Sylvestre, On Sat, 12 Mar 2016, Sylvestre Ledru wrote: > I am working on it as we speak. Hopefully, most of the 3.8 & 3.9 > packages are going to be green by next week. Any updates on that? It appears that Precise repositories are now in order, but all the others (and, most importantly, Trusty) are still not updated. Also, 3.9 packages are not mentioned on the web page,
2014 May 12
4
[LLVMdev] Name of the libraries + soname? 3.4.1 ?
On 12/05/2014 16:13, Tom Stellard wrote: > On Mon, May 12, 2014 at 04:05:20PM +0200, Sylvestre Ledru wrote: >> On 12/05/2014 15:22, Tom Stellard wrote: >>> On Mon, May 12, 2014 at 08:41:36AM +0200, Sylvestre Ledru wrote: >>>> Hello, >>>> >>>> With the release of 3.4.1, the LLVM library has been renamed from >>>> libLLVM-3.4.so to
2015 Feb 24
5
[LLVMdev] RFC: Dropping support for building sanitizers with autotools
On 18/02/2015 23:29, Alexey Samsonov wrote: > > On Tue, Feb 17, 2015 at 6:23 PM, Anna Zaks <ganna at apple.com <mailto:ganna at apple.com>> wrote: > > >> On Feb 17, 2015, at 4:00 PM, Alexey Samsonov <vonosmas at gmail.com <mailto:vonosmas at gmail.com>> wrote: >> >> >> On Tue, Feb 17, 2015 at 3:37 PM, Anna Zaks <ganna at
2014 May 12
2
[LLVMdev] Name of the libraries + soname? 3.4.1 ?
On 12/05/2014 17:12, Tom Stellard wrote: > On Mon, May 12, 2014 at 04:17:05PM +0200, Sylvestre Ledru wrote: >> On 12/05/2014 16:13, Tom Stellard wrote: >>> On Mon, May 12, 2014 at 04:05:20PM +0200, Sylvestre Ledru wrote: >>>> On 12/05/2014 15:22, Tom Stellard wrote: >>>>> On Mon, May 12, 2014 at 08:41:36AM +0200, Sylvestre Ledru wrote:
2016 May 17
2
Coverage Update on http://llvm.org/reports/coverage/
> On May 16, 2016, at 11:58 AM, Sylvestre Ledru <sylvestre at debian.org> wrote: > > Le 16/05/2016 à 19:19, Mehdi Amini a écrit : >> Hi, >> >> Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) > I am in charge of this. I had some recent issues with cmake but I think > I fixed them today. >
2014 Aug 21
2
[LLVMdev] LLVM 3.6 release notes
On 21 August 2014 17:08, Sylvestre Ledru <sylvestre at debian.org> wrote: > Yes, commit directly in the 3.5 branch. > > About 3.6, we usually reset the release notes after the release (3.5 in > this case). The note I have is for 3.6, not 3.5. Should I just hold it until 3.5 is released? Cheers, Rafael
2016 May 16
5
Coverage Update on http://llvm.org/reports/coverage/
Hi, Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) Thanks, Mehdi
2016 May 19
2
Coverage Update on http://llvm.org/reports/coverage/
> On May 19, 2016, at 8:59 AM, Sylvestre Ledru <sylvestre at debian.org> wrote: > > Le 16/05/2016 à 19:19, Mehdi Amini a écrit : >> Hi, >> >> Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) > This is now fixed: http://llvm.org/reports/coverage/ > I skimmed the results, and it seems that there
2014 May 12
2
[LLVMdev] Name of the libraries + soname? 3.4.1 ?
On 12/05/2014 15:22, Tom Stellard wrote: > On Mon, May 12, 2014 at 08:41:36AM +0200, Sylvestre Ledru wrote: >> Hello, >> >> With the release of 3.4.1, the LLVM library has been renamed from >> libLLVM-3.4.so to libLLVM-3.4.1.so. In parallel, the soname has been >> updated to >> reflect this change. >> >> AFAIK, we kept the ABI compatible from 3.4
2019 Sep 14
2
[GSoC 2019] Apply the Clang Static Analyzer to LLVM-based projects - final report
Hello, Le 29/08/2019 à 01:02, Artem Dergachev a écrit : > Yay thx! > > Sylvestre, is there anything i can help you with in order to get the reports page back up? Sorry, it took me a while to get that back but here is the report of r371718: https://llvm.org/reports/scan-build/ > I'd also indeed love to spam people with warnings that they introduced, even if in the form of a
2016 May 09
2
Status of the official LLVM APT repositories
On Mon, May 9, 2016 at 4:46 PM Sylvestre Ledru <sylvestre at debian.org> wrote: > Le 09/05/2016 à 07:34, Paweł Bylica a écrit : > > llvm-3.8-dev is broken: > > > > CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 (include): > > include could not find load file: > > > > /usr/share/llvm/cmake/LLVMExports.cmake > Brad King helped me
2016 Mar 12
4
Status of the official LLVM APT repositories
On Wed, Mar 9, 2016 at 10:30 PM, Sylvestre Ledru via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Le 09/03/2016 à 21:44, Yury V. Zaytsev a écrit : > > On Wed, 9 Mar 2016, Sylvestre Ledru wrote: > > > >> This is still maintained. However the cmake transition (for both 3.8 > >> and 3.9) wasn't simple... While it should be fine for debian, it >
2016 Mar 09
2
Status of the official LLVM APT repositories
On Wed, 9 Mar 2016, Sylvestre Ledru wrote: > This is still maintained. However the cmake transition (for both 3.8 and > 3.9) wasn't simple... While it should be fine for debian, it might need > more work for old Ubuntu (back port of cmake) Hi Sylvestre, Thank you for the clarification! Any ETAs on when the APT repositories are going to be updated with LLVM 3.8 & 3.9 builds?
2016 Apr 13
2
Status of the official LLVM APT repositories
On Wed, 13 Apr 2016 at 08:10 Amaury SECHET via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I'd like to shime in here. These apt repository used to contain packages > named llvm-3.8-tools containing, amongst other things, the lit python > library used to test llvm. It seems that it went away recently and I have > travis build failing because of this. > > What is
2016 Mar 12
0
Status of the official LLVM APT repositories
Le 12/03/2016 à 14:15, Johan Engelen a écrit : > > > > I'm not sure how clean / dirty of a solution you'd be okay with, but > > I'd just point out that CMake developers provide working binary > > tarballs for Linux with every release at > https://cmake.org/download/ . > > So, if you are not a purist and/or need the CMake backport for
2016 Jun 23
3
apt repositories back!
Hello, Thanks to the LLVM Foundation and Tanya, the apt repository is now back: http://apt.llvm.org/ It will take a few days before all the builds go green [1]. Please update your configurations. Sylvestre [1] The same build infra is still used but the builds were failing because using llvm.org/apt too.
2017 Jun 14
3
LLVM coverage report
Hi Sylvestre, it seems the code coverage runs are not updated since a couple of months. http://llvm.org/reports/coverage/tools/polly/lib/Support/SCEVValidator.cpp.gcov.html The last run was on 2017-05-20 02:07:48. Are you still maintaining these? Is this on purpose? Any chance this could be fixed? Best, Tobias
2016 Jun 24
2
[llvm-foundation] apt repositories back!
Le 23/06/2016 à 19:13, Renato Golin a écrit : > On 23 June 2016 at 17:56, Sylvestre Ledru via llvm-foundation > <llvm-foundation at lists.llvm.org> wrote: >> Thanks to the LLVM Foundation and Tanya, the apt repository is now back: >> >> http://apt.llvm.org/ > Nice! Thanks everyone! > > Are we filtering multiple hits, or are we just assuming people will be