Bug 1250268 - boost 1.58 uses wrong CFLAGS on aarch64 and hence is FTBFS
boost 1.58 uses wrong CFLAGS on aarch64 and hence is FTBFS
Product: Fedora
Classification: Fedora
Component: boost (Show other bugs)
aarch64 Unspecified
urgent Severity urgent
: ---
: ---
Assigned To: Jonathan Wakely
Fedora Extras Quality Assurance
Depends On:
Blocks: ARM64/F-ExcludeArch-aarch64
  Show dependency treegraph
Reported: 2015-08-04 19:12 EDT by Peter Robinson
Modified: 2015-08-05 12:45 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-08-05 12:45:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Robinson 2015-08-04 19:12:39 EDT

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 08:38:24 EDT
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 10:40:50 EDT
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 10:49:31 EDT
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 12:45:50 EDT
OK, built now

Note You need to log in before you can comment on or make changes to this bug.