Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1266235

Summary: Sample CMPI providers won't build on ppc64le
Product: Red Hat Enterprise Linux 7 Reporter: Alois Mahdal <amahdal>
Component: tog-pegasusAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED ERRATA QA Contact: Alois Mahdal <amahdal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: ppc64le   
OS: Unspecified   
Whiteboard:
Fixed In Version: tog-pegasus-2.14.1-4.el7 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 16:45:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1380364, 1393870, 1400961    
Attachments:
Description Flags
proposed fix none

Description Alois Mahdal 2015-09-24 20:32:16 UTC
Description of problem
======================

Sample CMPI providers shipped with tog-pegasus won't build
on ppc64le.  (Rest of architectures seems OK.)  The error is:

    mak/config.mak:84: *** PEGASUS_PLATFORM environment variable undefined. Please set to one of the following:  LINUX_PPC_E500_GNU   LINUX_ZSERIES_GNU   LINUX_GNU   LINUX_SH4_GNU   LINUX_IX86_GNU   LINUX_X86_64_CLANG   LINUX_IX86_CLANG   LINUX_PPC64_GNU   LINUX_AARCH64_GNU   LINUX_IA64_GNU   LINUX_PPC_GNU   LINUX_ZSERIES64_GNU   LINUX_X86_64_GNU  .  Stop.


Version-Release number of selected component
============================================

tog-pegasus-2.14.1-3.el7.ppc64le


How reproducible
================

Always


Steps to Reproduce
==================

 1. Install pegasus and tog-pegasus-devel
 2. `systemctl start tog-pegasus`
 3. `cd /usr/share/Pegasus/samples`
 4. `make setupSDK`


Actual results
==============

Failure with above error


Expected results
================

Success; no errors.


Additional info
===============

Somehow related is bug 1127399 which is about inability to build these
providers on other architectures.  That has been fixed, but the newly
added ppc64le has not been enabled in the scripts.

Comment 2 Vitezslav Crhonek 2015-10-06 12:26:03 UTC
Created attachment 1080224 [details]
proposed fix

Comment 5 Alois Mahdal 2017-05-03 00:31:12 UTC
Verified manually with tog-pegasus-devel-2.14.1-4.

Build succeeds without error.

Comment 6 errata-xmlrpc 2017-08-01 16:45:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1969