public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Yi Zhao <yi.zhao@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>, antonin.godard@bootlin.com
Cc: openembedded-core@lists.openembedded.org, liuyd.fnst@fujitsu.com
Subject: Re: [OE-core] [PATCH 1/2 v2] blueprint-compiler: add recipe
Date: Mon, 19 Jan 2026 21:15:37 +0800	[thread overview]
Message-ID: <4a276d8b-aedc-4925-8246-a5b09a0a8b59@windriver.com> (raw)
In-Reply-To: <CANNYZj_bBj+btrm79ZJ9wsdCFSX-8K_ns8hhz5D3jz9YRLv0uQ@mail.gmail.com>


On 1/19/26 20:56, Alexander Kanavin wrote:
> On Mon, 19 Jan 2026 at 09:44, Antonin Godard via
> lists.openembedded.org
> <antonin.godard=bootlin.com@lists.openembedded.org> wrote:
>> This failed to build:
>>
>> ERROR: blueprint-compiler-0.18.0-r0 do_package: QA Issue: blueprint-compiler: Files/directories were installed but not shipped in any package:
>>    /usr/lib
>>    /usr/lib/python3.14
>>    /usr/lib/python3.14/site-packages
>>    /usr/lib/python3.14/site-packages/blueprintcompiler
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/formatter.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/decompiler.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/interactive_port.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/__init__.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/errors.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/gir.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/main.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/ast_utils.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/utils.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/reference_docs.json
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/completions_utils.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/parse_tree.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/tokenizer.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/typelib.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/lsp_utils.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/parser.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/completions.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/xml_reader.py
>>    /usr/lib/python3.14/site-packages/blueprintcompiler/lsp.py
>>
>> Log: https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/4986196/raw_inline
>> Parent build: https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/2884
>>
>> It only seemed to happen with the qemux86-64 builds.
>>
>> Can you have a look?
> I suspect the issue is in multilib setups, e.g. upstream is hardcoding
> '/usr/lib/' prefix instead of $libdir.


Yes, I think so too. I'll take a look.


//Yi


>
> Alex


      reply	other threads:[~2026-01-19 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  9:01 [PATCH 1/2 v2] blueprint-compiler: add recipe Yi Zhao
2026-01-16  9:01 ` [PATCH 2/2 v2] epiphany: upgrade 48.5 -> 49.2 Yi Zhao
2026-01-19  8:44 ` [OE-core] [PATCH 1/2 v2] blueprint-compiler: add recipe Antonin Godard
2026-01-19 12:56   ` Alexander Kanavin
2026-01-19 13:15     ` Yi Zhao [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=4a276d8b-aedc-4925-8246-a5b09a0a8b59@windriver.com \
    --to=yi.zhao@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=antonin.godard@bootlin.com \
    --cc=liuyd.fnst@fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox