search for: _types

On Fri, 2020-09-25 at 10:33 +0800, Wei Wang wrote: > In file included from ../src/util/virfile.c:42: > /usr/include/libutil.h:43:10: fatal error: sys/_types.h: No such file or directory > 43 | #include <sys/_types.h> > | ^~~~~~~~~~~~~~ > compilation terminated. > [51/908] Compiling C object src/qemu/libvirt_driver_qemu_impl.a.p/qemu_driver.c.o > ninja: build stopped: subcommand failed > > I have /usr/incl...

...1 +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: > > > In file included from ../src/util/virfile.c:42: > > > /usr/include/libutil.h:43:10: fatal error: sys/_types.h: No such file or directory > > > 43 | #include <sys/_types.h> > > > | ^~~~~~~~~~~~~~ > > > compilation terminated. > > > [51/908] Compiling C object src/qemu/libvirt_driver_qemu_impl.a.p/qemu_driver.c.o > > > ninja: build stoppe...

...bj/../runtime/GCCLibraries/crtend/SJLJ-Exception.cpp:16: > /usr/home/llvm/cfrontend/x86/llvm-gcc/bin/../lib/gcc/i686-pc-linux-gnu/3.4-llvm/../../../../include/c++/3.4-llvm/i686-pc-linux-gnu/bits/os_defines.h:39:22: features.h: No such file or directory > In file included from /usr/include/sys/_types.h:33, > from /usr/include/stdlib.h:42, > from /usr/home/llvm/cfrontend/x86/llvm-gcc/bin/../lib/gcc/i686-pc-linux-gnu/3.4-llvm/../../../../include/c++/3.4-llvm/cstdlib:52, > from /usr/home/llvm/obj/../runtime/GCCLibraries/crtend/SJLJ-Except...

...ome/llvm/obj/../runtime/GCCLibraries/crtend/SJLJ-Exception.cpp:16: /usr/home/llvm/cfrontend/x86/llvm-gcc/bin/../lib/gcc/i686-pc-linux-gnu/3.4-llvm/../../../../include/c++/3.4-llvm/i686-pc-linux-gnu/bits/os_defines.h:39:22: features.h: No such file or directory In file included from /usr/include/sys/_types.h:33, from /usr/include/stdlib.h:42, from /usr/home/llvm/cfrontend/x86/llvm-gcc/bin/../lib/gcc/i686-pc-linux-gnu/3.4-llvm/../../../../include/c++/3.4-llvm/cstdlib:52, from /usr/home/llvm/obj/../runtime/GCCLibraries/crtend/SJLJ-Exception.cpp:16: /us...

On Thu, Sep 24, 2020 at 2:58 PM Ján Tomko <jtomko@redhat.com> wrote: > On a Thursday in 2020, Wei Wang wrote: > >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

...ime/GCCLibraries/crtend/SJLJ-Exception.cpp:16: > > /usr/home/llvm/cfrontend/x86/llvm-gcc/bin/../lib/gcc/i686-pc-linux-gnu/3.4-llvm/../../../../include/c++/3.4-llvm/i686-pc-linux-gnu/bits/os_defines.h:39:22: features.h: No such file or directory > > In file included from /usr/include/sys/_types.h:33, > > from /usr/include/stdlib.h:42, > > from /usr/home/llvm/cfrontend/x86/llvm-gcc/bin/../lib/gcc/i686-pc-linux-gnu/3.4-llvm/../../../../include/c++/3.4-llvm/cstdlib:52, > > from /usr/home/llvm/obj/../runtime/GCCLibraries/crt...

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: > > In file included from ../src/util/virfile.c:42: > > /usr/include/libutil.h:43:10: fatal error: sys/_types.h: No such file or > directory > > 43 | #include <sys/_types.h> > > | ^~~~~~~~~~~~~~ > > compilation terminated. > > [51/908] Compiling C object > src/qemu/libvirt_driver_qemu_impl.a.p/qemu_driver.c.o > > ninja: build stopped: subcommand f...

...> > 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: > > > > In file included from ../src/util/virfile.c:42: > > > > /usr/include/libutil.h:43:10: fatal error: sys/_types.h: No such > file or directory > > > > 43 | #include <sys/_types.h> > > > > | ^~~~~~~~~~~~~~ > > > > compilation terminated. > > > > [51/908] Compiling C object > src/qemu/libvirt_driver_qemu_impl.a.p/qemu_driver.c.o >...

Hello Michael, > The module dump suggests everything is right, i can see in the function call the struct with the values 10 and 25, but the function is only received the 10 for the x field, nothing for the y field.  Am I missing something? You're missing the Platform ABI. I assume you're on x86-64, then your struct (according to the ABI) should be passed in a single 64 bit register as

I've tried to build something that wanted ms-extensions on OpenBSD. Long story short, didn't work so well, because all system includes lead to <machine/_types.h> #ifndef __cplusplus typedef int __wchar_t; #endif and since ms-extensions includes __char_t as a built-in, this did fail abysmally. It would be simple to fix in OpenBSD, assuming clang did tell us it was using ms-extensions. Would something like this be appropriate ? ma...

...op_srcdir="/opt/projects/libvirt"' -MD -MQ src/util/libvirt_util.a.p/virfile.c.o -MF src/util/libvirt_util.a.p/virfile.c.o.d -o src/util/libvirt_util.a.p/virfile.c.o -c ../src/util/virfile.c In file included from ../src/util/virfile.c:42: /usr/include/libutil.h:43:10: fatal error: sys/_types.h: No such file or directory 43 | #include <sys/_types.h> | ^~~~~~~~~~~~~~ compilation terminated. [51/908] Compiling C object src/qemu/libvirt_driver_qemu_impl.a.p/qemu_driver.c.o ninja: build stopped: subcommand failed I have /usr/include/sys/types.h, but no "_types...

I've been working on a wrapper for LLVM's C++ API to use from Objective-C for a scripting language I'm working on. I currently have an issue with passing arguments to a function that takes a struct argument. typedef struct _test_struct { int x; int y; } test_struct; id testLLVMStructFuncCall(test_struct x) { NSLog(@"%d %d",x.x,x.y); return N(x.x + x.y); }

...xen-3.3.0/stubdom/../extras/mini-os/include/mini-os/sched.h:5, from /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/errno.h:116, from ../../../../../newlib-1.16.0/newlib/libc/argz/argz_add.c:7: /usr/src/xen-3.3.0/stubdom/newlib-1.16.0/newlib/libc/include/sys/_types.h:76: erreur: expected specifier-qualifier-list before ''wint_t '' In file included from /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/posix/time.h:6, from /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/mini-os/time.h:52, from /usr/...

I have two questions about the CRAN machines that build binary packages for Mac. When a new version of a package is released, (A) Do the downstream dependencies get re-checked? (B) Do the downstream dependencies get re-built? I have heard (but do not know for sure) that the answer to (A) is no, the downstream dependencies do not get rechecked. >From publicly available information on the

...p 25, 2020 at 3:56 PM Andrea Bolognani <abologna@redhat.com> > > wrote: > > > > On Fri, 2020-09-25 at 10:33 +0800, Wei Wang wrote: > > > > > In file included from ../src/util/virfile.c:42: > > > > > /usr/include/libutil.h:43:10: fatal error: sys/_types.h: No such > > file or directory > > > > > 43 | #include <sys/_types.h> > > > > > | ^~~~~~~~~~~~~~ > > > > > compilation terminated. > > > > > [51/908] Compiling C object > > src/qemu/libvirt_driver_qemu...

...hose guest types will be able to use many > operations without paravirt abstraction while still supporting all the > other paravirt features. > > For now just add the new Kconfig option and select it for XEN_PV and > LGUEST_GUEST. Add paravirt_full.c, paravirt_full.h and > paravirt_types_full.h which will contain the necessary implementation > parts of the pv guest specific paravirt functions. Is it not possible to just 'ifdef CONFIG_PARAVIT_FULL' the (ir)relevant parts of paravirt.[ch] and paravirt_types.c? Separating structures and files into pv and pvfull seems some...

...hose guest types will be able to use many > operations without paravirt abstraction while still supporting all the > other paravirt features. > > For now just add the new Kconfig option and select it for XEN_PV and > LGUEST_GUEST. Add paravirt_full.c, paravirt_full.h and > paravirt_types_full.h which will contain the necessary implementation > parts of the pv guest specific paravirt functions. Is it not possible to just 'ifdef CONFIG_PARAVIT_FULL' the (ir)relevant parts of paravirt.[ch] and paravirt_types.c? Separating structures and files into pv and pvfull seems some...

...t 20:04, Marc Espie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > I've tried to build something that wanted ms-extensions on OpenBSD. > > Long story short, didn't work so well, because all system includes > > lead to > > > > <machine/_types.h> > > #ifndef __cplusplus > > typedef int __wchar_t; > > #endif > > > > and since ms-extensions includes __char_t as a built-in, this did fail > > abysmally. > > Back in 2014 when we encountered this in FreeBSD, we just renamed our...

...that worked well was G++ 6.x I've asked about this issue both on GDB and LLDB maillists. Unfortunately it's hard or impossible to fix it on debugger side. The problem is that compilers do not emit linkage name of type to debug information, and so debuggers can't link RTTI with DW_TAG_*_types reliably. Consider example: //////////////////////////////////////////////////////////////// enum class EN{ONE,TWO}; template<auto x> struct foo { virtual ~foo() {} }; foo<11u> fu; foo<11> fi; foo<EN::ONE> fe; /////////////////////////////////////////////////////////////...

...nstant /home/ang/build/llvm-gcc-4.2-2.7/./gcc/include/stddef.h:214: error: expected ide ntifier or '(' before string constant /home/ang/build/llvm-gcc-4.2-2.7/./gcc/include/stddef.h:326: error: expected ide ntifier or '(' before string constant In file included from /usr/include/sys/_types.h:63, from /usr/include/sys/reent.h:14, from /usr/include/stdio.h:45, from /home/ang/src/llvm-gcc4.2-2.7.source/gcc/tsystem.h:90, from /home/ang/src/llvm-gcc4.2-2.7.source/gcc/config/i386/cygmi ng-crtbegin.c:37: /home/ang/build/llv...