qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Build *-user targets as PIE
Date: Wed, 02 Sep 2009 18:03:17 +0200	[thread overview]
Message-ID: <87ljkxibay.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <cc557aab0909020852t284c19cdsb9131f693512e91f@mail.gmail.com> (Kirill A. Shutemov's message of "Wed\, 2 Sep 2009 18\:52\:26 +0300")

"Kirill A. Shutemov" <kirill@shutemov.name> writes:

> On Wed, Sep 2, 2009 at 6:46 PM, Arnaud Patard<arnaud.patard@rtp-net.org> wrote:
>> "Kirill A. Shutemov" <kirill@shutemov.name> writes:
>>
>> Hi,
>>
>> [...]
>>
>>> diff --git a/configure b/configure
>>> index 0d0162a..b501526 100755
>>> --- a/configure
>>> +++ b/configure
>>> @@ -2302,6 +2302,11 @@ if test "$target_softmmu" = "yes" ; then
>>>    esac
>>>  fi
>>>
>>> +if test "$target_user_only" = "yes" -a "$static" = "no" ; then
>>> +  cflags="-fpie $cflags"
>>> +  ldflags="-pie $ldflags"
>>> +fi
>>> +
>>
>> Please do that on per-arch basis. For instance, pie support tends to
>> be broken quite often on mips (afaik, it's currently broken on debian
>> unstable). I know qemu doesn't support mips host but it doesn't mean it
>> will never be supported - I need to find time to update to current git
>> and fix remaining bugs in my code before sending it for merge.
>> Unfortunately, this kind of patch will make sure it won't happen soon :(
>>
>>
>> Thanks,
>> Arnaud
>>
>
> Will you happy if I provide option like --disable-user-pie to configure?

yes, it's fine as I hope that pie support will be fixed.

>
> P.S. Sorry I forgot to put qemu-devil into CC.

qemu-_devil_ ? :)


Arnaud

  reply	other threads:[~2009-09-02 15:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 15:21 [Qemu-devel] [PATCH 1/2] Do not link *-user target with libhw*.a Kirill A. Shutemov
2009-09-02 15:21 ` [Qemu-devel] [PATCH 2/2] Build *-user targets as PIE Kirill A. Shutemov
2009-09-02 14:24   ` [Qemu-devel] " Paolo Bonzini
2009-09-02 14:35     ` Kirill A. Shutemov
2009-09-02 15:46   ` [Qemu-devel] " Arnaud Patard
2009-09-02 15:52     ` Kirill A. Shutemov
2009-09-02 16:03       ` Arnaud Patard [this message]
2009-09-03 12:15         ` [Qemu-devel] [PATCH v2] " Kirill A. Shutemov
2009-09-03 12:00           ` Reimar Döffinger
2009-09-03 14:21             ` Kirill A. Shutemov
2009-09-03 14:38               ` Paul Brook
2009-09-03 14:52                 ` [Qemu-devel] " Paolo Bonzini
2009-09-03 15:07                 ` [Qemu-devel] " Kirill A. Shutemov
2009-09-03 17:17                   ` Reimar Döffinger
2009-09-04  4:33                     ` Kirill A. Shutemov
2009-09-04  7:51                       ` Reimar Döffinger
2009-09-04  8:03                         ` Kirill A. Shutemov
     [not found]           ` <m3ws4g9qqe.fsf@neno.mitica>
2009-09-03 12:51             ` [Qemu-devel] " Kirill A. Shutemov
2009-09-03 14:39           ` [Qemu-devel] " Paul Brook
2009-09-03 15:08             ` Kirill A. Shutemov
2009-09-02 18:54   ` [Qemu-devel] [PATCH 2/2] " Riku Voipio
     [not found]   ` <m3iqg1ckts.fsf@neno.mitica>
2009-09-02 18:59     ` [Qemu-devel] " Kirill A. Shutemov

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=87ljkxibay.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=kirill@shutemov.name \
    --cc=qemu-devel@nongnu.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).