All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v6] mesa: Upgrade to 19.2.1
Date: Tue, 12 Nov 2019 17:31:29 +0200	[thread overview]
Message-ID: <20191112153129.GB14540@localhost> (raw)
In-Reply-To: <CAMKF1srMzPL4pBAQYscX6fxPPL2SExcYFw+Ti2B656nK3hyH0g@mail.gmail.com>

On Fri, Nov 08, 2019 at 10:13:07AM -0800, Khem Raj wrote:
> On Fri, Nov 8, 2019 at 2:32 AM Ross Burton <ross.burton@intel.com> wrote:
> > On 04/11/2019 22:48, Alistair Francis wrote:
> > > From: Alistair Francis <alistair@alistair23.me>
> > >
> > > Upgrade mesa and mesa-gl to 19.2.1.
> > >
> > > The license hash change was a trivial new line removal.
> > >
> > > The glx-tls option was removed as it isn't included in the meson.build
> > > file. It has been replaced with 'use-elf-tls' instead.
> >
> > I think this has regressed something, this is a new warning on musl builds:
> >
> > do_package_qa: QA Issue: ELF binary
> > '[...]libgles2-mesa/usr/lib/libGLESv2.so.2.0.0' has relocations in .text
> > [textrel]
> >
> > (ditto for libGLESv1_CM.so.1.1.0 libGL.so.1.2.0 libglapi.so.0.0.0)
> 
> right this means glx-tls is not working anymore, and it will fail on
> musl at runtime
> see
> https://gitlab.freedesktop.org/mesa/mesa/issues/966

glx-tls is already PACKAGECONFIG_remove_libc-musl.

That this is no longer sufficient is the regression Ross mentioned.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      parent reply	other threads:[~2019-11-12 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 22:48 [PATCH v6] mesa: Upgrade to 19.2.1 Alistair Francis
2019-11-08 10:31 ` Ross Burton
2019-11-08 18:13   ` Khem Raj
2019-11-08 23:01     ` Alistair Francis
2019-11-09 15:36       ` Alexander Kanavin
2019-11-12 16:19         ` Khem Raj
2019-11-12 18:01           ` Alistair Francis
2019-11-12 18:15             ` Khem Raj
2019-11-12 18:28               ` Alexander Kanavin
2019-11-12 15:31     ` Adrian Bunk [this message]

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=20191112153129.GB14540@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=raj.khem@gmail.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.