Bug 1250268

Summary:	boost 1.58 uses wrong CFLAGS on aarch64 and hence is FTBFS
Product:	[Fedora] Fedora	Reporter:	Peter Robinson <pbrobinson>
Component:	boost	Assignee:	Jonathan Wakely <jwakely>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	rawhide	CC:	dakingun, denis.arnaud_fedora, jwakely, me
Target Milestone:	---
Target Release:	---
Hardware:	aarch64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 16:45:50 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:	922257

Description Peter Robinson 2015-08-04 23:12:39 UTC

http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3114086

The key with this error is "unrecognized command line option '-m64'" but that tells me that boost isn't actually using the proper distro CFLAG options because if it was it was it would not fail as the distro flags automatically provide the optimal flags for each architecture

gcc.compile.c++ serial/boost/bin.v2/libs/atomic/build/gcc-5.1.1/release/debug-symbols-on/pch-off/python-2.7/threading-multi/lockpool.o
    "g++"  -g -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fno-strict-aliasing -pthread -fPIC -m64  -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_ATOMIC_SOURCE -DNDEBUG  -I"." -c -o "serial/boost/bin.v2/libs/atomic/build/gcc-5.1.1/release/debug-symbols-on/pch-off/python-2.7/threading-multi/lockpool.o" "libs/atomic/src/lockpool.cpp"
cc1plus: error: unrecognized command line option '-m64'

Comment 1 Jonathan Wakely 2015-08-05 12:38:24 UTC

This should be fixed already in boost-1.58.0-4.fc24, could you try another build please?

Comment 2 Jonathan Wakely 2015-08-05 14:40:50 UTC

The problem is not that boost isn't using the distro CFLAGS, it is using them, but that Boost's own build system adds additional flags to the compiler commands, and for GCC it always adds either -m32 or -m64. The latest versions in f23 and rawhide has a patch to prevent that being added.

Comment 3 Peter Robinson 2015-08-05 14:49:31 UTC

OK, koji-shadow builds in order so I'm going to have to spend time to override that process

Comment 4 Peter Robinson 2015-08-05 16:45:50 UTC

OK, built now