FreeBSD Bugzilla – Attachment 163203 Details for
Bug 204606
devel/boost-all: Update to 1.58.0 (Needed for MySQL 5.7]
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
my shar files of lib boost
boost-all.shar (text/plain), 7.33 KB, created by
Mahdi Mokhtari
on 2015-11-16 19:18:31 UTC
(
hide
)
Description:
my shar files of lib boost
Filename:
MIME Type:
Creator:
Mahdi Mokhtari
Created:
2015-11-16 19:18:31 UTC
Size:
7.33 KB
patch
obsolete
># This is a shell archive. Save it in a file, remove anything before ># this line, and then unpack it by entering "sh file". Note, it may ># create directories; files and directories will be owned by you and ># have default permissions. ># ># This archive contains: ># ># boost-all/ ># boost-all/common.mk ># boost-all/Makefile ># boost-all/compiled.mk ># boost-all/pkg-message.threads ># boost-all/pkg-descr ># boost-all/pkg-message.python ># boost-all/common.mk.orig ># boost-all/compiled.mk.orig ># >echo c - boost-all/ >mkdir -p boost-all/ > /dev/null 2>&1 >echo x - boost-all/common.mk >sed 's/^X//' >boost-all/common.mk << 'de57c7ec6b519d1e55c8b99716df5b4e' >X >XPORTVERSION= 1.58.0 >XPORTVERSUFFIX= ${PORTVERSION:C/\.[0-9]+$//} >XDISTNAME= boost_${PORTVERSION:S/./_/g} >X >XCATEGORIES= devel >XMAINTAINER= office@FreeBSD.org >X >XCONFLICTS+= boost-python-1* boost-1* >XMASTER_SITES= SF/boost/boost/${PORTVERSION} >X >XUSES+= tar:bzip2 >de57c7ec6b519d1e55c8b99716df5b4e >echo x - boost-all/Makefile >sed 's/^X//' >boost-all/Makefile << '75143f08079b2f64b214b079bcd092f6' >X# Created by: "Mahdi Mokhtari <mokhi64@gmail.com>" >X# $FreeBSD$ >X >XPORTNAME= boost-all >XMASTER_SITES= # empty >X >XMAINTAINER= mokhi64@gmail.com >X >XDISTFILES= # none >XEXTRACT_ONLY= # empty >X >XCOMMENT?= The "meta-port" for boost libraries >X >XOPTIONS_DEFINE= JAM LIBRARIES PYTHON DOCS >XOPTIONS_DEFAULT= JAM LIBRARIES >XJAM_DESC= Boost.Jam - Build tool from the boost.org >XLIBRARIES_DESC= Free portable C++ libraries >XPYTHON_DESC= Boost.Python - interfacing Python and C++ >X >XNO_BUILD= yes >XNO_MTREE= yes >X >X.include "common.mk" >X >XLIBRARIES_RUN_DEPENDS= ${LOCALBASE}/lib/libboost_thread.so:${PORTSDIR}/devel/boost-libs >XJAM_RUN_DEPENDS= ${LOCALBASE}/bin/bjam:${PORTSDIR}/devel/boost-jam >XPYTHON_RUN_DEPENDS= ${LOCALBASE}/lib/libboost_python.so:${PORTSDIR}/devel/boost-python-libs >XDOCS_RUN_DEPENDS= ${LOCALBASE}/share/doc/boost/doc/html/index.html:${PORTSDIR}/devel/boost-docs >X >Xdo-install: >X ${DO_NADA} >X >X.include <bsd.port.mk> >75143f08079b2f64b214b079bcd092f6 >echo x - boost-all/compiled.mk >sed 's/^X//' >boost-all/compiled.mk << 'd7cf1ccc261b98b0e87e0e9019041c0e' >XUSE_LDCONFIG= yes >XPKGMESSAGE= ${WRKDIR}/pkg-message >XMAKE_CMD= bjam >XMAKEFILE= # >XMAKE_FLAGS= # >XALL_TARGET= stage >XUSES+= compiler:features >X >XPLIST_SUB+= BOOST_SHARED_LIB_VER=${PORTVERSION} COMPAT_LIB_VER=5 >X >XPKG_MESSAGE_FILE_THREADS= ${PORTSDIR}/devel/boost-all/pkg-message.threads >XPKG_MESSAGE_FILE_PYTHON= ${PORTSDIR}/devel/boost-all/pkg-message.python >X >X.include <bsd.port.pre.mk> >X >XMAKE_ARGS= --layout=system \ >X --prefix=${PREFIX} \ >X >X.if ${ARCH} == amd64 >XMAKE_ARGS+= cxxflags=-fPIC >X.endif >X >X# Our compiler-flags will be added AFTER those set by bjam. We remove >X# the optimization level, because Boost sets it itself (to -O3 in case >X# of gcc/g++): >XMAKE_ARGS+= cxxflags="${CXXFLAGS:N-O*}" cflags="${CFLAGS:N-O*}" >X >XBOOST_TOOLSET= ${CHOSEN_COMPILER_TYPE} >X >XMAKE_ARGS+= --toolset=${BOOST_TOOLSET} \ >X ${_MAKE_JOBS} >X >X.if ${PORT_OPTIONS:MVERBOSE_BUILD} >XMAKE_ARGS+= -d2 >X.endif >X >X.if ${PORT_OPTIONS:MDEBUG} >XMAKE_ARGS+= debug >X.else >XMAKE_ARGS+= release >X.endif >X >XMAKE_ARGS+= threading=multi \ >X link=shared,static >X >XMAKE_ARGS+= optimization=speed >X.if ${PORT_OPTIONS:MOPTIMIZED_CFLAGS} >XMAKE_ARGS+= inlining=full >X.endif >X >X# ccache build fails when using precompiled headers, on a cached build. >X.if defined(WITH_CCACHE_BUILD) >XMAKE_ARGS+= pch=off >X.endif >X >Xpost-patch: >X.if defined(USE_BINUTILS) >X @${ECHO} "using ${BOOST_TOOLSET} : : ${CXX} : <linkflags>-B${LOCALBASE}/bin ;" >> ${WRKSRC}/tools/build/src/user-config.jam >X.else >X @${ECHO} "using ${BOOST_TOOLSET} : : ${CXX} ;" >> ${WRKSRC}/tools/build/src/user-config.jam >X.endif >d7cf1ccc261b98b0e87e0e9019041c0e >echo x - boost-all/pkg-message.threads >sed 's/^X//' >boost-all/pkg-message.threads << '2224b45ced20eef9bc953de4acbba9e7' >XYou have built the Boost library with thread support. >X >XDon't forget to add -pthread to your linker options when >Xlinking your code. >2224b45ced20eef9bc953de4acbba9e7 >echo x - boost-all/pkg-descr >sed 's/^X//' >boost-all/pkg-descr << '1f6b5af0f64f7a28365510bf56d74997' >XThis is a meta-port for boost libraries, depends on all of them. >X >XBoost provides free peer-reviewed portable C++ source libraries. >X >XThe emphasis is on libraries that work well with the C++ Standard >XLibrary. Boost libraries are intended to be widely useful, and usable >Xacross a broad spectrum of applications. The Boost license encourages >Xboth commercial and non-commercial use. >X >XThe goal is to establish "existing practice" and provide reference >Ximplementations so that Boost libraries are suitable for eventual >Xstandardization. Ten Boost libraries are already included in the C++ >XStandards Committee's Library Technical Report (TR1) and will be in >Xthe new C++0x Standard now being finalized. C++0x will also include >Xseveral more Boost libraries in addition to those from TR1. More Boost >Xlibraries are proposed for TR2. >X >XWWW: http://www.boost.org/ >1f6b5af0f64f7a28365510bf56d74997 >echo x - boost-all/pkg-message.python >sed 's/^X//' >boost-all/pkg-message.python << 'ebf83aa5bce403e661d5c23f6de7f23c' >XYou have built the Boost.Python library. You have to add the following >Xoptions when building your own code: >X >XCompiler options: >X -I%%PYTHON_INCLUDEDIR%% -I%%LOCALBASE%%/include >X >XLinker options: >X -L%%PYTHON_LIBDIR%% -L%%LOCALBASE%%/lib -lboost_python -l%%PYTHON_VERSION%% >ebf83aa5bce403e661d5c23f6de7f23c >echo x - boost-all/common.mk.orig >sed 's/^X//' >boost-all/common.mk.orig << '70aef603c1aaa37fe80cc65eaf13722c' >X >XPORTVERSION= 1.55.0 >XPORTVERSUFFIX= ${PORTVERSION:C/\.[0-9]+$//} >XDISTNAME= boost_${PORTVERSION:S/./_/g} >X >XCATEGORIES= devel >XMAINTAINER= office@FreeBSD.org >X >XCONFLICTS+= boost-python-1* boost-1* >XMASTER_SITES= SF/boost/boost/${PORTVERSION} >X >XUSES+= tar:bzip2 >70aef603c1aaa37fe80cc65eaf13722c >echo x - boost-all/compiled.mk.orig >sed 's/^X//' >boost-all/compiled.mk.orig << 'e21e67087b6b58ced52972b13715d4fb' >XUSE_LDCONFIG= yes >XPKGMESSAGE= ${WRKDIR}/pkg-message >XBJAM= bjam >XUSES+= compiler:c++11-lang >X >XPLIST_SUB+= BOOST_SHARED_LIB_VER=${PORTVERSION} COMPAT_LIB_VER=5 >X >XPKG_MESSAGE_FILE_THREADS= ${PORTSDIR}/devel/boost-all/pkg-message.threads >XPKG_MESSAGE_FILE_PYTHON= ${PORTSDIR}/devel/boost-all/pkg-message.python >X >X.include <bsd.port.pre.mk> >X >XBJAM_ARGS= --layout=system \ >X --prefix=${PREFIX} \ >X >X.if ${ARCH} == amd64 >XBJAM_ARGS+= cxxflags=-fPIC >X.endif >X >X# Our compiler-flags will be added AFTER those set by bjam. We remove >X# the optimization level, because Boost sets it itself (to -O3 in case >X# of gcc/g++): >XBJAM_ARGS+= cxxflags="${CXXFLAGS:N-O*}" cflags="${CFLAGS:N-O*}" >X >XBOOST_TOOLSET= ${CHOSEN_COMPILER_TYPE} >X >XBJAM_ARGS+= --toolset=${BOOST_TOOLSET} \ >X ${_MAKE_JOBS} >X >X.if ${PORT_OPTIONS:MVERBOSE_BUILD} >XBJAM_ARGS+= -d2 >X.endif >X >X.if ${PORT_OPTIONS:MDEBUG} >XBJAM_ARGS+= debug >X.else >XBJAM_ARGS+= release >X.endif >X >XBJAM_ARGS+= threading=multi \ >X link=shared,static >X >XBJAM_ARGS+= optimization=speed >X.if ${PORT_OPTIONS:MOPTIMIZED_CFLAGS} >XBJAM_ARGS+= inlining=full >X.endif >X >X# ccache build fails when using precompiled headers, on a cached build. >X.if defined(WITH_CCACHE_BUILD) >XBJAM_ARGS+= pch=off >X.endif >X >Xpost-patch: >X.if defined(USE_BINUTILS) >X @${ECHO} "using ${BOOST_TOOLSET} : : ${CXX} : <linkflags>-B${LOCALBASE}/bin ;" >> ${WRKSRC}/tools/build/v2/user-config.jam >X.else >X @${ECHO} "using ${BOOST_TOOLSET} : : ${CXX} ;" >> ${WRKSRC}/tools/build/v2/user-config.jam >X.endif >e21e67087b6b58ced52972b13715d4fb >exit >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 204606
: 163203 |
163204
|
163205