Bug 826745

Summary:	Undefined non-weak symbols
Product:	Red Hat Enterprise Linux 6	Reporter:	David Kovalsky <dkovalsk>
Component:	libreport	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED ERRATA	QA Contact:	Iveta Wiedermann <isenfeld>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.3	CC:	benl, dkutalek, isenfeld, jmoskovc, mnowak, nobody+abrt-devel-list, npajkovs, rvokal
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	libreport-2.0.9-6.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 07:53:42 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:

Description David Kovalsky 2012-05-30 21:24:16 UTC

`prelink -avMR' shows the following warning:


Prelinking /usr/lib64/libabrt_web.so.0.0.1
prelink: Warning: /usr/lib64/libabrt_web.so.0 has undefined non-weak symbols


libreport-2.0.9-5.el6.x86_64

Comment 1 Nikola Pajkovsky 2012-05-31 12:35:31 UTC

Jiri take that one

commit 27257a32c88c404a5e13521d38742bd5a8a7d955
Author: Nikola Pajkovsky <npajkovs>
Date:   Tue May 15 15:09:32 2012 +0200

    prelink: fix undefined non-weak symbols
    
    Signed-off-by: Nikola Pajkovsky <npajkovs>

Comment 4 Nikola Pajkovsky 2013-01-08 14:42:15 UTC

abrt also needs following patch

commit 6c96fe597fb578f59efc36e39487dbbfc6f9e4b6
Author: Nikola Pajkovsky <npajkovs>
Date:   Tue May 15 13:27:08 2012 +0200

    libabrt: link with libreport
    
    Signed-off-by: Nikola Pajkovsky <npajkovs>

fully resolve prelinks weak-symobls

Comment 6 Jiri Moskovcak 2013-01-24 14:59:21 UTC

Cause
    Wrong linker parameters
Consequence
    Errors when running prelink on the affected libraries
Fix
    Add the proper linker flags
Result
    No errors when running prelink on abrt libreries

Comment 7 errata-xmlrpc 2013-02-21 07:53:42 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.

http://rhn.redhat.com/errata/RHBA-2013-0290.html