Bug 1919148 - No platform macros for armhfp: xargs: invalid number "%{_smp_build_ncpus}" for -P option
Summary: No platform macros for armhfp: xargs: invalid number "%{_smp_build_ncpus}" fo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-22 09:13 UTC by Miro Hrončok
Modified: 2023-04-25 16:59 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-04-25 16:59:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2021-01-22 09:13:38 UTC
Description of problem:
When building for the armhfp architecture, some macros are undefined.
This manifests e.g. via:

    xargs: invalid number "%{_smp_build_ncpus}" for -P option

I think it is because /usr/lib/rpm/platform/armhfp-linux is not there and/or there is a missing alias.

Version-Release number of selected component (if applicable): 4.16.1.2-1.fc33, 4.16.1.2-3.fc34


Steps to Reproduce:
1. fedpkg clone python3.9 && cd python3.9
2. fedpkg build --nowait --scratch --arches armhfp

Actual results:
Build proceeds, but fails in/near /usr/lib/rpm/redhat/brp-strip-lto with:
xargs: invalid number "%{_smp_build_ncpus}" for -P option

Expected results:
Build succeeds.

Comment 1 Ben Cotton 2021-02-09 15:42:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 2 Ben Cotton 2022-05-12 16:22:02 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-08 00:25:36 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Jordan Sissel 2022-11-06 21:33:29 UTC
I am able to reproduce this on Fedora 36.

Comment 5 Panu Matilainen 2022-11-07 11:36:24 UTC
There seems to be (at least) two bugs here: 

1) We're merrily building for an unknown platform, armhfp is not something rpm knows about. Where did that name come from anyway?
2) Dependency on platform-specific stuff in macros (see https://github.com/rpm-software-management/rpm/pull/2266)

Comment 6 Ben Cotton 2023-04-25 16:41:32 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Miro Hrončok 2023-04-25 16:59:57 UTC
With ARM retirement in F37, I no longer care about this.


Note You need to log in before you can comment on or make changes to this bug.