All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] gio-module-cache.bbclass: disable update_gio_module_cache postinst script for nativesdk
Date: Fri, 20 Jul 2018 11:11:04 +0200	[thread overview]
Message-ID: <CA+chaQe0U+-KTqnMe015uKuF5ExFY4qq0Brbnx7thOzNLoFvSA@mail.gmail.com> (raw)
In-Reply-To: <580eec70-ffc4-fa12-b52d-28717c0c21a5@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

I've tried to remove this from my sumo build and noticed that it's still
failing, the log shows:

NOTE: Running intercept scripts:
NOTE: > Executing update_gio_module_cache-nativesdk intercept ...
WARNING: The postinstall intercept hook 'update_gio_module_cache-nativesdk'
failed, details in my-sdk/1.0.0-1-r3/temp/log.do_populate_sdk
NOTE: Exit code 255. Output:
my-sdk/1.0.0-1-r3/sdk/image/opt/webos-sdk-x86_64/7.0~s14/sysroots/x86_64-webossdk-linux/usr/libexec/nativesdk-gio-querymodules:
Invalid ELF image for this architecture

unfortunately the workdir is again gone already, I'll check if it happens
with latest master as well and will try to keep the workdir if rm_work
isn't faster than me.

Cheers,

On Tue, Mar 20, 2018 at 7:02 PM Alexander Kanavin <
alexander.kanavin@linux.intel.com> wrote:

> On 03/20/2018 06:07 PM, Burton, Ross wrote:
> > Can you file a bug for this? Probably best to fix instead of working
> > around, as this leaves gio modules broken.
>
> I also wonder if the shadow recipe's postinst needs to be fixed properly
> (instead of removing it altogether for nativesdk). On the other hand
> these two have been broken for a long time, and no one noticed, so maybe
> they don't need working nativesdk postinst at all.
>
> Alex
>

[-- Attachment #2: Type: text/html, Size: 1867 bytes --]

  reply	other threads:[~2018-07-20  9:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 11:27 [PATCH] ca-certificates: run postinst script only for -target package Alexander Kanavin
2018-03-19 15:32 ` Martin Jansa
2018-03-19 16:31   ` Alexander Kanavin
2018-03-20 12:10     ` [PATCH 1/2] gio-module-cache.bbclass: disable update_gio_module_cache postinst script for nativesdk Martin Jansa
2018-03-20 12:10       ` [PATCH 2/2] shadow.inc: run postinst only for target Martin Jansa
2018-03-20 16:07       ` [PATCH 1/2] gio-module-cache.bbclass: disable update_gio_module_cache postinst script for nativesdk Burton, Ross
2018-03-20 17:55         ` Alexander Kanavin
2018-07-20  9:11           ` Martin Jansa [this message]
2018-07-20 16:03             ` [sumo][PATCH] " Martin Jansa
2018-07-20 16:07               ` Alexander Kanavin

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=CA+chaQe0U+-KTqnMe015uKuF5ExFY4qq0Brbnx7thOzNLoFvSA@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 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.