All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Dimitry Andric" <dim@FreeBSD.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Laurent Vivier" <laurent@vivier.eu>,
	qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] qemu-user: fix build with LLVM lld 10
Date: Fri, 27 Mar 2020 15:44:47 +0000	[thread overview]
Message-ID: <878sjln6og.fsf@linaro.org> (raw)
In-Reply-To: <20200327140839.GB28583@Air-de-Roger>


Roger Pau Monné <roger.pau@citrix.com> writes:

> On Fri, Mar 27, 2020 at 11:28:04AM +0000, Alex Bennée wrote:
>> 
>> Roger Pau Monné <roger.pau@citrix.com> writes:
>> 
>> > On Thu, Mar 26, 2020 at 09:56:38AM -0700, Richard Henderson wrote:
>> >> On 3/26/20 6:43 AM, Roger Pau Monne wrote:
>> >> > lld 10.0.0 introduced a new linker option --image-base equivalent to
>> >> > the GNU -Ttext-segment one, hence use it when available.
>> >> > 
>> >> > This fixes the build of QEMU on systems using lld 10 or greater.
>> >> > 
>> >> > Signed-off-by: Dimitry Andric <dim@FreeBSD.org>
>> >> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>> >> > ---
>> >> > Cc: Laurent Vivier <laurent@vivier.eu>
>> >> > Cc: Richard Henderson <richard.henderson@linaro.org>
>> >> > Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>
>> >> > Cc: Paolo Bonzini <pbonzini@redhat.com>
>> >> > Cc: "Daniel P. Berrangé" <berrange@redhat.com>
>> >> > ---
>> >> 
>> >> The Plan is still to drop this whole section of code.
>> >> 
>> >> However, it's still blocked on getting the x86_64 vsyscall patches upstream.
>> >
>> > While this doesn't materialize, could it be possible to get this patch
>> > accepted?
>> >
>> > This is currently blocking the build of QEMU on FreeBSD HEAD, which
>> > has already switched to LLVM 10.0.0.
>> 
>> I think the vsyscall patch has just been merged, however way I don't
>> think targeting HEAD of a OS release during the rc phase is appropriate.
>
> I'm not sure I understand what you mean. If QEMU doesn't build on
> FreeBSD HEAD it won't build on the next release. Also the LLVM
> toolchain used is not a development version AFAIK, but the actual
> 10.0.0 release, which QEMU should aim to support?

QEMU's supported build platforms are based on what is currently shipping
as stable versions:

  https://www.qemu.org/docs/master/system/build-platforms.html

> Can this be applied to stable branches then please if QEMU master
> doesn't have that chunk in configure anymore?

Usually platforms released after a given QEMU release will just carry
their own patches in the local packaging. When is the current HEAD due
to be cut as the next release? The schedule for QEMU's release is
documented on out planning pages:

  https://wiki.qemu.org/Planning/5.0

> FWIW, I've just looked at configure from git master branch and it
> still has that exact same linker detection chunk that this patch is
> trying to fix.

Now the vsyscalls patch is in this can be cleaned up I think. Richard?

-- 
Alex Bennée


  reply	other threads:[~2020-03-27 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 13:43 [PATCH] qemu-user: fix build with LLVM lld 10 Roger Pau Monne
2020-03-26 16:56 ` Richard Henderson
2020-03-27 10:16   ` Roger Pau Monné
2020-03-27 11:28     ` Alex Bennée
2020-03-27 14:08       ` Roger Pau Monné
2020-03-27 15:44         ` Alex Bennée [this message]
2020-03-27 15:48           ` Daniel P. Berrangé
2020-03-27 15:57             ` Alex Bennée
2020-03-27 10:51   ` Laurent Vivier
2020-03-27 23:00     ` Richard Henderson

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=878sjln6og.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=dim@FreeBSD.org \
    --cc=laurent@vivier.eu \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=roger.pau@citrix.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.