Opened 6 years ago
Closed 6 years ago
#56790 closed defect (fixed)
qemu @2.12.0_1 +target_or32 configure fails with errors in qemu-conf.c
Reported by: | ShadSterling (Shad Sterling) | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.5.3 |
Keywords: | Cc: | ||
Port: | qemu |
Description
Looks like the wrong compiler is being used; I expect the relevant errors are these:
/usr/bin/clang -m64 -mcx16 -DOS_OBJECT_USE_OBJC=0 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wno-error=address-of-packed-member -Wno-string-plus-int -Wno-initializer-overrides -Wexpansion-to-defined -Wendif-labels -Wno-shift-negative-value -Wno-missing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Werror -Wold-style-declaration -o config-temp/qemu-conf.exe config-temp/qemu-conf.c -m64 -framework CoreFoundation -framework IOKit -g -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 error: unknown warning option '-Wold-style-declaration'; did you mean '-Wout-of-line-declaration'? [-Werror,-Wunknown-warning-option]
/usr/bin/clang -m64 -mcx16 -DOS_OBJECT_USE_OBJC=0 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wno-error=address-of-packed-member -Wno-string-plus-int -Wno-initializer-overrides -Wexpansion-to-defined -Wendif-labels -Wno-shift-negative-value -Wno-missing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-definition -Wtype-limits -fstack-protector-strong -Wno-missing-braces -Werror -fno-gcse -o config-temp/qemu-conf.exe config-temp/qemu-conf.c -m64 -framework CoreFoundation -framework IOKit -g -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 clang: error: optimization flag '-fno-gcse' is not supported [-Werror,-Wignored-optimization-argument]
On macOS High Sierra 10.13.5 (17F77), XCode Version 9.4.1 (9F2000), Command Line Tools 9.4
There are also several errors messages which I expect are part of normal operation; Most of those are of this form:
/usr/bin/clang -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -c -o c onfig-temp/qemu-conf.o config-temp/qemu-conf.c config-temp/qemu-conf.c:2:2: error: __linux__ not defined #error __linux__ not defined
And one is different:
/usr/bin/clang -m64 -mcx16 -DOS_OBJECT_USE_OBJC=0 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -Wno-error=address-of-packed-member -Wno-string-plus-int -Wno-initializer-overrides -Wexpansion-to-defined -Wendif-labels -Wno-shift-negative-value -Wno-missing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-definition -Wtype-limits -fstack-protector-strong -Werror -c -o config-temp/qemu-conf.o config-temp/qemu-conf.c config-temp/qemu-conf.c:3:8: error: suggest braces around initialization of subobject [-Werror,-Wmissing-braces] } x = {0}; ^ {} 1 error generated.
Attachments (2)
Change History (5)
Changed 6 years ago by ShadSterling (Shad Sterling)
Attachment: | config.log added |
---|
Changed 6 years ago by ShadSterling (Shad Sterling)
comment:1 Changed 6 years ago by mf2k (Frank Schima)
Cc: | raimue removed |
---|---|
Owner: | set to raimue |
Status: | new → assigned |
comment:2 Changed 6 years ago by raimue (Rainer Müller)
comment:3 Changed 6 years ago by raimue (Rainer Müller)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
The real error message in the normal output:
I had missed that or32 was renamed to or1k in the latest release. I am working on an update to correct this.