similar to: Trouble configuring with macvtap passthrough on Debian Wheezy / Jessie

Hello If I'm not terribly mistaken, looks like libvirt 1.2.1 does not provide ability of merging only a subset of the entire chain of backing files. So, if I have a chain like this: root <- a <-b <- c <- d <- active ... and I'd like to obtain a chain like this: root <- c <- d <- active ... looks like it's not supported,

Hello, I've configured a network passtrough like this: <interface type='direct'> <mac address='52:54:00:ec:e8:d9'/> <source dev='eth1' mode='passthrough'/> <target dev='macvtap0'/> <model type='rtl8139'/> <alias name='net1'/> <address type='pci'

Hello Eric, Absolutely enlightening! Thanks a lot :) Richard Gomes http://rgomes.info http://www.linkedin.com/in/rgomes mobile: +44(77)9955-6813 inum <http://www.inum.net/>: +883(5100)0800-9804 sip:rgomes@ippi.fr On 29/01/14 16:46, Eric Blake wrote: > On 01/29/2014 07:51 AM, Richard Gomes wrote: >> Hello >> >> If I'm not terribly mistaken, looks like libvirt

Hi, On Fri, May 23, 2014 at 10:57:31AM -0300, Mauricio Faria de Oliveira wrote: > > The ppc64el port needs klibc's static binaries, like ppc64. This segfaulting is a bug in klibc that needs investigation. > This patch enables the ARCH=ppc64 make env var in debian/rules, in order > for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. I have no problem

qemu has supported virtio-serial since forever, and we depend on much newer features now, so testing for virtio-serial is pointless. In fact allowing a set of possible qemu binaries to be supplied is also pointless, since packagers or even people building from source know what qemu binary they want to use. Now the possible options for --with-qemu are: * --with-qemu=search (or --with-qemu

From: "Richard W.M. Jones" <rjones at redhat.com> This means there will be no default hypervisor, and effectively the user will always have to specify one (eg. by setting LIBGUESTFS_HV or calling guestfs_set_hv). This is useful on platforms where qemu doesn't work, or where qemu is not needed (eg. if you want to use UML, or you just want to compile libguestfs without

This one's for maks' git, not for hpa's. Tell klibc what the compiler defaults already require: armhf is thumb. Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 1fb4c44..ec55d7d 100755 --- a/debian/rules +++ b/debian/rules @@ -10,7 +10,7 @@ ifeq

Hi, we?re currently seeing trouble with klibc on several architectures, cf. http://www.zytor.com/pipermail/klibc/2012-May/003277.html and armhf is being one of them, when using klibc to compile mksh-static with it. I can look into it (asked zumbi for build-deps in a sid chroot on harris already), but not 100% sure I?ll find it, so more eyes on klibc would not be unwelcome ;-) maks, does klibc

Initially out there as #965245. I strongly prefer to build ARM64 packages on non-ARM systems. Something about my main build machine having twice the cores and twice the clock speed. As such after many builds I've managed to generate a set of patches which appear to mostly function to get functioning cross-builds of Xen. These are NOT a 100% solution. Some packaging hacks were needed. In

Hai...   Finaly im passed all errors, some problem with meself.. , some the code. ..    Lots of thank to the samba devs, that gave the clue to fix the last parts. :-)) whoehoe..   Its still in the stretch-experimental repo, and if the feedback is ok, i'll make the final build tomorrow. Testing can be done with Debian Stretch or Ubuntu 18.04 amd64 or Devuan ASCII AMD64 only.   #setup: get

V4 of the patch, incorporating Bastian's suggestions. Jon --- xen/debian/patches/series | 1 + xen/debian/patches/tools-ocaml-fix-build.diff | 81 +++++++++++++++++++++++++ xen/debian/rules | 5 ++ xen/debian/rules.real | 39 ++++++++++++ xen/debian/templates/control.main.in | 16 +++++

Cool, i'll help out a bit with the windows port, i will start right away with a new project on asteriskguru making nightly executable builds and installers - will post the links in -users when i'm done. Well done luigi, this will make it a lot easier for a lot of non linux guys to make their first steps in the asterisk world Crossposted to -users. Zoa Luigi Rizzo wrote: > As a

I was successful in compiling asterisk in raspbien except for the following error If I enable the gsm codec. It appears there is something in the Makefile n this directory that needs to be changed. Probably involving optimization. Not sure why it does not recognize the processor since it is one that is mentioned in the Makefile.? Any help would be appreciated. make[2]: Entering directory

On Mar 19, 2008, at 2:03 PM, Török Edwin wrote: > > What is kext64, and how do I disable it? Comes from: APPLE_LOCAL='APPLE LOCAL libcc_kext' \ MULTILIBS="`$(GCC_FOR_TARGET) --print-multi-lib` static;@static at fno-pic kext;@Dmal loc=kern_os_malloc at Dfree=kern_os_free at DLIBCC_KEXT@static at fno-pic@fno- exceptions at fno-non-ca

Hi Guys, Looked at lotsa places on the Web/archives already. Does anyone have a Makefile for Asterisk 1.4 that integrates spandsp, app_rxfax, & app_txfax? This patch sure doesn't work with the Asterisk 1.4 Makefile: <http://soft-switch.org/downloads/spandsp/spandsp-0.0.2pre26/asterisk-1.2.x/apps_Makefile.patch> ==============================================================

Thanks, Mike! I applied this to the tree. Török, please give it a try. In the meantime, I'm going to try on a Linux machine I just got access to. -bw On Wed, Mar 19, 2008 at 2:37 PM, Mike Stump <mrs at apple.com> wrote: > On Mar 19, 2008, at 2:03 PM, Török Edwin wrote: > > > > What is kext64, and how do I disable it? > > Comes from: > >

Bill Wendling wrote: > On Wed, Mar 19, 2008 at 12:11 PM, Duncan Sands <baldrick at free.fr> wrote: > >> Hi Bill, thanks for fixing it. >> >> > No prob! :-) I can't build llvm-gcc4.2 on x86-32 Linux. What is kext64, and how do I disable it? (I suppose I don't need it on a 32-bit platform?) ..... ranlib kext/libgcc_eh.a

With the -Wformat-truncation warnings fixed, finish the job started in commit a61ddb4393ad ("drm: enable (most) W=1 warnings by default across the subsystem"), and enable that warning too. Signed-off-by: Jani Nikula <jani.nikula at intel.com> --- Gut feeling says there are more issues, and my configs just don't catch them all, but let's see what the build bots have to

On Wed, Mar 19, 2008 at 12:11 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Bill, thanks for fixing it. > No prob! :-) > > > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c: In function 'ix86_expand_convert_uns_DI2DF_sse': > > > ../../gcc-4.2.llvm.master/gcc/config/i386/i386.c:10270: warning: large integer implicitly truncated to unsigned type

Hi Jani, On Thu, May 23, 2024 at 06:51:09PM +0300, Jani Nikula wrote: > With the -Wformat-truncation warnings fixed, finish the job started in > commit a61ddb4393ad ("drm: enable (most) W=1 warnings by default across > the subsystem"), and enable that warning too. > > Signed-off-by: Jani Nikula <jani.nikula at intel.com> When it is enabled for all of drm then the