Re: devel/boost fails to build on sparc64
Markus Lude markus.l...@gmx.de writes: On Tue, Jul 28, 2015 at 04:42:33PM +0200, Jrmie Courrges-Anglas wrote: Stuart Henderson s...@spacehopper.org writes: Hi Jeremie, It's just complaining about -mcpu=c3 (which we don't want anyway) so this should be easy enough to fix.. Indeed. Markus, does boost successfuly package with the following patch? no, build fails not much later: I see, looks like the gcc_sparc backend is not ready for prime time. Here's a diff that should make it fall back on gcc __sync ops; I've just tested a similar diff on amd64 but the sparc64 box I use for ports hasn't been updated in a while. Could you please retry? Index: patches/patch-boost_atomic_detail_platform_hpp === RCS file: patches/patch-boost_atomic_detail_platform_hpp diff -N patches/patch-boost_atomic_detail_platform_hpp --- /dev/null 1 Jan 1970 00:00:00 - +++ patches/patch-boost_atomic_detail_platform_hpp 29 Jul 2015 19:53:52 - @@ -0,0 +1,12 @@ +$OpenBSD$ +--- boost/atomic/detail/platform.hpp.orig Wed Jul 29 20:47:08 2015 boost/atomic/detail/platform.hpp Wed Jul 29 21:51:19 2015 +@@ -59,7 +59,7 @@ + + #define BOOST_ATOMIC_DETAIL_PLATFORM gcc_arm + +-#elif defined(__GNUC__) defined(__sparc_v9__) ++#elif defined(__GNUC__) 0 + + #define BOOST_ATOMIC_DETAIL_PLATFORM gcc_sparc + Index: patches/patch-tools_build_src_tools_gcc_jam === RCS file: /cvs/ports/devel/boost/patches/patch-tools_build_src_tools_gcc_jam,v retrieving revision 1.2 diff -u -p -r1.2 patch-tools_build_src_tools_gcc_jam --- patches/patch-tools_build_src_tools_gcc_jam 10 Jul 2015 08:13:46 - 1.2 +++ patches/patch-tools_build_src_tools_gcc_jam 29 Jul 2015 19:53:52 - @@ -1,6 +1,6 @@ $OpenBSD: patch-tools_build_src_tools_gcc_jam,v 1.2 2015/07/10 08:13:46 jasper Exp $ --- tools/build/src/tools/gcc.jam.orig Sat Apr 4 19:25:07 2015 -+++ tools/build/src/tools/gcc.jam Fri Jul 10 10:13:10 2015 tools/build/src/tools/gcc.jam Tue Jul 28 16:36:55 2015 @@ -337,7 +337,7 @@ class gcc-pch-generator : pch-generator # Return result of base class and pch-file property as # usage-requirements. @@ -68,3 +68,127 @@ $OpenBSD: patch-tools_build_src_tools_gc } rule setup-threading ( targets * : sources * : properties * ) +@@ -1068,123 +1067,3 @@ local rule cpu-flags ( toolset variable : architecture + } + + +-# Set architecture/instruction-set options. +-# +-# x86 and compatible +-# The 'native' option appeared in gcc 4.2 so we cannot safely use it as default. +-# Use i686 instead for 32-bit. +-toolset.flags gcc OPTIONS architecturex86/address-model32/instruction-set : -march=i686 ; +-cpu-flags gcc OPTIONS : x86 : native : -march=native ; +-cpu-flags gcc OPTIONS : x86 : i486 : -march=i486 ; +-cpu-flags gcc OPTIONS : x86 : i586 : -march=i586 ; +-cpu-flags gcc OPTIONS : x86 : i686 : -march=i686 ; +-cpu-flags gcc OPTIONS : x86 : pentium : -march=pentium ; +-cpu-flags gcc OPTIONS : x86 : pentium-mmx : -march=pentium-mmx ; +-cpu-flags gcc OPTIONS : x86 : pentiumpro : -march=pentiumpro ; +-cpu-flags gcc OPTIONS : x86 : pentium2 : -march=pentium2 ; +-cpu-flags gcc OPTIONS : x86 : pentium3 : -march=pentium3 ; +-cpu-flags gcc OPTIONS : x86 : pentium3m : -march=pentium3m ; +-cpu-flags gcc OPTIONS : x86 : pentium-m : -march=pentium-m ; +-cpu-flags gcc OPTIONS : x86 : pentium4 : -march=pentium4 ; +-cpu-flags gcc OPTIONS : x86 : pentium4m : -march=pentium4m ; +-cpu-flags gcc OPTIONS : x86 : prescott : -march=prescott ; +-cpu-flags gcc OPTIONS : x86 : nocona : -march=nocona ; +-cpu-flags gcc OPTIONS : x86 : core2 : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe-l : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : allendale : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : wolfdale : -march=core2 -msse4.1 ; +-cpu-flags gcc OPTIONS : x86 : merom : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : merom-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : kentsfield : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : kentsfield-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : yorksfield : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : penryn : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : corei7 : -march=corei7 ; +-cpu-flags gcc OPTIONS : x86 : nehalem : -march=corei7 ; +-cpu-flags gcc OPTIONS : x86 : corei7-avx : -march=corei7-avx ; +-cpu-flags gcc OPTIONS : x86 : sandy-bridge : -march=corei7-avx ; +-cpu-flags gcc OPTIONS : x86 : core-avx-i : -march=core-avx-i ; +-cpu-flags gcc OPTIONS : x86 : ivy-bridge : -march=core-avx-i ; +-cpu-flags gcc OPTIONS : x86 : haswell : -march=core-avx-i -mavx2 -mfma -mbmi -mbmi2 -mlzcnt ; +-cpu-flags gcc OPTIONS : x86 : k6 : -march=k6 ; +-cpu-flags gcc OPTIONS : x86 : k6-2 : -march=k6-2 ; +-cpu-flags gcc OPTIONS :
Re: devel/boost fails to build on sparc64
On Tue, Jul 28, 2015 at 12:07:21AM +0200, Markus Lude wrote: Hello, devel/boost fails to build on sparc64 here: This is known, it also fails on hppa and alpha. Landry
Re: devel/boost fails to build on sparc64
It's just complaining about -mcpu=c3 (which we don't want anyway) so this should be easy enough to fix.. On 27 July 2015 23:07:21 BST, Markus Lude markus.l...@gmx.de wrote: Hello, devel/boost fails to build on sparc64 here: === Building for boost-1.58.0 Performing configuration checks - 32-bit : no - 64-bit : yes - arm : no - mips1: no - power: no - sparc: yes Building the Boost C++ Libraries. - lockfree boost::atomic_flag : no - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add using mpi ; to your user-config.jam - zlib : no - iconv (libc) : no - iconv (separate) : no - icu : no - icu (lib64) : no - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - gcc visibility : no - long double support : no warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add using mpi ; to user-config.jam. note: to suppress this message, pass --without-mpi to bjam. note: otherwise, you can safely ignore this message. - zlib : no (cached) - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - zlib : no - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - zlib : no (cached) - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. Component configuration: - atomic : building - chrono : building - container: building - context : not building - coroutine: building - date_time: building - exception: building - filesystem : building - graph: building - graph_parallel : building - iostreams: building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex: building - serialization: building - signals : building - system : building - test : building - thread : building - timer: building - wave : building mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7 common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi gcc.compile.c++ bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o echo g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -mcpu=c3 -pthread -m64 -O2 -pipe -pthread -O2 -pipe -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I. -c -o bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o libs/atomic/src/lockpool.cpp g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -mcpu=c3 -pthread -m64 -O2 -pipe -pthread -O2 -pipe -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I. -c -o bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static
Re: devel/boost fails to build on sparc64
Stuart Henderson s...@spacehopper.org writes: It's just complaining about -mcpu=c3 (which we don't want anyway) so this should be easy enough to fix.. Indeed. Markus, does boost successfuly package with the following patch? cc'ing Brad. Index: patches/patch-tools_build_src_tools_gcc_jam === RCS file: /cvs/ports/devel/boost/patches/patch-tools_build_src_tools_gcc_jam,v retrieving revision 1.2 diff -u -p -r1.2 patch-tools_build_src_tools_gcc_jam --- patches/patch-tools_build_src_tools_gcc_jam 10 Jul 2015 08:13:46 - 1.2 +++ patches/patch-tools_build_src_tools_gcc_jam 28 Jul 2015 14:37:02 - @@ -1,6 +1,6 @@ $OpenBSD: patch-tools_build_src_tools_gcc_jam,v 1.2 2015/07/10 08:13:46 jasper Exp $ --- tools/build/src/tools/gcc.jam.orig Sat Apr 4 19:25:07 2015 -+++ tools/build/src/tools/gcc.jam Fri Jul 10 10:13:10 2015 tools/build/src/tools/gcc.jam Tue Jul 28 16:36:55 2015 @@ -337,7 +337,7 @@ class gcc-pch-generator : pch-generator # Return result of base class and pch-file property as # usage-requirements. @@ -68,3 +68,127 @@ $OpenBSD: patch-tools_build_src_tools_gc } rule setup-threading ( targets * : sources * : properties * ) +@@ -1068,123 +1067,3 @@ local rule cpu-flags ( toolset variable : architecture + } + + +-# Set architecture/instruction-set options. +-# +-# x86 and compatible +-# The 'native' option appeared in gcc 4.2 so we cannot safely use it as default. +-# Use i686 instead for 32-bit. +-toolset.flags gcc OPTIONS architecturex86/address-model32/instruction-set : -march=i686 ; +-cpu-flags gcc OPTIONS : x86 : native : -march=native ; +-cpu-flags gcc OPTIONS : x86 : i486 : -march=i486 ; +-cpu-flags gcc OPTIONS : x86 : i586 : -march=i586 ; +-cpu-flags gcc OPTIONS : x86 : i686 : -march=i686 ; +-cpu-flags gcc OPTIONS : x86 : pentium : -march=pentium ; +-cpu-flags gcc OPTIONS : x86 : pentium-mmx : -march=pentium-mmx ; +-cpu-flags gcc OPTIONS : x86 : pentiumpro : -march=pentiumpro ; +-cpu-flags gcc OPTIONS : x86 : pentium2 : -march=pentium2 ; +-cpu-flags gcc OPTIONS : x86 : pentium3 : -march=pentium3 ; +-cpu-flags gcc OPTIONS : x86 : pentium3m : -march=pentium3m ; +-cpu-flags gcc OPTIONS : x86 : pentium-m : -march=pentium-m ; +-cpu-flags gcc OPTIONS : x86 : pentium4 : -march=pentium4 ; +-cpu-flags gcc OPTIONS : x86 : pentium4m : -march=pentium4m ; +-cpu-flags gcc OPTIONS : x86 : prescott : -march=prescott ; +-cpu-flags gcc OPTIONS : x86 : nocona : -march=nocona ; +-cpu-flags gcc OPTIONS : x86 : core2 : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe-l : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : allendale : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : wolfdale : -march=core2 -msse4.1 ; +-cpu-flags gcc OPTIONS : x86 : merom : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : merom-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : kentsfield : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : kentsfield-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : yorksfield : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : penryn : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : corei7 : -march=corei7 ; +-cpu-flags gcc OPTIONS : x86 : nehalem : -march=corei7 ; +-cpu-flags gcc OPTIONS : x86 : corei7-avx : -march=corei7-avx ; +-cpu-flags gcc OPTIONS : x86 : sandy-bridge : -march=corei7-avx ; +-cpu-flags gcc OPTIONS : x86 : core-avx-i : -march=core-avx-i ; +-cpu-flags gcc OPTIONS : x86 : ivy-bridge : -march=core-avx-i ; +-cpu-flags gcc OPTIONS : x86 : haswell : -march=core-avx-i -mavx2 -mfma -mbmi -mbmi2 -mlzcnt ; +-cpu-flags gcc OPTIONS : x86 : k6 : -march=k6 ; +-cpu-flags gcc OPTIONS : x86 : k6-2 : -march=k6-2 ; +-cpu-flags gcc OPTIONS : x86 : k6-3 : -march=k6-3 ; +-cpu-flags gcc OPTIONS : x86 : athlon : -march=athlon ; +-cpu-flags gcc OPTIONS : x86 : athlon-tbird : -march=athlon-tbird ; +-cpu-flags gcc OPTIONS : x86 : athlon-4 : -march=athlon-4 ; +-cpu-flags gcc OPTIONS : x86 : athlon-xp : -march=athlon-xp ; +-cpu-flags gcc OPTIONS : x86 : athlon-mp : -march=athlon-mp ; +-## +-cpu-flags gcc OPTIONS : x86 : k8 : -march=k8 ; +-cpu-flags gcc OPTIONS : x86 : opteron : -march=opteron ; +-cpu-flags gcc OPTIONS : x86 : athlon64 : -march=athlon64 ; +-cpu-flags gcc OPTIONS : x86 : athlon-fx : -march=athlon-fx ; +-cpu-flags gcc OPTIONS : x86 : k8-sse3 : -march=k8-sse3 ; +-cpu-flags gcc OPTIONS : x86 : opteron-sse3 : -march=opteron-sse3 ; +-cpu-flags gcc OPTIONS : x86 : athlon64-sse3 : -march=athlon64-sse3 ; +-cpu-flags gcc OPTIONS : x86 : amdfam10 : -march=amdfam10 ; +-cpu-flags gcc OPTIONS : x86 : barcelona : -march=barcelona ; +-cpu-flags gcc OPTIONS : x86 : bdver1 : -march=bdver1 ; +-cpu-flags gcc OPTIONS : x86 : bdver2 : -march=bdver2 ; +-cpu-flags gcc OPTIONS : x86 : bdver3 : -march=bdver3 ; +-cpu-flags gcc OPTIONS : x86 : btver1 : -march=btver1 ; +-cpu-flags gcc OPTIONS
Re: devel/boost fails to build on sparc64
Shouldn't also kind of https://github.com/boostorg/build/commit/ec60c37295146bb80aa44a92cf416027b75b5ff7 goes in? On Tue, Jul 28, 2015 at 4:42 PM, Jérémie Courrèges-Anglas j...@wxcvbn.org wrote: Stuart Henderson s...@spacehopper.org writes: It's just complaining about -mcpu=c3 (which we don't want anyway) so this should be easy enough to fix.. Indeed. Markus, does boost successfuly package with the following patch? cc'ing Brad. Index: patches/patch-tools_build_src_tools_gcc_jam === RCS file: /cvs/ports/devel/boost/patches/patch-tools_build_src_tools_gcc_jam,v retrieving revision 1.2 diff -u -p -r1.2 patch-tools_build_src_tools_gcc_jam --- patches/patch-tools_build_src_tools_gcc_jam 10 Jul 2015 08:13:46 - 1.2 +++ patches/patch-tools_build_src_tools_gcc_jam 28 Jul 2015 14:37:02 - @@ -1,6 +1,6 @@ $OpenBSD: patch-tools_build_src_tools_gcc_jam,v 1.2 2015/07/10 08:13:46 jasper Exp $ --- tools/build/src/tools/gcc.jam.orig Sat Apr 4 19:25:07 2015 -+++ tools/build/src/tools/gcc.jam Fri Jul 10 10:13:10 2015 tools/build/src/tools/gcc.jam Tue Jul 28 16:36:55 2015 @@ -337,7 +337,7 @@ class gcc-pch-generator : pch-generator # Return result of base class and pch-file property as # usage-requirements. @@ -68,3 +68,127 @@ $OpenBSD: patch-tools_build_src_tools_gc } rule setup-threading ( targets * : sources * : properties * ) +@@ -1068,123 +1067,3 @@ local rule cpu-flags ( toolset variable : architecture + } + + +-# Set architecture/instruction-set options. +-# +-# x86 and compatible +-# The 'native' option appeared in gcc 4.2 so we cannot safely use it as default. +-# Use i686 instead for 32-bit. +-toolset.flags gcc OPTIONS architecturex86/address-model32/instruction-set : -march=i686 ; +-cpu-flags gcc OPTIONS : x86 : native : -march=native ; +-cpu-flags gcc OPTIONS : x86 : i486 : -march=i486 ; +-cpu-flags gcc OPTIONS : x86 : i586 : -march=i586 ; +-cpu-flags gcc OPTIONS : x86 : i686 : -march=i686 ; +-cpu-flags gcc OPTIONS : x86 : pentium : -march=pentium ; +-cpu-flags gcc OPTIONS : x86 : pentium-mmx : -march=pentium-mmx ; +-cpu-flags gcc OPTIONS : x86 : pentiumpro : -march=pentiumpro ; +-cpu-flags gcc OPTIONS : x86 : pentium2 : -march=pentium2 ; +-cpu-flags gcc OPTIONS : x86 : pentium3 : -march=pentium3 ; +-cpu-flags gcc OPTIONS : x86 : pentium3m : -march=pentium3m ; +-cpu-flags gcc OPTIONS : x86 : pentium-m : -march=pentium-m ; +-cpu-flags gcc OPTIONS : x86 : pentium4 : -march=pentium4 ; +-cpu-flags gcc OPTIONS : x86 : pentium4m : -march=pentium4m ; +-cpu-flags gcc OPTIONS : x86 : prescott : -march=prescott ; +-cpu-flags gcc OPTIONS : x86 : nocona : -march=nocona ; +-cpu-flags gcc OPTIONS : x86 : core2 : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : conroe-l : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : allendale : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : wolfdale : -march=core2 -msse4.1 ; +-cpu-flags gcc OPTIONS : x86 : merom : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : merom-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : kentsfield : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : kentsfield-xe : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : yorksfield : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : penryn : -march=core2 ; +-cpu-flags gcc OPTIONS : x86 : corei7 : -march=corei7 ; +-cpu-flags gcc OPTIONS : x86 : nehalem : -march=corei7 ; +-cpu-flags gcc OPTIONS : x86 : corei7-avx : -march=corei7-avx ; +-cpu-flags gcc OPTIONS : x86 : sandy-bridge : -march=corei7-avx ; +-cpu-flags gcc OPTIONS : x86 : core-avx-i : -march=core-avx-i ; +-cpu-flags gcc OPTIONS : x86 : ivy-bridge : -march=core-avx-i ; +-cpu-flags gcc OPTIONS : x86 : haswell : -march=core-avx-i -mavx2 -mfma -mbmi -mbmi2 -mlzcnt ; +-cpu-flags gcc OPTIONS : x86 : k6 : -march=k6 ; +-cpu-flags gcc OPTIONS : x86 : k6-2 : -march=k6-2 ; +-cpu-flags gcc OPTIONS : x86 : k6-3 : -march=k6-3 ; +-cpu-flags gcc OPTIONS : x86 : athlon : -march=athlon ; +-cpu-flags gcc OPTIONS : x86 : athlon-tbird : -march=athlon-tbird ; +-cpu-flags gcc OPTIONS : x86 : athlon-4 : -march=athlon-4 ; +-cpu-flags gcc OPTIONS : x86 : athlon-xp : -march=athlon-xp ; +-cpu-flags gcc OPTIONS : x86 : athlon-mp : -march=athlon-mp ; +-## +-cpu-flags gcc OPTIONS : x86 : k8 : -march=k8 ; +-cpu-flags gcc OPTIONS : x86 : opteron : -march=opteron ; +-cpu-flags gcc OPTIONS : x86 : athlon64 : -march=athlon64 ; +-cpu-flags gcc OPTIONS : x86 : athlon-fx : -march=athlon-fx ; +-cpu-flags gcc OPTIONS : x86 : k8-sse3 : -march=k8-sse3 ; +-cpu-flags gcc OPTIONS : x86 : opteron-sse3 : -march=opteron-sse3 ; +-cpu-flags gcc OPTIONS : x86 : athlon64-sse3 : -march=athlon64-sse3 ; +-cpu-flags gcc OPTIONS : x86 : amdfam10 : -march=amdfam10 ; +-cpu-flags gcc OPTIONS : x86 :
Re: devel/boost fails to build on sparc64
Oh, I've thought Jérémie's diff just added those cpu specific flags. Reading more carefully it looks like it adds removal of those flags into the OpenBSD's patch file. Sorry guys for noise. On Tue, Jul 28, 2015 at 6:27 PM, Stuart Henderson s...@spacehopper.org wrote: On 2015/07/28 18:10, Karel Gardas wrote: Shouldn't also kind of https://github.com/boostorg/build/commit/ec60c37295146bb80aa44a92cf416027b75b5ff7 goes in? No, because we don't want to use the CPU-specific flags at all, Jérémie's diff removes these completely.
Re: devel/boost fails to build on sparc64
On 2015/07/28 18:10, Karel Gardas wrote: Shouldn't also kind of https://github.com/boostorg/build/commit/ec60c37295146bb80aa44a92cf416027b75b5ff7 goes in? No, because we don't want to use the CPU-specific flags at all, Jérémie's diff removes these completely.
Re: devel/boost fails to build on sparc64
On Tue, Jul 28, 2015 at 04:42:33PM +0200, Jrmie Courrges-Anglas wrote: Stuart Henderson s...@spacehopper.org writes: Hi Jeremie, It's just complaining about -mcpu=c3 (which we don't want anyway) so this should be easy enough to fix.. Indeed. Markus, does boost successfuly package with the following patch? no, build fails not much later: === Building for boost-1.58.0 Performing configuration checks - 32-bit : no - 64-bit : yes - arm : no - mips1: no - power: no - sparc: yes Building the Boost C++ Libraries. - lockfree boost::atomic_flag : no - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add using mpi ; to your user-config.jam - zlib : yes - iconv (libc) : no - iconv (separate) : yes - icu : no - icu (lib64) : no - gcc visibility : yes - long double support : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add using mpi ; to user-config.jam. note: to suppress this message, pass --without-mpi to bjam. note: otherwise, you can safely ignore this message. - zlib : yes (cached) - zlib : yes - zlib : yes (cached) Component configuration: - atomic : building - chrono : building - container: building - context : not building - coroutine: building - date_time: building - exception: building - filesystem : building - graph: building - graph_parallel : building - iostreams: building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex: building - serialization: building - signals : building - system : building - test : building - thread : building - timer: building - wave : building common.mkdir stage mkdir -p stage common.mkdir stage/lib mkdir -p stage/lib common.mkdir bin.v2/libs/atomic mkdir -p bin.v2/libs/atomic common.mkdir bin.v2/libs/atomic/build mkdir -p bin.v2/libs/atomic/build common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1 mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1 common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7 mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7 common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi gcc.compile.c++ bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o echo g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -pthread -m64 -O2 -pipe -pthread -O2 -pipe -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I. -c -o bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o libs/atomic/src/lockpool.cpp g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -pthread -m64 -O2 -pipe -pthread -O2 -pipe -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I. -c -o bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o libs/atomic/src/lockpool.cpp g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -pthread -m64 -O2 -pipe -pthread -O2 -pipe -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I. -c -o bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o libs/atomic/src/lockpool.cpp In file included from ./boost/atomic/detail/operations_lockfree.hpp:21, from libs/atomic/src/lockpool.cpp:22: ./boost/atomic/detail/ops_gcc_sparc.hpp: In static member function 'static void
devel/boost fails to build on sparc64
Hello, devel/boost fails to build on sparc64 here: === Building for boost-1.58.0 Performing configuration checks - 32-bit : no - 64-bit : yes - arm : no - mips1: no - power: no - sparc: yes Building the Boost C++ Libraries. - lockfree boost::atomic_flag : no - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add using mpi ; to your user-config.jam - zlib : no - iconv (libc) : no - iconv (separate) : no - icu : no - icu (lib64) : no - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - gcc visibility : no - long double support : no warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add using mpi ; to user-config.jam. note: to suppress this message, pass --without-mpi to bjam. note: otherwise, you can safely ignore this message. - zlib : no (cached) - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - zlib : no - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - zlib : no (cached) - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. Component configuration: - atomic : building - chrono : building - container: building - context : not building - coroutine: building - date_time: building - exception: building - filesystem : building - graph: building - graph_parallel : building - iostreams: building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex: building - serialization: building - signals : building - system : building - test : building - thread : building - timer: building - wave : building mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7 common.mkdir bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi mkdir -p bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi gcc.compile.c++ bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o echo g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -mcpu=c3 -pthread -m64 -O2 -pipe -pthread -O2 -pipe -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I. -c -o bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o libs/atomic/src/lockpool.cpp g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -mcpu=c3 -pthread -m64 -O2 -pipe -pthread -O2 -pipe -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I. -c -o bin.v2/libs/atomic/build/gcc-4.2.1/release/link-static/python-2.7/threading-multi/lockpool.o libs/atomic/src/lockpool.cpp g++ -ftemplate-depth-128 -finline-functions -Wno-inline -Wall -mcpu=c3
