From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v6] rpm: Allow setting platform macro settings externally
Date: Thu, 3 Aug 2023 14:17:48 +0200 [thread overview]
Message-ID: <0e09aba7-acd0-17ca-abbc-e6e1d5ee924b@gmail.com> (raw)
In-Reply-To: <CANNYZj9sn6UyaQwpXwcywBZJ=+PMvUwsZ5AtVx4eeSVqk9xCiQ@mail.gmail.com>
2023. 08. 03. 13:15 keltezéssel, Alexander Kanavin írta:
> On Thu, 3 Aug 2023 at 12:59, Böszörményi Zoltán <zboszor@gmail.com> wrote:
>> When /etc/rpm/platform exists, its content is read and
>> /usr/lib/rpm/platform/`cat /etc/rpm/platform`/macros will be used
>> for setting up essential macro values, even if this file does not exist.
>> rpmbuild will look no further for other fallback "macros" file, like
>> /usr/lib/rpm/platform/x86_64-linux/macros in my case.
> But /etc/rpm/platform contains:
> qemux86_64-pc-linux
>
> Do you know at which point '-pc' is stripped from the middle?
The cpu-vendor-os triplet with the optional -gnu suffix is deduced here:
https://github.com/rpm-software-management/rpm/blob/rpm-4.18.x/lib/rpmrc.c#L689
Then cpu[-vendor]-os[-gnu] combinations are tried as the platform directory names
but I have not yet found where exactly.
next prev parent reply other threads:[~2023-08-03 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 13:29 [PATCH v6] rpm: Allow setting platform macro settings externally Zoltán Böszörményi
2023-08-02 13:41 ` [OE-core] " Alexandre Belloni
2023-08-02 19:28 ` Böszörményi Zoltán
2023-08-02 19:54 ` Alexander Kanavin
2023-08-03 6:09 ` Böszörményi Zoltán
2023-08-03 7:55 ` Alexander Kanavin
2023-08-03 10:59 ` Böszörményi Zoltán
2023-08-03 11:15 ` Alexander Kanavin
2023-08-03 12:17 ` Böszörményi Zoltán [this message]
[not found] ` <1777D06DC603E04E.27883@lists.openembedded.org>
2023-08-03 8:55 ` Alexander Kanavin
[not found] ` <1777D3B13579ECA3.27883@lists.openembedded.org>
2023-08-03 10:19 ` Alexander Kanavin
2023-08-03 11:13 ` 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=0e09aba7-acd0-17ca-abbc-e6e1d5ee924b@gmail.com \
--to=zboszor@gmail.com \
--cc=alex.kanavin@gmail.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.