similar to: virt-v2v: error: redefinition of 'glib_autoptr_clear_OsinfoList'

On Monday, 1 June 2020 04:17:00 CEST Kevin Locke wrote: > Hi All, > > I'm attempting to compile virt-v2v 1.42.0 on Debian testing. With gcc > 9.3.0, libosinfo 1.7.1, and glib 2.64.2, `./configure && make` fails > on libosinfo-c.c with the following error message: > > -8<-------------------------------------------------------------------- > In file included

hi my graduation project is" voice over ip" and i want to make codec to voice with speex-1.1.12 , i try to run it in my computer by" visual studio 6" but i have problems 1-i want to get exe file to speexdec&speexenc(i found missing files "glib.h, glibconfig.h, o gg/ogg.h, glib/gmacros.h , ogg_static.dsp" when i found it i have errors in the speexenc.c or

Greetings everybody! I've created a patch to get compiz (upstream about 2 hours old) away from libsvg and libsvg-cairo. Those two libraries, which are regarded as "dead meat" by their initial developer Carl Worth, are replaced with librsvg 2.14.x (e.g. part of Gnome 2.14.x) by this patch. The patch is rather small and only touches these three files: compiz/configure.ac

On Wed, Dec 7, 2016 at 10:36 AM Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2016-Dec-07, at 10:14, Teresa Johnson <tejohnson at google.com> wrote: > > > > A couple weeks ago I sat down with David Blaikie to figure out what we > could trim when importing debug metadata during function importing. I have > a prototype that reduces the

+pcc to answer question about global variable list on CU Thanks for the comments, responses below. Teresa On Wed, Dec 7, 2016 at 10:36 AM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2016-Dec-07, at 10:14, Teresa Johnson <tejohnson at google.com> wrote: > > > > A couple weeks ago I sat down with David Blaikie to figure out what we >

A couple weeks ago I sat down with David Blaikie to figure out what we could trim when importing debug metadata during function importing. I have a prototype that reduces the resulting .o sizes significantly with ThinLTO -g. However, I ran into some issues when cleaning up part of this in preparation for a patch. Since Mehdi indicated that he and Adrian were going to be looking at this as well

Add a minimal release note text for the first standalone version, virt-p2v 1.41.0; in addition, add the first items for the future 1.42.0. --- docs/p2v-release-notes.pod | 32 ++++++++++++++++++++++++++------ 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/docs/p2v-release-notes.pod b/docs/p2v-release-notes.pod index ee0dd98..21d736d 100644 --- a/docs/p2v-release-notes.pod +++

Hi, I would like to implement macro debug info support in LLVM. Below you will find 4 parts: 1. Background on what does it mean to debug macros. 2. A brief explanation on how to represent macro debug info in DWARF 4.0. 3. The suggested design. 4. A full example: Source -> AST -> LLVM IR -> DWARF. Feel free to skip first two parts if you think you know the background.

Avoid using an auto-cleanup for OsinfoList, duplicating the cleanup everywhere needed. --- v2v/libosinfo-c.c | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-) diff --git a/v2v/libosinfo-c.c b/v2v/libosinfo-c.c index 322e7d3d..75c2fae4 100644 --- a/v2v/libosinfo-c.c +++ b/v2v/libosinfo-c.c @@ -49,17 +49,6 @@ #if !IS_LIBOSINFO_VERSION(1, 8, 0)

> Do we really need to touch the AST? Or would it be reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) This sound as a good idea, I will check that approach. PPCallbacks is only an interface, has nothing connected to it, but we will create a new class, which implement PPCallbacks, for macros. So we can

> Not necessarily, if we kept the macros in order in the list of macros attached to the CU, which I imagine we would. OK, now I understand what you are aiming for. I really do not favor one on the other. But, can you explain what is the advantage of the parent approach over the children approach? If any, the children approach seems to be the one reduces the LLVM IR size, is not it? Regards,

> Right - I was wondering if CGDebugInfo already implemented PPCallbacks or was otherwise being notified of PPCallback related things, possibly through a layer or two of indirection. I checked the approach of skipping representing macros in AST, and communicate them directly from Parser to CGDebugInfo. However, I could not find a way to initialize this communication. The only interface

This patch series integrates libosinfo in virt-v2v to get the list of files for Windows from libosinfo, if possible. The actual data is still from virtio-win, just unpacked. Pino Toscano (3): build: require libosinfo v2v: add a minimal libosinfo interface v2v: try to get windows driver files from libosinfo m4/guestfs-v2v.m4 | 3 + v2v/Makefile.am | 9 +-

On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> wrote: > I found a way to skip representing macros in AST and create them directly > in CGDebugInfo through PPCallbacks during preprocessing. > > To do that, I needed to extend ASTConsumer interface with this extra > method: > > > > /// If the consumer is interested in notifications from

This patch series integrates libosinfo in virt-v2v to get the list of files for Windows from libosinfo, if possible. The actual data is still from virtio-win, just unpacked. Changes from v1: - adapt to use the priority in libosinfo 1.7.0+ - filter out non-pre-installable drivers - collect all the drivers matching the requirements, not just the first, sorting them by priority like libosinfo does

I'd like to jump in. I do not work on a preprocessor based language, but have the same code expansion problem to encode. Right now, we hack around the problem by appending some prefix after the file name and pretend it is a different file, which is not great. I understand you want to represent expansion by DIFileMacro ? I'm not how this is supposed to be used and it is not in the example.

On Fri, Nov 13, 2015 at 2:41 PM, Richard Smith <richard at metafoo.co.uk> wrote: > On Fri, Nov 13, 2015 at 10:21 AM, David Blaikie via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> >> wrote: >> >>> I found a way to skip representing macros in AST and create them

Hi, I am getting a weird libguestfs failure from time to time: 2020-08-27 08:48:40 T libguestfs - 0 - appliance - SeaBIOS (version 1.12.0-1) 2020-08-27 08:48:40 T libguestfs - 0 - appliance - Booting from ROM... 2020-08-27 08:48:40 T libguestfs - 0 - library - child_cleanup: 0xd5a840: child process died Let me elaborate more about my environment I am running libguestfs 1.42.0 on GCP -

On Monday, 24 August 2020 20:53:09 CEST Zachary Taylor wrote: > Here is the output from running libguestfs-test-tool: > > PATH=/home/zmt1002/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin > SELinux: sh: getenforce: command not found > guestfs_get_append: (null) >

Hi All, Thanks to your previous assistance, I'm able to compile virt-v2v 1.42.0 on Debian testing. However, when I run `make check` tests/test-v2v-oa-option.sh fails with the following log: -8<------------------------------------------------------------------ test-v2v-oa-option.sh: info: you can skip this test by setting SKIP_TEST_V2V_OA_OPTION_SH=1 [ 0.0] Opening the source -i libvirt