Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Jose Quaresma <quaresma.jose@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v4 4/4] shaderc: fix the build with glslang 11.1.0
Date: Thu, 28 Jan 2021 22:44:43 +0000	[thread overview]
Message-ID: <4af03c39ce342ee647d8932bb1ac4f2f4cf6c2fc.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210128223834.GA2544418@piout.net>

On Thu, 2021-01-28 at 23:38 +0100, Alexandre Belloni wrote:
> Hello Jose,
> 
> On 24/01/2021 18:07:58+0000, Jose Quaresma wrote:
> > Drop patches:
> >     * 0001-Fix-the-link-order-of-libglslang-and-libHLSL.patch
> >       is rejected upstream and is not need when glslang as shared libs.
> > 
> > Update pacthes:
> >     * 0001-cmake-de-vendor-libs-and-disable-git-versioning.patch
> >       renamed and refreshed from 0003-cmake-de-vendor-libs-and-disable-git-versioning.patch.
> > 
> 
> It seems there is still a linking issue when building shaderc-native.
> The full log is available here:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/2978/steps/11/logs/stdio

I have a suspicion this happens on Ubuntu 18.04 systems since I've seen
issues like this locally with 18.04's binutils version and OE generated
vulkan-samples binaries, I think Joshua Watt reported the same issue
too with 18.04.

Not sure what we can do about it, can we disable the debug symbol types
causing problems in that -native recipe?

Cheers,

Richard


  reply	other threads:[~2021-01-28 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 18:07 [PATCH v4 1/4] glslang: upgrade 8.13.3743 -> 11.1.0 Jose Quaresma
2021-01-24 18:07 ` [PATCH v4 2/4] glslang: enable shared libs Jose Quaresma
2021-01-24 18:07 ` [PATCH v4 3/4] shaderc: avoid reproducible issues Jose Quaresma
2021-01-24 18:07 ` [PATCH v4 4/4] shaderc: fix the build with glslang 11.1.0 Jose Quaresma
2021-01-28 22:38   ` Alexandre Belloni
2021-01-28 22:44     ` Richard Purdie [this message]
     [not found]     ` <165E86C2AF927994.17182@lists.openembedded.org>
2021-01-29 11:42       ` [OE-core] " Richard Purdie
     [not found]       ` <165EB138E76788A6.12832@lists.openembedded.org>
2021-01-29 14:24         ` Richard Purdie
2021-01-29 22:14           ` Jose Quaresma

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=4af03c39ce342ee647d8932bb1ac4f2f4cf6c2fc.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quaresma.jose@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox