Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1548687

Summary:	llvm: Partial injection of Fedora build flags
Product:	[Fedora] Fedora	Reporter:	Florian Weimer <fweimer>
Component:	llvm	Assignee:	Tom Stellard <tstellar>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ajax, davejohansen, dmalcolm, jakub, jistone, petersen, scottt.tw, siddharth.kde, tschelle, tstellar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-05 14:39:33 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:	1539083

Description Florian Weimer 2018-02-24 12:02:54 UTC

/usr/lib64/libLLVM-6.0.so and /usr/lib64/libLTO.so.6.0.0 in llvm-libs-6.0.0-0.3.rc1.fc28.x86_64 have not been linked with the standard Fedora linker flags (LDFLAGS) from redhat-rpm-config.

In particular, the BIND_NOW feature is missing, as can be seen from the readelf -d output:

 0x000000006ffffffb (FLAGS_1)            Flags: NODELETE

There should be a NOW flag.

See https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/master/f/buildflags.md for information on RPM macros and environment variables provided by the build environment.

Comment 1 Tom Stellard 2018-03-22 23:59:11 UTC

This was fixed in rawhide by llvm-6.0.0-5.fc29.

Comment 2 Igor Gnatenko 2018-03-26 08:43:55 UTC

(In reply to Tom Stellard from comment #1)
> This was fixed in rawhide by llvm-6.0.0-5.fc29.

Can you get fix into F28 as well?

Comment 3 Tom Stellard 2018-03-26 14:40:14 UTC

(In reply to Igor Gnatenko from comment #2)
> (In reply to Tom Stellard from comment #1)
> > This was fixed in rawhide by llvm-6.0.0-5.fc29.
> 
> Can you get fix into F28 as well?

Yes, I working on it.

Comment 4 Fedora Update System 2018-04-02 14:22:02 UTC

pocl-1.1-2.fc28 lldb-6.0.0-3.fc28 clang-6.0.0-5.fc28 llvm-6.0.0-11.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319

Comment 5 Fedora Update System 2018-04-03 15:57:29 UTC

clang-6.0.0-5.fc28, lldb-6.0.0-3.fc28, llvm-6.0.0-11.fc28, mesa-18.0.0-2.fc28.1, pocl-1.1-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319

Comment 6 Fedora Update System 2018-04-03 23:25:53 UTC

clang-6.0.0-5.fc28 lldb-6.0.0-3.fc28 llvm-6.0.0-11.fc28 mesa-18.0.0-3.fc28 pocl-1.1-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319

Comment 7 Fedora Update System 2018-04-04 18:35:28 UTC

clang-6.0.0-5.fc28, lldb-6.0.0-3.fc28, llvm-6.0.0-11.fc28, mesa-18.0.0-3.fc28, pocl-1.1-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-02c4091319

Comment 8 Fedora Update System 2018-04-05 11:48:07 UTC

clang-6.0.0-5.fc28, lldb-6.0.0-3.fc28, llvm-6.0.0-11.fc28, mesa-18.0.0-3.fc28, pocl-1.1-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.