diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2016-05-11 14:47:59 +0200 |
|---|---|---|
| committer | David Vrabel <david.vrabel@citrix.com> | 2016-05-24 12:58:18 +0100 |
| commit | 971a69db7dc02faaeed325c195f5db5da597cb58 (patch) | |
| tree | defcbf4af0f83ebd361daba81575946da0d72130 /drivers/xen/Makefile | |
| parent | 36ae220aa62d382a8bacbf7ec080d9d36a2b4d49 (diff) | |
| download | linux-stable-971a69db7dc02faaeed325c195f5db5da597cb58.tar.gz linux-stable-971a69db7dc02faaeed325c195f5db5da597cb58.tar.bz2 linux-stable-971a69db7dc02faaeed325c195f5db5da597cb58.zip | |
Xen: don't warn about 2-byte wchar_t in efi
The XEN UEFI code has become available on the ARM architecture
recently, but now causes a link-time warning:
ld: warning: drivers/xen/efi.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
This seems harmless, because the efi code only uses 2-byte
characters when interacting with EFI, so we don't pass on those
strings to elsewhere in the system, and we just need to
silence the warning.
It is not clear to me whether we actually need to build the file
with the -fshort-wchar flag, but if we do, then we should also
pass --no-wchar-size-warning to the linker, to avoid the warning.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Fixes: 37060935dc04 ("ARM64: XEN: Add a function to initialize Xen specific UEFI runtime services")
Diffstat (limited to 'drivers/xen/Makefile')
| -rw-r--r-- | drivers/xen/Makefile | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/xen/Makefile b/drivers/xen/Makefile index 9b7a35c9e51d..030e91b38e32 100644 --- a/drivers/xen/Makefile +++ b/drivers/xen/Makefile @@ -8,6 +8,7 @@ nostackp := $(call cc-option, -fno-stack-protector) CFLAGS_features.o := $(nostackp) CFLAGS_efi.o += -fshort-wchar +LDFLAGS += $(call ld-option, --no-wchar-size-warning) dom0-$(CONFIG_PCI) += pci.o dom0-$(CONFIG_USB_SUPPORT) += dbgp.o |