Bug 1385475

Summary:	dynamic linking failing for armv7hl executables with ghc-7.10.3
Product:	[Fedora] Fedora	Reporter:	Jens Petersen <petersen>
Component:	ghc	Assignee:	Jens Petersen <petersen>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	bos, haskell-devel, petersen
Target Milestone:	---
Target Release:	---
Hardware:	armv7hl
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-26 07:41:53 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 Jens Petersen 2016-10-17 07:10:13 UTC

Description of problem:
Dynamic linking of for packages with executables is failing on armv7hl
when using ghc-7.10.3 on armv7hl (and aarch64).

eg:
Linking dist/build/xmobar/xmobar ...
/usr/lib/ghc-7.10.3/scien_3vmCXiZeJinKZBcLawS8i0/libHSscientific-0.3.4.7-3vmCXiZeJinKZBcLawS8i0-ghc7.10.3.so: error: undefined reference to 'log'
collect2: error: ld returned 1 exit status

How reproducible:
100%

Steps to Reproduce:
1. build packages with dynlinked executable

Actual results:
fails with "undefined reference to 'log'" etc.

Expected results:
dynlinking to work

Additional info:
This worked earlier though, eg in beginning of August 2016:
http://koji.fedoraproject.org/koji/buildinfo?buildID=787831

Comment 1 Jens Petersen 2016-10-17 07:18:29 UTC

As a workaround for now I have disabled exe dynlinking in ghc-rpm-macros.

Comment 2 Jens Petersen 2016-10-17 07:19:18 UTC

ghc-rpm-macros-1.6.9-8.fc26

Comment 3 Fedora End Of Life 2017-02-28 10:27:13 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 4 Jens Petersen 2017-04-26 07:45:29 UTC


*** This bug has been marked as a duplicate of bug 1386126 ***