From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: virtualbox 6.1.34 is broken with Windows guests (please downgrade)
Date: Mon, 18 Jul 2022 02:57:58 +0200 [thread overview]
Message-ID: <20220718005758.RexYE3Yevg5y8-03X3uZM8USdWNsaE4LtfZKvY6gR5Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38116@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/38116#issuecomment-1186652714
Comment:
```sh
g++ -c -O2 -fno-pie -nostdinc -g -pipe -pedantic -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter -Wlogical-op -Wno-variadic-macros -Wno-long-long -Wunused-variable -Wunused-function -Wunused-label -Wunused-parameter -Wno-overloaded-virtual -Wno-array-bounds -Wno-ignored-qualifiers -Wno-variadic-macros -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fno-exceptions -fno-stack-protector -fno-common -fvisibility-inlines-hidden -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fno-rtti -ffreestanding -fPIC -m64 -mno-red-zone -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fasynchronous-unwind-tables -I/builddir/VirtualBox-6.1.34/src/VBox/Devices/build -I/builddir/VirtualBox-6.1.34/include/VBox/Graphics -I/builddir/VirtualBox-6.1.34/include/iprt/nocrt -I/builddir/VirtualBox-6.1.34/out/linux.amd64/release/obj/VBoxDDR0/dtrace -I/builddir/VirtualBox-6.1.34/out/linux.amd64/release/obj/VBoxDDR0/dtrace -I/builddir/VirtualBox-6.1.34/include -I/builddir/VirtualBox-6.1.34/out/linux.amd64/release -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" -DRTPATH_APP_DOCS=\"\" -DIN_RING0 -DIN_RING0_AGNOSTIC -DIPRT_NO_CRT -DRT_WITH_NOCRT_ALIASES -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DVBOX_WITH_DTRACE -DVBOX_WITH_DTRACE_R0 -DIN_RT_R0 -DVBOX_WITH_HGCM -DVBOX_WITH_HGSMI -DVBOX_WITH_WDDM -DVBOX_WITH_VDMA -DVBOXWDDM_WITH_VBVA -DVBOX_WITH_INTEL_HDA -DVBOX_WITH_AUDIO_ENUM -DVBOX_WITH_AUDIO_CALLBACKS -DVBOX_WITH_INTEL_HDA -DVBOX_WITH_E1000 -DVBOX_WITH_VIRTIO -DVBOX_WITH_NETSHAPER -DVBOX_WITH_VMSVGA -DVBOX_WITH_VMSVGA3D -DVBOX_WITH_VUSB -DVBOX_WITH_USB -DVBOX_WITH_EFI -DVBOX_WITH_AHCI -DIN_AHCI_R0 -DVBOX_WITH_BUSLOGIC -DVBOX_WITH_LSILOGIC -DVBOX_WITH_VIRTIO_SCSI -DVBOX_WITH_HGSMI -DVBOX_WITH_VIDEOHWACCEL -Wp,-MD,/builddir/VirtualBox-6.1.34/out/linux.amd64/release/obj/VBoxDDR0/build/VBoxDDR0.o.dep -Wp,-MT,/builddir/VirtualBox-6.1.34/out/linux.amd64/release/obj/VBoxDDR0/build/VBoxDDR0.o -Wp,-MP -o /builddir/VirtualBox-6.1.34/out/linux.amd64/release/obj/VBoxDDR0/build/VBoxDDR0.o /builddir/VirtualBox-6.1.34/src/VBox/Devices/build/VBoxDDR0.cpp
```
https://build.voidlinux.org/builders/x86_64_builder/builds/38499/steps/shell_3/logs/stdio
next prev parent reply other threads:[~2022-07-18 0:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 21:11 [ISSUE] " AngryPhantom
2022-07-18 0:53 ` sgn
2022-07-18 0:57 ` sgn [this message]
2022-07-18 1:04 ` slender100
2022-07-18 1:17 ` sgn
2022-07-18 8:18 ` AngryPhantom
2022-07-18 8:19 ` AngryPhantom
2022-07-18 11:32 ` dmarto
2022-07-18 12:57 ` sgn
2022-07-18 13:40 ` dmarto
2022-07-18 15:45 ` AngryPhantom
2022-07-19 0:21 ` sgn
2022-07-20 16:40 ` AngryPhantom
2022-07-20 16:40 ` [ISSUE] [CLOSED] " AngryPhantom
2022-09-06 8:27 ` alekspickle
2022-09-06 8:28 ` alekspickle
2022-09-06 8:29 ` alekspickle
2022-09-06 10:18 ` AngryPhantom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220718005758.RexYE3Yevg5y8-03X3uZM8USdWNsaE4LtfZKvY6gR5Y@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).