2023. 08. 03. 13:15 keltezéssel, Alexander Kanavin írta:
On Thu, 3 Aug 2023 at 12:59, Böszörményi Zoltán 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
On Thu, 3 Aug 2023 at 12:59, Böszörményi Zoltán 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 f
2023. 08. 03. 12:19 keltezéssel, Alexander Kanavin írta:
Ok, sorry for rapid-fire. The more I think about this, the more I'm
convinced the target platform macro needs to go to
platform/--/macros, e.g. include the vendor. That
way we can install into x86_64-poky-linux, and it would neither clash
w
2023. 08. 03. 9:55 keltezéssel, Alexander Kanavin írta:
I applied the patch and checked what the difference in install tree
is. I see that the only difference is addition of
usr/lib/rpm/platform/qemux86_64-linux/macros
I'd like to step back for a bit, and clarify:
What is the mechanism at runti
Ok, sorry for rapid-fire. The more I think about this, the more I'm
convinced the target platform macro needs to go to
platform/--/macros, e.g. include the vendor. That
way we can install into x86_64-poky-linux, and it would neither clash
with upstream macros, nor make rpm recipe machine-specific (
A couple more observations:
the content of usr/lib/rpm/platform/qemux86_64-linux/macros is not at
all specific to qemu. In fact, the only significant difference with
upstream's x86_64-linux/macros is where the libraries go (lib vs
lib64).
So the machine name is needed only for the file location, a
I applied the patch and checked what the difference in install tree
is. I see that the only difference is addition of
usr/lib/rpm/platform/qemux86_64-linux/macros
I'd like to step back for a bit, and clarify:
What is the mechanism at runtime for finding that file? How does rpm
tooling arrive at t
2023. 08. 02. 21:54 keltezéssel, Alexander Kanavin írta:
I think the culprit is the usage of MACHINE_ARCH. You can't have that
in regular recipes, as that makes them machine-specific, rather than
tune (i.e. architecture) specific.
So, how to fix it?
Would putting this into the rpm recipe be en
I think the culprit is the usage of MACHINE_ARCH. You can't have that
in regular recipes, as that makes them machine-specific, rather than
tune (i.e. architecture) specific.
Alex
On Wed, 2 Aug 2023 at 21:28, Böszörményi Zoltán wrote:
>
> Some clues please. What does this error mean? How to solve
Some clues please. What does this error mean? How to solve it?
2023. 08. 02. 15:41 keltezéssel, Alexandre Belloni írta:
Hello,
This causes
sstatetests.SStateHashSameSigs3.test_sstate_sametune_samesigs to fail:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5572/steps/14/logs
Hello,
This causes
sstatetests.SStateHashSameSigs3.test_sstate_sametune_samesigs to fail:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5572/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5538/steps/14/logs/stdio
https://autobuilder.yocto
Feed platform settings to installplatform externally. Based on the patch
submitted under https://github.com/rpm-software-management/rpm/pull/2585
Patch against INSTALL was backported for rpm 4.18.1
Signed-off-by: Zoltán Böszörményi
---
...atform-macro-settings-externally-258.patch | 119 +++
12 matches
Mail list logo
