Bug 834652 - Replace ppc64 with %{power64} macro in openssl spec
Summary: Replace ppc64 with %{power64} macro in openssl spec
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: openssl
Version: 17
Hardware: ppc64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: f18-ppc64p7
TreeView+ depends on / blocked
 
Reported: 2012-06-22 16:48 UTC by Brent Baude
Modified: 2012-07-13 07:47 UTC (History)
3 users (show)

Fixed In Version: openssl-1.0.1c-3.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-13 07:47:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brent Baude 2012-06-22 16:48:09 UTC
Description of problem:
RPM (as of 4.9.1.3-6.fc17) now honors a %{power64} macro that leads to additional subarchitectures coming in F18.  For Fedora 17, please update the sendmail spec to facilitate testing of the package.  In addition to using the macro, we also add a suggestion for definning 'sslarch', similar to arm. A patch will be provided.


--- a/openssl.spec
+++ b/openssl.spec
@@ -16,7 +16,7 @@
 
 # Arches on which we need to prevent arch conflicts on opensslconf.h, must
 # also be handled in opensslconf-new.h.
-%define multilib_arches %{ix86} ia64 ppc ppc64 s390 s390x sparcv9 sparc64 x86_64
+%define multilib_arches %{ix86} ia64 ppc %{power64} s390 s390x sparcv9 sparc64 x86_64
 
 Summary: A general purpose cryptography library with TLS implementation
 Name: openssl
@@ -213,7 +213,11 @@ sslarch="linux-s390x"
 %ifarch %{arm} sh3 sh4
 sslarch=linux-generic32
 %endif
-# ia64, x86_64, ppc, ppc64 are OK by default
+%ifarch %{power64}
+sslarch=linux-ppc64
+%endif
+
+# ia64, x86_64, and ppc are OK by default
 # Configure the build tree.  Override OpenSSL defaults with known-good defaults
 # usable on all platforms.  The Configure script already knows to use -fPIC and
 # RPM_OPT_FLAGS, so we can skip specifiying them here.


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