search for: flavours

...cific contexts (like virt-rescue, with more network/recovery tools) without filling the main appliance. It's still WIP (the most notable lack is a proper base.tar.gz with config files of flavour packages), but I'd like to get some feedback about it. Pino Toscano (3): New API: appliance flavours appliance: add a "rescue" appliance for virt-rescue appliance: move openssh to the "rescue" appliance appliance/Makefile.am | 21 ++++++++++++++++++++- appliance/packagelist-rescue.in | 32 ++++++++++++++++++++++++++++++++ appliance/packagelist.in | 4 ---...

Hi all, I have built a test version of the glibc with a xen flavour. It is available on http://people.debian.org/~aurel32/xen/ . The only difference with the version currently in sid is the presence of the libc6-xen package. If you are using xen, please test it and tell me if it fixes speed problems. If everything is ok, I will commit it into our SVN. Bye, Aurelien -- .''`.

...d line as the universal interface in the > future versions of their toolchains. > > I completely agree; that's why I said this is not feasible for the time > being. > > I am still wondering about a few things: > > Is it desired to address the functional difference of the flavours at all? > > Is it a bug if a flavour has a feature that its original counterpart does > not have? For example, would it be > acceptable to add scripting support to the Darwin flavour, given that > Apple ld64 does not support scripts? No and no. It is not desired and it is not a bug...

Hello everybody, by the way, speaking about the r-cran-rcurl package in Ubuntu, the versions in trusty and vivid are linked by error to the "NSS" flavour of libcurl3 instead of the "OpenSSL flavour", which cause at least problems when using the CRAN devtools package. A bit more details are available in the Debian bug tracking system (https://bugs.debian.org/786473). I am not

...hink you need to convince not us but other first-party toolchain developers. In my opinion, GNU ld has CLI closest to my description, so it is a good > basis for a universal interface. In fact, GNU flavour can be universal if > support > for more targets is added there, but then the other flavours will likely > be redundant. One difference would be that a universal CLI need not > maintain compatibility > with GNU ld CLI. > > > On 1 Nov 2017, at 20:36, Rui Ueyama <ruiu at google.com> wrote: > > > > Most command line options in GNU, macOS and MSVC are not ju...

Hi all, As some of you might know, the FLAC format is being processed by an IETF working group to become an internationally recognized standard. Part of this process is FLAC being assigned a media type (also known as MIME-type by many): audio/flac. However, during review of the application, it was requested to include a UTI and a Windows Clipboard Flavour Name. Now, apparently the latest macOS

...nt given: ~~~ function jsPostAppend(script, form_id) { if(form_id) //parameters=''&'' + $(form_id).serialize() // first flavour parameters=''&'' + Form.serialize($(form_id)) // second flavour [...] ~~~ This works perfect for FF2, IE7 and Safari3 (in both flavours). With Opera 9.x, I get the following javascript errors: First flavour: ~~~ JavaScript - https://...url.../file.php Event thread: click Error: name: TypeError message: Statement on line 47: Type mismatch (usually a non-object value used where an object is required) Backtrace: Line 47 of linked s...

...when invoked. However, it looks like this option also determines the set of supported targets we are linking for. For example, lld -flavor gnu cannot link mach-o binaries, and could not link PE binaries either (well, not until rL312926). Is this really intended by the design of lld? It looks the flavours are merely legacy compatibility shims, but then why is there no universal lld driver that is able to link binary for any platform using a unified CLI?

...e "Type" [] [PCData "balloon"]; > e "Device" [] [PCData "memballoon"]; > + e "SpecParams" [] [ > + e "model" [] [PCData "virtio"] > + ] Are they needed in both the flavours of OVF? (Not a problem for me, just asking to understand it better.) -- Pino Toscano

When writing the OVF in OVirt flavour, write the actual UUID of the VM as ovf:id attribute for <VirtualSystem>, instead of a dummy value. Suggested by Arik Hadas in https://www.redhat.com/archives/libguestfs/2018-April/msg00005.html --- v2v/create_ovf.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/create_ovf.ml b/v2v/create_ovf.ml index f56c4cb64..554374f45

When writing the OVF in OVirt flavour, write the actual UUID of the VM as ovf:id attribute for <VirtualSystem>, instead of a dummy value. Suggested by Arik Hadas in https://www.redhat.com/archives/libguestfs/2018-April/msg00005.html --- v2v/create_ovf.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/create_ovf.ml b/v2v/create_ovf.ml index ce06ce613..2fc041168

Due to a conflict with the IDs of the OVF standard, and the existing implementation in ovirt-engine, the ID of QXL devices changed to a different value. As a consequence, change the ResourceType of QXL devices, but only in OVirt flavour to avoid breaking vdsm mode. See: https://bugzilla.redhat.com/show_bug.cgi?id=1598715#c5 --- v2v/create_ovf.ml | 6 +++++-

...istent with GCC. > > I think it's just so that we have a way to actually write out the > symbol into the assembly file. What does gcc do? > > -Eli > > It emits the high bits literally. The consequence is that UTF-8-encoded identifiers come out in UTF-8: scshunt at natural-flavours:~$ gcc -fextended-identifiers -std=c99 -x c -c -o test.o - int i\u03bb; scshunt at natural-flavours:~$ nm test.o 00000004 C iλ scshunt at natural-flavours:~$ As you can see, the nm output includes the literal lambda. Sean -------------- next part -------------- An HTML attachment was scrubbed......

...of > supported targets we are linking for. For example, lld -flavor gnu > >>>> cannot link mach-o binaries, and could not link PE binaries either > (well, not until rL312926). > >>>> > >>>> Is this really intended by the design of lld? It looks the flavours > are merely legacy compatibility shims, but then why is there no > >>>> universal lld driver that is able to link binary for any platform > using a unified CLI? > >>>> _______________________________________________ > >>>> LLVM Developers mailing...

On Thu, 5 Apr 2018 14:53:51 +0200 Pino Toscano <ptoscano@redhat.com> wrote: > @@ -383,8 +581,9 @@ let rec create_ovf source targets guestcaps inspect > ] in > (match ovf_flavour with > | OVirt -> > - e "OperatingSystemSection" ["ovf:id", vm_uuid; > - "ovf:required",

Hello! Is it possible to make the sources a bit more portable? I'm on QNX4 with Watcom C v10.6B which has no support for int64. I'd like to be able to compile as many modules as do not depend on int64. (Currently I do not need SFTP that bad, the SSH is enough for me) -- Best regards, Anthony mailto:rz1a at mail.ru

...this option also determines the set of supported > targets we are linking for. For example, lld -flavor gnu > > cannot link mach-o binaries, and could not link PE binaries either > (well, not until rL312926). > > > > Is this really intended by the design of lld? It looks the flavours are > merely legacy compatibility shims, but then why is there no > > universal lld driver that is able to link binary for any platform using > a unified CLI? > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llv...

...is GPL as well. I was shaken when I have discovered my mistake :-) This basically made it unusable for many users which want to use ssh in commercial environments. Thus I decided to port OpenSSH to OS/2, to get a really free ssh. After looking at your web site I've found that there are two flavours of openssh: OpenBSD and "portable" version. Thus I have the question: which flavour should I base my work upon? I could derive it from "portable" ssh, but I believe I will find hardly a single common line between other OS-es and OS/2. In general, I prefer to avoid all kinds...

...this option also determines the set of supported > targets we are linking for. For example, lld -flavor gnu > > cannot link mach-o binaries, and could not link PE binaries either > (well, not until rL312926). > > > > Is this really intended by the design of lld? It looks the flavours are > merely legacy compatibility shims, but then why is there no > > universal lld driver that is able to link binary for any platform using > a unified CLI? > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llv...

Hi, v2 of this patch: https://www.redhat.com/archives/libguestfs/2018-April/msg00003.html that includes an additional fix. Thanks, Pino Toscano (2): v2v: OVF: write ovirt:id attribute for the OS in OVirt flavour v2v: OVF: fix ovf:id for VirtualSystem in OVirt flavour v2v/create_ovf.ml | 204 +++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 202 insertions(+), 2