Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] rpmbuild doesn't work on the target system out of the box with standard macros in the specfile
Date: Fri, 14 Jul 2023 15:48:11 +0200	[thread overview]
Message-ID: <ee3e5bff-5067-e798-d2ed-ffbd1e4159c8@gmail.com> (raw)
In-Reply-To: <98E1AB5A-E531-457D-97B5-CFFD1C4A1103@arm.com>

2023. 07. 14. 15:23 keltezéssel, Ross Burton írta:
> On 14 Jul 2023, at 13:53, Zoltan Boszormenyi via lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org> wrote:
>> It would be nice if Yocto's rpm recipe added the possible
>> buildarchtranslate lines for BSP target archs automatically.
> As you’re in the perfect position to test this, would you be willing to come up with a patch?

I am trying to.
Currently I am stuck with making this work for Yocto 3.4.
Later I may be able to come up with something that works for Yocto master.

> It might be as simple as only changing the macro files in native builds, so the target rpm has conventional macros.  Then again I don’t know much about RPM so may be wrong!

rpmrc and the platform specific macros file need changing.

rpm --eval '%{_arch}' also not correct. strace shows that
it looks at the contents of /etc/rpm/platform and then
wants to read /usr/lib/rpm/platform/<platform>/macros
which doesn't exist for e.g. platform=genericx86-64 or
other BSPs.

Also, I am not using multiarch so the default
/usr/lib/rpm/platform/x86_64-linux/macros is not correct
as it tells rpmbuild to use /usr/lib64 as opposed to use /usr/lib.

Not sure what to do with a multiarch Yocto build.

> A test case that does a simple build using rpm would be a good step too.
>
> Cheers,
> Ross



  reply	other threads:[~2023-07-14 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 12:53 rpmbuild doesn't work on the target system out of the box with standard macros in the specfile Böszörményi Zoltán
2023-07-14 13:23 ` [OE-core] " Ross Burton
2023-07-14 13:48   ` Böszörményi Zoltán [this message]
     [not found]   ` <1771C00C48FCDC1F.28005@lists.openembedded.org>
2023-07-24 12:40     ` Böszörményi Zoltán

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=ee3e5bff-5067-e798-d2ed-ffbd1e4159c8@gmail.com \
    --to=zboszor@gmail.com \
    --cc=Ross.Burton@arm.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