similar to: Building libvirt library without libvirtd or virsh

On Thu, Oct 08, 2020 at 09:38:22AM +0200, Martin Kletzander wrote: > On Wed, Oct 07, 2020 at 04:50:26PM -0700, Román González wrote: > > Hello there, > > > > I'm trying to play with musl and libvirt to see if I'm able to build a > > libvirt client binary without dynamic lib dependencies. I have two > > questions: > > > > 1) to your knowledge,

> > If you want to do a minimal build of libvirt you can run meson with > --auto-features=disabled which will disable most of the features and you > can explicitly enable only the things that you want to use (this is what > most distributions are doing when building packages). I just noticed > that there are some build options where this doesn't work so I'll post >

On Wed, Oct 07, 2020 at 04:50:26PM -0700, Román González wrote: >Hello there, > >I'm trying to play with musl and libvirt to see if I'm able to build a >libvirt client binary without dynamic lib dependencies. I have two >questions: > >1) to your knowledge, is this exercise futile? > >2) Do you know if there is a way to *only* compile the library bits? > >I

Un saludo a todos. Estoy haciendo un ACC y utilizo el paquete Ade4. Cuando quiero realizar un plot del resultado utilizo plot(). el resultado son 6 gráficos: loadings, correlation, inertia axes, scores and predictions, eigenvalues y species. Lo que quería saber es cómo representar en una sola ventana (los 6 gráficos a parecen en la misma) el gráfico correspondiente a Species. Gracias por vuestra

Hello all, Is there a reason why the library location code in cindex py does not use find_library() to locate libclang, like in the attached patch? Without it there were problems locating a versioned libclang.so.1 file on Debian, for example. Cheers, Mihai -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 06/25/2012 12:50 AM, Mihai Basa wrote: > Hello all, > > Is there a reason why the library location code in cindex py does not > use find_library() to locate libclang, like in the attached patch? > > Without it there were problems locating a versioned libclang.so.1 file > on Debian, for example. Hi Mihai, as this is a clang related question, I move your mail to the clang

Hi, Just a heads up on my experiences with the new build system. Arch Linux meson-0.55.1 Overall, it looks good, so well done! Just a couple of minor things I noted: 1. Arch uses a meson wrapper script (arch-meson) that sets:   --buildtype plain This seems to trigger a bug in meson that results in copious bogus compiler warnings: cc1: warning: ‘-Wformat-y2k’ ignored without ‘-Wformat’

On a Tuesday in 2020, Pavel Hrdina wrote: >On Tue, Sep 01, 2020 at 03:13:39PM +0200, Ján Tomko wrote: >> On a Tuesday in 2020, Pavel Hrdina wrote: >> > On Sun, Aug 30, 2020 at 02:34:56AM +0200, Toolybird wrote: >> > > Hi, >> > > >> > > Just a heads up on my experiences with the new build system. >> > > >> > > Arch Linux

On a Tuesday in 2020, Pavel Hrdina wrote: >On Sun, Aug 30, 2020 at 02:34:56AM +0200, Toolybird wrote: >> Hi, >> >> Just a heads up on my experiences with the new build system. >> >> Arch Linux >> meson-0.55.1 >> >> Overall, it looks good, so well done! >> >> Just a couple of minor things I noted: >> >> 1. Arch uses a meson

On Fri, Sep 25, 2020 at 04:44:24PM +0800, Wei Wang wrote: > On Fri, Sep 25, 2020 at 4:40 PM Andrea Bolognani <abologna@redhat.com> > wrote: > > > On Fri, 2020-09-25 at 16:21 +0800, Wei Wang wrote: > > > On Fri, Sep 25, 2020 at 3:56 PM Andrea Bolognani <abologna@redhat.com> > > wrote: > > > > On Fri, 2020-09-25 at 10:33 +0800, Wei Wang wrote:

I have managed to compile llvm and clang against musl, but it behaves really strange: At first I tried to launch the compiler with musl dynamic loader: $ LD_LIBRARY_PATH=/path/to/musl/lib /path/to/musl/lib/ld-musl-x86_64.so.1 /path/to/llvm/bin/clang -v clang version 4.0.0 (https://github.com/llvm-mirror/clang 40adebeca0f99006d407508653c2cbd270a1a51c) (https://github.com/llvm-mirror/llvm

Seems it didn't appear on the mailing list, resent it. Hi folks, I'm trying to build libvirt using meson with the latest upstream libvirt, but the compilation fails: (followed on https://libvirt.org/compiling.html, not sure if any dependencies are missed. I checked, src/util/libvirt_util.a.p does not exist.) FAILED: src/util/libvirt_util.a.p/glibcompat.c.o .... In file included from

Alpine linux is a distribution that uses musl libc instead glibc. Here are my steps to reproduce: On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, and build them from source. $ clang -c hello_world.c $ ld.lld --gc-sections -m elf_x86_64 -o hello_world /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o

> > - Using CMake for the release binaries. I think I promised we'd do > > this for 3.7. I haven't actually started looking at this yet, but I'm > > still optimistic. > > I'm absolutely in agreement with this. Most of us already use CMake > for development, a lot of the buildbots are based on it and I think we > all agree that autoconf is deprecated.

I have what I hope is a simple question regarding a security practice I''ve been using in my first Rails app. I want to know if it''s worthwhile or if the extra typing isn''t worth it. I have 3 models that are related to each other. class User < AR:Base has_one :library end class Library < AR:Base belongs_to :user has_many :items end class Item < AR:Base

Can you add `--reproduce=repro` to lld command line? That generates repro.tar in your current directory which contains all input files. And then please compress and upload it somewhere so that we can take a look. On Mon, Apr 2, 2018 at 9:18 AM Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Alpine linux is a distribution that uses musl libc instead glibc. Here are

https://superjoe.s3.amazonaws.com/temp/repro.tar.xz On Mon, Apr 2, 2018 at 1:26 PM, Rui Ueyama <ruiu at google.com> wrote: > Can you add `--reproduce=repro` to lld command line? That generates > repro.tar in your current directory which contains all input files. And > then please compress and upload it somewhere so that we can take a look. > > > On Mon, Apr 2, 2018 at

Hello, I'm trying to create a pure LLVM toolchain (that will not depend on GNU and produce GNU-free code too) on a musl based distribution. For now, I use gcc to bootstrap and build all LLVM components. I do it individually because I was running out of space and memory trying to build all using LLVM_ENABLE_PROJECTS. Also, I don't want to create a all-in-one package. Then, once

On Fri, Aug 04, 2017 at 04:40:44PM -0600, Jonathan Roelofs wrote: > Might be a helpful exercise for you to try building vanilla clang with > runtimes for the host, before worrying about how to build everything for > your baremetal case: > http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary So I did. :o) It was fun realizing how much Release type reduces LD

There is incompatibility between R strptime and musl libc. I posted about it on their mailing list, but they need more information I can't provide, so I'm forwarding the message here in hope R developers can help. Thanks. ---------- Forwarded message ---------- From: Rich Felker <dalias at libc.org> Date: Thu, Feb 4, 2016 at 2:07 PM Subject: Re: [musl] strptime() question To: Alba