similar to: [APT] lldb symbols

Hello everyone I was just porting a project to build against the LLVM 9 apt packages and noticed that the issue I filed and explained during the release phase in https://llvm.org/PR43035 still persists: CMake Error at /usr/lib/llvm-9/lib/cmake/llvm/LLVMExports.cmake:1323 (message):   The imported target "yaml-bench" references the file      "/usr/lib/llvm-9/bin/yaml-bench"

On 02/05/2014 11:26, Adam Strzelecki wrote: >> It should be fixed. Can you confirm? > > Nope. Sorry. Still doesn't work here: > > Get:3 http://llvm.org/apt/trusty/ llvm-toolchain-trusty/main libllvm3.5 amd64 1:3.5~svn207822-1~exp1 [7,300 kB] > Get:4 http://llvm.org/apt/trusty/ llvm-toolchain-trusty/main llvm-3.5-runtime amd64 1:3.5~svn207822-1~exp1 [52.0 kB] > Get:5

On 02/12/2019 15:21, Sylvestre Ledru wrote: > yaml-bench is shipping in libclang-common-9-dev Ok possible. Though, it adds an unnecessary 46MB to my docker image. > It should be indeed in llvm-9-dev instead. This would hide the problem, right. I am not sure it's is a good solution. Where can we review the build process for the apt packages? On 02/12/2019 15:21, Sylvestre Ledru wrote:

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

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on

Ok, thank you, I will implement it then. As far as I see this optimization should be done in AArch64LoadStoreOptimizer, is it right? From: Eli Friedman [mailto:efriedma at quicinc.com] Sent: Thursday, November 21, 2019 11:55 PM To: Kosov Pavel <kosov.pavel at huawei.com>; LLVM Dev <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] [ARM] Peephole optimization ( instructions tst +

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,

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

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

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 >

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?

Le 09/05/2016 à 16:59, Paweł Bylica a écrit : > On Mon, May 9, 2016 at 4:46 PM Sylvestre Ledru <sylvestre at debian.org > <mailto: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): >

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 llvm-3.7-dev is ok. Why is it so error prone for so many years? On Sun, May 8, 2016 at 11:31 PM Amaury SECHET via llvm-dev < llvm-dev at lists.llvm.org> wrote: > So, it turns out that the secret sauce to

Hello, Just a quick refresh, on llvm.org/apt/ [1], I am rebuilding the sources of LLVM to create snapshot packages for the stable branches and development branches (currently, 3.4, in the hope of point releases and 3.5). This currently targets 2 releases of Debian and 4 of Ubuntu [2] and the llvm toolchain is built using the compiler shipped with the distribution. Following the recent

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

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.

On Sun, Oct 6, 2013 at 10:40 PM, Sylvestre Ledru <sylvestre at debian.org> wrote: > I did some cleanup of the repositories today (Sunday). > I remove all the 3.3 snapshots which were wrong (they were older than the > official 3.3 release and not maintained). > I didn't think that anybody was using them (Looks like I was wrong, sorry!). No problem, we were just using them

After some thinking on this idea, it would not work because I need / want to use Debian/Ubuntu package to do the build and clang 3.4 is not built on these architecture :( So, if I bootstrap clang 3.4, I will have a dependency on libstdc++ 4.8... :/ On 25/12/2013 22:23, Arnaud Allard de Grandmaison wrote: > Hi Sylvestre, > > The easiest is probably to have a dependency to (and use)

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

Le 29/03/2016 à 14:17, Yury V. Zaytsev a écrit : > Hi Sylvestre, > ri > 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? Yes, most of the remaining issues are fixed (the sync to llvm.org/apt was disabled). I will send a summary soon.