Bug 861452

Summary:	webkitgtk-1.10.0-1 not built with $RPM_OPT_FLAGS
Product:	[Fedora] Fedora	Reporter:	Ville Skyttä <ville.skytta>
Component:	webkitgtk	Assignee:	Kevin Fenzi <kevin>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	huzaifas, kalevlember, kevin, martin.sourada, mtasaka, rdieter
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-03 18:24:04 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:	496968

Description Ville Skyttä 2012-09-28 16:07:05 UTC

webkitgtk-1.10.0-1 is not built with $RPM_OPT_FLAGS:

http://kojipkgs.fedoraproject.org//packages/webkitgtk/1.10.0/1.fc19/data/logs/x86_64/build.log

1.8.3-1 did not have this problem.

Comment 1 Kevin Fenzi 2012-09-28 16:22:37 UTC

Thats because it won't build with the default RPM_OPT_FLAGS. ;) 

It creates a >4GB ar archive that ar barfs on. 

From the comment in the spec: 

# Build with -g1 on all platforms to avoid running into 4 GB ar format limit
# https://bugs.webkit.org/show_bug.cgi?id=91154
%global optflags %(echo %{optflags} | sed 's/-g /-g1 /')

So, not sure what else we can do here until upstream splits things up more.

Comment 2 Kalev Lember 2012-12-10 23:52:34 UTC

The issue with 4 GB ar archives is now fixed upstream in webkitgtk 1.10.2 by splitting the library up into smaller chunks.

But now the builds with full -g are running into another issue: in koji, during the final ld linking step the linker gets killed by the OOM killer. So unfortunately, Fedora webkitgtk / webkitgtk3 1.10.2-1 buids are still done with -g1.

Comment 3 Kevin Fenzi 2013-02-03 03:41:32 UTC

With the recent rearrangment of the builders to have more memory this no longer seems to be the problem. I am going to revert this now. ;) 

Kalev: Would you like to do this for webkitgtk3? or would you like me to?

Comment 4 Kalev Lember 2013-02-03 12:19:27 UTC

Awesome. Sure, please go ahead with webkitgtk3 as well.

Comment 5 Kevin Fenzi 2013-02-03 18:24:04 UTC

Sadly, webkitgtk3 still fails. ;( 

/usr/bin/ld: failed to set dynamic section sizes: Memory exhausted
collect2: error: ld returned 1 exit status

So, I guess we keep it in webkitgtk3 for now... when webkitgtk moves to the newer version it may also have to do this. ;( 

Hopefully a better solution can be found upstream.