qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Smith <brad@comstyle.com>
To: Stefan Weil <sw@weilnetz.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Fix QEMU build on OpenBSD on x86 archs
Date: Tue, 10 Dec 2013 02:48:03 -0500	[thread overview]
Message-ID: <52A6C733.2030608@comstyle.com> (raw)
In-Reply-To: <52A6BDC8.1000209@weilnetz.de>

On 10/12/13 2:07 AM, Stefan Weil wrote:
> Am 10.12.2013 02:26, schrieb Brad Smith:
>> This resolves the build issue with building the ROMs on OpenBSD on x86 archs.
>> As of OpenBSD 5.3 the compiler builds PIE binaries by default and thus the
>> whole OS/packages and so forth. The ROMs need to have PIE disabled. This
>> is my initial attempt at trying to get somehting upstream so that QEMU
>> both builds out of the box and to resolve the build issue with the
>> buildbots that has been around for awhile. We have a patch in our ports
>> tree but it is just the flags hardcoded into the Makefile which obviously
>> is not appropriate for upstream.
>>
>>  From the OpenBSD buildbots..
>>    Building optionrom/multiboot.img
>> ld: multiboot.o: relocation R_X86_64_16 can not be used when making a shared object; recompile with -fPIC
>>
>>
>> Signed-off by: Brad Smith <brad@comstyle.com>
>> ---
>>
>> Changes in v2:
>>      * Fix '==' is not portable syntax.
>>
>>
>> diff --git a/configure b/configure
>> index 508f6a5..6d84885 100755
>> --- a/configure
>> +++ b/configure
>> @@ -1342,6 +1342,10 @@ EOF
>>     if compile_prog "-fPIE -DPIE" "-pie"; then
>>       QEMU_CFLAGS="-fPIE -DPIE $QEMU_CFLAGS"
>>       LDFLAGS="-pie $LDFLAGS"
>> +    if test "$targetos" = OpenBSD; then
>> +      CC_NOPIE="-fno-pie"
>> +      LD_NOPIE="-nopie"
>> +    fi
>>       pie="yes"
>>       if compile_prog "" "-Wl,-z,relro -Wl,-z,now" ; then
>>         LDFLAGS="-Wl,-z,relro -Wl,-z,now $LDFLAGS"
>> @@ -4307,6 +4311,8 @@ if test "$gcov" = "yes" ; then
>>     echo "CONFIG_GCOV=y" >> $config_host_mak
>>     echo "GCOV=$gcov_tool" >> $config_host_mak
>>   fi
>> +echo "CC_NOPIE=$CC_NOPIE" >> $config_host_mak
>> +echo "LD_NOPIE=$LD_NOPIE" >> $config_host_mak
>>
>>   # use included Linux headers
>>   if test "$linux" = "yes" ; then
>> diff --git a/pc-bios/optionrom/Makefile b/pc-bios/optionrom/Makefile
>> index 57d8bd0..0b35000 100644
>> --- a/pc-bios/optionrom/Makefile
>> +++ b/pc-bios/optionrom/Makefile
>> @@ -12,6 +12,7 @@ $(call set-vpath, $(SRC_PATH)/pc-bios/optionrom)
>>   CFLAGS := -Wall -Wstrict-prototypes -Werror -fomit-frame-pointer -fno-builtin
>>   CFLAGS += -I$(SRC_PATH)
>>   CFLAGS += $(call cc-option, $(CFLAGS), -fno-stack-protector)
>> +CFLAGS += $(CC_NOPIE)
>
> Would it be possible to add -fno-pie unconditionally here ...
>
>
>>   QEMU_CFLAGS = $(CFLAGS)
>>
>>   build-all: multiboot.bin linuxboot.bin kvmvapic.bin
>> @@ -20,7 +21,7 @@ build-all: multiboot.bin linuxboot.bin kvmvapic.bin
>>   .SECONDARY:
>>
>>   %.img: %.o
>> -	$(call quiet-command,$(LD) -Ttext 0 -e _start -s -o $@ $<,"  Building $(TARGET_DIR)$@")
>> +	$(call quiet-command,$(LD) $(LD_NOPIE) -Ttext 0 -e _start -s -o $@ $<,"  Building $(TARGET_DIR)$@")
>>
>
>
> ... and use -nopie here? I tried it in my Linux build environment, and
> it seems to work.
>
> Then no changes to file configure are needed.

The linker flag definitely does not exist everywhere so that would
break the build on other OS/toolchain combinations; for example stock
binutils does not have this flag. I would not have bothered going this
route if I didn't see having the flags hard coded as causing a problem.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

  reply	other threads:[~2013-12-10  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  1:26 [Qemu-devel] [PATCH v2] Fix QEMU build on OpenBSD on x86 archs Brad Smith
2013-12-10  7:07 ` Stefan Weil
2013-12-10  7:48   ` Brad Smith [this message]
2013-12-10 18:42     ` Stefan Weil
2013-12-10 18:44       ` Stefan Weil
2013-12-10 21:32         ` Brad Smith
2013-12-11  0:41         ` Brad Smith

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=52A6C733.2030608@comstyle.com \
    --to=brad@comstyle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).