summary refs log tree commit diff stats
path: root/hw/char/xilinx_uartlite.c
diff options
context:
space:
mode:
authorChristian Ehrhardt <christian.ehrhardt@canonical.com>2020-12-14 16:09:38 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2020-12-15 12:53:16 -0500
commitbbd2d5a8120771ec59b86a80a1f51884e0a26e53 (patch)
treeffedf1f33d354efc539aae971aaf5d6639857374 /hw/char/xilinx_uartlite.c
parenta1bcbb485c91c0869832b0bda62ff564ddfc52f3 (diff)
downloadfocaccia-qemu-bbd2d5a8120771ec59b86a80a1f51884e0a26e53.tar.gz
focaccia-qemu-bbd2d5a8120771ec59b86a80a1f51884e0a26e53.zip
build: -no-pie is no functional linker flag
Recent binutils changes dropping unsupported options [1] caused a build
issue in regard to the optionroms.

  ld -m elf_i386 -T /<<PKGBUILDDIR>>/pc-bios/optionrom//flat.lds -no-pie \
    -s -o multiboot.img multiboot.o
  ld.bfd: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)

This isn't really a regression in ld.bfd, filing the bug upstream
revealed that this never worked as a ld flag [2] - in fact it seems we
were by accident setting --nmagic).

Since it never had the wanted effect this usage of LDFLAGS_NOPIE, should be
droppable without any effect. This also is the only use-case of LDFLAGS_NOPIE
in .mak, therefore we can also remove it from being added there.

[1]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=983d925d
[2]: https://sourceware.org/bugzilla/show_bug.cgi?id=27050#c5

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Message-Id: <20201214150938.1297512-1-christian.ehrhardt@canonical.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'hw/char/xilinx_uartlite.c')
0 files changed, 0 insertions, 0 deletions