Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] libdrm: buildroot patchstack - static linking
Date: Thu, 5 Dec 2019 22:11:51 +0100	[thread overview]
Message-ID: <20191205221151.214db463@windsurf> (raw)
In-Reply-To: <20191205215234.7058f6df@gmx.net>

On Thu, 5 Dec 2019 21:54:53 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> some progress on up-streaming the buildroot libdrm patch stack:
> 
>  - 0001-Add-ARM-support-into-xf86drm.h.patch
>    https://gitlab.freedesktop.org/mesa/drm/merge_requests/31
>    Acked, but with one further question 'why not catch-all __ARM_ARCH?'
>    Thomas - you touched the patch and added the comment, any further input?

Well, my comment explains it all: ldrex/strex only exist on ARM >= v6,
but __ARM_ARCH is true for all ARM ISAs, including ARMv4 and ARMv5,
which Buildroot supports, but don't provide ldrex/strex.

>  - 0004-meson.build-enable-static-build.patch
>    declined https://gitlab.freedesktop.org/mesa/drm/merge_requests/28
>    'Closing the MR, but feel free to reopen if it turns out someone has
>    a real need for this'
> 
>    Anyone out there using libdrm static linking?

But what is the cost for upstream to use the correct library() Meson
macro/function instead of shared_library() ? It is shorter, and does
the job. I'm not sure why upstream is reluctant to merge this.

>  - 0005-tests-meson.build-disable-nouveau-tests-for-static-b.patch
>    folded into previous one https://gitlab.freedesktop.org/mesa/drm/merge_requests/27
>    and declined

So, they basically say they don't want to support static linking at all?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-12-05 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 20:54 [Buildroot] libdrm: buildroot patchstack - static linking Peter Seiderer
2019-12-05 21:11 ` Thomas Petazzoni [this message]
2019-12-05 21:25   ` Peter Seiderer

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=20191205221151.214db463@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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