search for: monolithically

I have one reasone why we should not moe to monolithic repository - If you do some light stuff like clang-tidy, that don't often require syncing with clang, but you still want to have the most recent checks, then I don't see a solution in monolithic repository. And this is a real issue if you only have 2 or 4 core laptop to do work. And I guess the the build system won't solve the

Dear all, I would like to (re-)open a discussion on the following specific question: Assuming we are moving the llvm project to git, should we a) use multiple git repositories, linked together as subrepositories of an umbrella repo, or b) use a single git repository for most llvm subprojects. The current proposal assembled by Renato follows option (a), but I think option (b) will be

I spun a new xen kernel from pristine sources using modules, had the APCI errors and scsi timeouts. I took pristine source and spun a monolithic kernel and everything appears to be working. gcc version 3.4.4 20050721 (Red Hat 3.4.4-2) if it matter. xen_changeset : Wed Oct 26 11:59:13 2005 +0100 7500:20d1a79ebe31 I have had this APCI issue on this SMP Athlon with modules for a while now.

On 22 July 2016 at 11:16, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > There's another reason I've been staying quiet too which is that past > experience with VCS migrations has taught me that people tend to over-value > some things and that discussion tends not to convince people in advance of > direct experience. I think some of these topics will end up being

The build system can help, you just need to have two (sparse) checkout: one for LLVM/clang and the other for clang-tidy, and configure the build with the LLVM/clang checkout adding the clang-tidy as external. — Mehdi > On Jul 22, 2016, at 1:22 PM, Piotr Padlewski via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > And the same thing happen to IDEs - I would not like to spend

One other point about maintaining branches: With the single repository approach, maintaining a long-running branch that touches multiple subprojects (e.g. llvm and clang) becomes *far* simpler. With the umbrella repo, you have to do the submodules trickery I described in the original e-mail. It is complicated, and takes a lot of typing (or requires you to develop custom scripts). But with the

Hi, All ! I'm trying to use nut 2.0.5 on FreeBSD 4.11-STABLE with UPS INELT Monolith II 1000LT UPS connected to box with RS-232 cable. In ups.conf: [apc] driver = megatec port = /dev/cuaa1 desc = "UPS" When starting /usr/local/etc/rc.d/nut.sh start got: Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Megatec protocol driver 1.5 (2.0.5) Carlos Rodrigues (c)

I guess perl 5.18 was released and it is causing issues texi2html -monolithic -number-sections qemu-doc.texi texi2html -monolithic -number-sections qemu-tech.texi /data/dev/xen/xen-4.3-git/src/xen-build/tools/qemu-xen-traditional-dir/ texi2pod.pl qemu-doc.texi qemu.pod pod2man --section=1 --center=" " --release=" " qemu.pod > qemu.1 qemu.pod around line 91: Non-ASCII

I guess perl 5.18 was released and it is causing issues texi2html -monolithic -number-sections qemu-doc.texi texi2html -monolithic -number-sections qemu-tech.texi /data/dev/xen/xen-4.3-git/src/xen-build/tools/qemu-xen-traditional-dir/ texi2pod.pl qemu-doc.texi qemu.pod pod2man --section=1 --center=" " --release=" " qemu.pod > qemu.1 qemu.pod around line 91: Non-ASCII

I have a data frame with three columns, type (a factor with two values: "Monolithic" and "Compositional"), size (numeric), and states (numeric). I want to create a plot where size goes on the x-axis and states goes on the y-axis. In this plot, I want two lines, one where the type is "Monolithic" and one where the type is "Compositional". I think this can

> Which projects do we put under this monolithic repository? The proposal at the moment is to include llvm, clang, clang-tools-extra, lld, polly, lldb, llgo, compiler-rt, openmp, and parallel-libs. This is the set {llvm} plus the transitive closure of "projects that are version-locked to a project in the set", where the closure is taken over the set of all active LLVM

On Friday, 10 January 2020 15:05:33 CET Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.

On Fri, Jan 10, 2020 at 02:05:33PM +0000, Richard W.M. Jones wrote: > libguestfs usually needs qemu. However it only requires an emulator > for the same architecture, not for all architectures. > libvirt-daemon-kvm pulls in qemu which pulls in emulators for all > architectures, as well as a bunch of other stuff we don't need at all > like network interface support and nwfilter.

On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > Do you use the libvirt "secret" APIs at all (disk encryption, network > > disk auth passwords) ? If so you will need "libvirt-daemon-driver-secret" > > too. How about any other libvirt sub-driver APIs ? Networking ?

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. --- libguestfs.spec

On Friday, 10 January 2020 17:34:27 CET Daniel P. Berrangé wrote: > > > > virStoragePoolFree ( > > > > virStoragePoolGetInfo ( > > > > virStoragePoolLookupByName ( > > > > virStorageVolFree ( > > > > virStorageVolGetInfo ( > > > > virStorageVolGetPath ( > > > > virStorageVolLookupByName ( > > > > >

Monolithic is trying to solve the wrong problem - it's that simple. Any discussion or attempt to coddle those who think it's necessary is a waste of time. #dictator As part of any potential migration, everyone involved must start to accept certain changes, (large or small) to the workflow. The big challenge here isn't technical, it's mindset. It's convincing any group of

On Fri, Jan 10, 2020 at 05:21:23PM +0100, Pino Toscano wrote: > On Friday, 10 January 2020 15:39:21 CET Daniel P. Berrangé wrote: > > On Fri, Jan 10, 2020 at 02:26:35PM +0000, Richard W.M. Jones wrote: > > > On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > > > > Do you use the libvirt "secret" APIs at all (disk encryption, network >

Thanks for the update Andy. I'm very happy to be involved in anyway that is helpful. If you would like me to test ideas, or contribute to further discussions, then please let me know. I currently have extempore running nicely with MCJIT for the "monolithic" case and am working on various LLVM hacks to better understand the issues involved with non-monolithic approaches - in