Hi,
I'm trying to build the ppc64le branch of OpenBLAS on EPEL7. But, I get the following error message in the setup phase:
DEBUG util.py:393: Error: No Package found for /usr/bin/execstack
Why would this binary not exist on ppc64le?
I'm trying to build the ppc64le branch of OpenBLAS on EPEL7. But, I get the following error message in the setup phase:
DEBUG util.py:393: Error: No Package found for /usr/bin/execstack
Why would this binary not exist on ppc64le?
Because originally it was part of prelink, which was never supported on aarch64/ppc64le, in RHEL it's shipped as part of that package, it was dropped in F-23 and the useful execstack binary was split out into it's own package. It shouldn't be built in EPEL as it'll conflict with core RHEL packages.
Peter
On 12/23/2015 10:57 PM, Peter Robinson wrote:
I'm trying to build the ppc64le branch of OpenBLAS on EPEL7. But, I get the following error message in the setup phase:
DEBUG util.py:393: Error: No Package found for /usr/bin/execstack
Why would this binary not exist on ppc64le?
Because originally it was part of prelink, which was never supported on aarch64/ppc64le, in RHEL it's shipped as part of that package, it was dropped in F-23 and the useful execstack binary was split out into it's own package. It shouldn't be built in EPEL as it'll conflict with core RHEL packages.
Peter
But perhaps we could do https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
add ppc64le to the list of ExclusiveArch, and only ship execstack? See http://koji.fedoraproject.org/koji/taskinfo?taskID=12421692
Or perhaps we could just go ahead an ship execstack with a Conflicts: prelink. Not sure it's that big of a deal.
On 01/05/2016 10:36 AM, Orion Poplawski wrote:
On 12/23/2015 10:57 PM, Peter Robinson wrote:
I'm trying to build the ppc64le branch of OpenBLAS on EPEL7. But, I get the following error message in the setup phase:
DEBUG util.py:393: Error: No Package found for /usr/bin/execstack
Why would this binary not exist on ppc64le?
Because originally it was part of prelink, which was never supported on aarch64/ppc64le, in RHEL it's shipped as part of that package, it was dropped in F-23 and the useful execstack binary was split out into it's own package. It shouldn't be built in EPEL as it'll conflict with core RHEL packages.
Peter
But perhaps we could do https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
add ppc64le to the list of ExclusiveArch, and only ship execstack? See http://koji.fedoraproject.org/koji/taskinfo?taskID=12421692
Or perhaps we could just go ahead an ship execstack with a Conflicts: prelink. Not sure it's that big of a deal.
Perhaps even ExclusiveArch the EPEL7 execstack package?
epel-devel@lists.fedoraproject.org
-
Orion Poplawski -
Peter Robinson -
Susi Lehtola