Bug 592516 - boost missing TEXTREL allocations for multiple libs - missing -fPIC on s390
Summary: boost missing TEXTREL allocations for multiple libs - missing -fPIC on s390
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: boost
Version: 6.0
Hardware: s390
OS: Linux
Target Milestone: rc
: ---
Assignee: Petr Machata
QA Contact: Michal Nowak
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-15 04:08 UTC by Miroslav Vadkerti
Modified: 2015-05-05 01:35 UTC (History)
4 users (show)

Fixed In Version: boost-1.41.0-11.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-07-02 18:53:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Miroslav Vadkerti 2010-05-15 04:08:47 UTC
Description of problem:
Please see RPMdiff run


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run rpmdiff adhoc analysis for boost
Actual results:
Execshield test fails

Expected results:
Execshield test passes

Additional info:

Comment 2 RHEL Program Management 2010-05-15 04:25:10 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 3 Petr Machata 2010-05-19 16:47:01 UTC
Looking at the libboost_graph_parallel-mt.so.5 case in logs.  In s390x, it uses libmpich.so and no text relocations are reported.  In s390, there's libmpich.a instead of libmpich.so, and text relocations are reported.

Looking at build log of mpich2 of the version that boost used:
  - add -fPIC for s390, to close

I'll simply try to rebuild, might help...

Comment 6 Miroslav Vadkerti 2010-06-07 12:18:28 UTC
Michal, you can see latest rpmdiff results:


Comment 8 releng-rhel@redhat.com 2010-07-02 18:53:47 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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