Re: update/fix: devel/boost

2018-12-30 Thread Stuart Henderson 
On 2018/12/30 19:05, Rafael Sadowski wrote:
> +Index: tools/build/src/engine/Jambase
> +--- tools/build/src/engine/Jambase.orig
>  tools/build/src/engine/Jambase
> +@@ -51,7 +51,7 @@ BOOST_BUILD_PATH.user-value = $(BOOST_BUILD_PATH) ;
> + # Policy.
> + if ! $(BOOST_BUILD_PATH) && $(UNIX)
> + {
> +-BOOST_BUILD_PATH = /usr/share/boost-build ;
> ++BOOST_BUILD_PATH = ${LOCALBASE}/share/boost-build ;

from bsd.port.mk(5) :

   LOCALBASE
   where other ports have already been installed.  Default: /usr/local.

   PREFIX  Base directory for the current port installation.

this refers to "current port" so should be prefix.

Re: update/fix: devel/boost

2018-12-30 Thread Rafael Sadowski 
On Sun Dec 30, 2018 at 05:32:22PM +0300, Ivan Krylov wrote:
> Hi Rafael,
> 
> On Fri, 28 Dec 2018 21:02:44 +0100
> Rafael Sadowski  wrote:
> 
> > package fine for me. OK?
> 
> b2 builds my projects fine, too. One small problem I have with it is
> that it requires me to pass BOOST_BUILD_PATH or BOOST_ROOT environment
> variable. I'm suggesting the patch below that should provide a default
> path for b2 to find its files in after the package is installed. Tell
> me if I should arrange it differently.
> 
> --- boost_1_66_0/tools/build/src/engine/Jambase.orig  Sun Dec 30 17:23:23 2018
> +++ boost_1_66_0/tools/build/src/engine/Jambase   Sun Dec 30 17:24:37 2018
> @@ -51,7 +51,7 @@
>  # Policy.
>  if ! $(BOOST_BUILD_PATH) && $(UNIX)
>  {
> -BOOST_BUILD_PATH = /usr/share/boost-build ;
> +BOOST_BUILD_PATH = /usr/local/share/boost-build/kernel ;
>  }
> 
> Thank you for your work and happy holidays!
> 
> -- 
> Best regards,
> Ivan
> 

Thanks for your feedback. New diff below which fix BOOST_BUILD_PATH in
Jambase.

Rafael Sadowski


Index: Makefile
===
RCS file: /cvs/ports/devel/boost/Makefile,v
retrieving revision 1.79
diff -u -p -u -p -r1.79 Makefile
--- Makefile24 Dec 2018 23:34:27 -  1.79
+++ Makefile30 Dec 2018 18:04:24 -
@@ -9,7 +9,7 @@ VERSION=1.66.0
 DISTNAME=  boost_${VERSION:S/./_/g}
 PKGNAME-main=  boost-${VERSION}
 PKGNAME-md=boost-md-${VERSION}
-REVISION-main= 1
+REVISION-main= 2
 CATEGORIES=devel
 MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=boost/}
 EXTRACT_SUFX=  .tar.bz2
@@ -145,6 +145,9 @@ NO_TEST=Yes
 
 SUBST_VARS+=   SO_VERSION
 
+pre-configure:
+   ${SUBST_CMD} ${WRKSRC}/tools/build/src/engine/Jambase
+
 do-configure:
echo "using ${TOOLSET} : : ${CXX} ;" 
>>${WRKSRC}/tools/build/user-config.jam
@${SUBST_CMD} ${WRKSRC}/Jamroot
@@ -167,12 +170,23 @@ do-build:
./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
-   ${PREFIX}/bin
+   # Libs and includes:
${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
@cd ${WRKSRC} && \
find boost -type d -exec ${INSTALL_DATA_DIR} 
${PREFIX}/include/{} \;
@cd ${WRKSRC} && \
find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {} 
${PREFIX}/include/{} \;
+   # boost-build:
+   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
+   ${PREFIX}/bin
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
+   @cd ${WRKSRC}/tools/build/src && \
+   pax -r -w -p pm -s ':^./engine.*$$::' \
+   -s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
+   ${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
+   ${PREFIX}/share/examples/boost-build
+   ${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
+   ${PREFIX}/share/boost-build/
 
 .include 
Index: patches/patch-tools_build_src_engine_Jambase
===
RCS file: patches/patch-tools_build_src_engine_Jambase
diff -N patches/patch-tools_build_src_engine_Jambase
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-tools_build_src_engine_Jambase30 Dec 2018 18:04:24 
-
@@ -0,0 +1,14 @@
+$OpenBSD$
+
+Index: tools/build/src/engine/Jambase
+--- tools/build/src/engine/Jambase.orig
 tools/build/src/engine/Jambase
+@@ -51,7 +51,7 @@ BOOST_BUILD_PATH.user-value = $(BOOST_BUILD_PATH) ;
+ # Policy.
+ if ! $(BOOST_BUILD_PATH) && $(UNIX)
+ {
+-BOOST_BUILD_PATH = /usr/share/boost-build ;
++BOOST_BUILD_PATH = ${LOCALBASE}/share/boost-build ;
+ }
+ 
+ 
Index: pkg/PLIST-main
===
RCS file: /cvs/ports/devel/boost/pkg/PLIST-main,v
retrieving revision 1.6
diff -u -p -u -p -r1.6 PLIST-main
--- pkg/PLIST-main  13 Dec 2018 19:52:46 -  1.6
+++ pkg/PLIST-main  30 Dec 2018 18:04:25 -
@@ -14160,3 +14160,362 @@ lib/libboost_wserialization-mt.a
 @lib lib/libboost_wserialization-mt.so.${LIBboost_wserialization-mt_VERSION}
 lib/libboost_wserialization.a
 @lib lib/libboost_wserialization.so.${LIBboost_wserialization_VERSION}
+share/boost-build/
+share/boost-build/__init__.py
+share/boost-build/__init__.pyc
+share/boost-build/bootstrap.jam
+share/boost-build/build/
+share/boost-build/build-system.jam
+share/boost-build/build/__init__.py
+share/boost-build/build/__init__.pyc
+share/boost-build/build/ac.jam
+share/boost-build/build/alias.jam
+share/boost-build/build/alias.py
+share/boost-build/build/alias.pyc
+share/boost-build/build/build-request.jam
+share/boost-build/build/build_request.py
+share/boost-build/build/build_request.pyc
+share/boost-build/build/config-cache.jam

Re: update/fix: devel/boost

2018-12-30 Thread Ivan Krylov 
Hi Rafael,

On Fri, 28 Dec 2018 21:02:44 +0100
Rafael Sadowski  wrote:

> package fine for me. OK?

b2 builds my projects fine, too. One small problem I have with it is
that it requires me to pass BOOST_BUILD_PATH or BOOST_ROOT environment
variable. I'm suggesting the patch below that should provide a default
path for b2 to find its files in after the package is installed. Tell
me if I should arrange it differently.

--- boost_1_66_0/tools/build/src/engine/Jambase.origSun Dec 30 17:23:23 2018
+++ boost_1_66_0/tools/build/src/engine/Jambase Sun Dec 30 17:24:37 2018
@@ -51,7 +51,7 @@
 # Policy.
 if ! $(BOOST_BUILD_PATH) && $(UNIX)
 {
-BOOST_BUILD_PATH = /usr/share/boost-build ;
+BOOST_BUILD_PATH = /usr/local/share/boost-build/kernel ;
 }

Thank you for your work and happy holidays!

-- 
Best regards,
Ivan

Re: update/fix: devel/boost

2018-12-28 Thread Antoine Jacoutot 
I agree with Stuart. We're not Debian. We don't subpackage by default. If we 
do, there needs to be a good reason.


On December 28, 2018 8:04:51 PM GMT+01:00, Stuart Henderson 
 wrote:
>On 2018/12/28 19:30, Rafael Sadowski wrote:
>> On Fri Dec 28, 2018 at 02:31:49PM +, Stuart Henderson wrote:
>> > Why subpackage this?
>> 
>> Because nobody needs boost-build to run/build any ports. Let's be
>> unfair, nobody needs boost-build except *maybe* a handful user.
>
>If it was something huge then it would make sense. But really I don't
>see the point in splitting it, it's got to be pretty small, I haven't
>looked at the size of the new files but I can't imagine the whole thing
>can be more than a MB or so can it? Less if the two identical files
>b2 and bjam were hardlinked together.
>
>> Doas another subpackge hurts?
>
>Yes, it's extra scaffolding and extra risk of getting things wrong
>both in the port itself, and in ports which might end up needing it
>in the future.
>
>I'm not going to insist but I really don't see a good reason to split
>it. But if you are going to split it anyway see comments inline.;
>
>> > -- 
>> > Sent from a phone, apologies for poor formatting.
>> > 
>> > On 28 December 2018 13:41:22 Rafael Sadowski
> wrote:
>> > 
>> > > Hi all!
>> > > 
>> > > Our boost.build executables b2 and bjam are useless without the
>*.jam
>> > > stuff. The diff below want to fix the situation withe a third
>> > > sub-package named "build".
>> > > 
>> > > do-install bits from NetBSD and DESCR from FreeBSD.
>> > > Noticed by Ivan Krylov via openbsd@freenode. Thanks!
>> > > 
>> > > Comments, OK?
>> > > 
>> > > Rafael Sadowski
>> > > 
>> 
>> New diff with a compileall.py call at the end of the do-install step,
>> after feedback from semarie@ and aja@ Thanks!
>> 
>> Index: Makefile
>> ===
>> RCS file: /cvs/ports/devel/boost/Makefile,v
>> retrieving revision 1.79
>> diff -u -p -u -p -r1.79 Makefile
>> --- Makefile 24 Dec 2018 23:34:27 -  1.79
>> +++ Makefile 28 Dec 2018 18:18:16 -
>> @@ -2,6 +2,7 @@
>>  
>>  COMMENT-main=   free peer-reviewed portable C++ source libraries
>>  COMMENT-md= machine-dependent libraries for boost
>> +COMMENT-build=  extensible cross-platform build tool suite
>>  
>>  # XXX if updating, try to remove
>-D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR
>>  # XXX in archivers/innoextract
>> @@ -9,7 +10,8 @@ VERSION=1.66.0
>>  DISTNAME=   boost_${VERSION:S/./_/g}
>>  PKGNAME-main=   boost-${VERSION}
>>  PKGNAME-md= boost-md-${VERSION}
>> -REVISION-main=  1
>> +PKGNAME-build=  boost-build-${VERSION}
>> +REVISION-main=  2
>>  CATEGORIES= devel
>>  MASTER_SITES=   ${MASTER_SITE_SOURCEFORGE:=boost/}
>>  EXTRACT_SUFX=   .tar.bz2
>> @@ -76,7 +78,7 @@ WANTLIB += ${COMPILER_LIBCXX} bz2 c icud
>>  
>>  COMPILER= base-clang ports-gcc
>>  
>> -MULTI_PACKAGES= -main -md
>> +MULTI_PACKAGES= -main -md -build
>>  
>>  MODULES=lang/python
>>  MODPY_RUNDEP=   No
>> @@ -167,12 +169,22 @@ do-build:
>>  ./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\
>>  
>>  do-install:
>> -${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam}
>\
>> -${PREFIX}/bin
>>  ${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
>>  @cd ${WRKSRC} && \
>>  find boost -type d -exec ${INSTALL_DATA_DIR} 
>> ${PREFIX}/include/{}
>\;
>>  @cd ${WRKSRC} && \
>>  find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {}
>${PREFIX}/include/{} \;
>> +# -build
>> +${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam}
>\
>> +${PREFIX}/bin
>> +${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
>> +@cd ${WRKSRC}/tools/build/src && \
>> +pax -r -w -p pm -s ':^./engine.*$$::' \
>> +-s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
>> +${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
>> +${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
>> +${PREFIX}/share/examples/boost-build
>> +${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
>> +${PREFIX}/share/boost-build/
>>  
>>  .include 
>> Index: pkg/DESCR-build
>> ===
>> RCS file: pkg/DESCR-build
>> diff -N pkg/DESCR-build
>> --- /dev/null1 Jan 1970 00:00:00 -
>> +++ pkg/DESCR-build  28 Dec 2018 18:18:16 -
>> @@ -0,0 +1,7 @@
>> +Boost.Build is an easy way to build C++ projects, everywhere. You
>name you
>> +executables and libraries and list their sources.
>
>"You name *your* executables"...
>
>> +
>> +Boost.Build takes care about compiling your sources with right
>options,
>
>"with the right options"
>
>> +creating static and shared libraries, making executables, and other
>chores --
>> +whether you're using gcc, msvc, or a dozen more supported C++
>compilers -- on
>> +Windows, OSX, Linux and commercial UNIX

Re: update/fix: devel/boost

2018-12-28 Thread Stuart Henderson 

Ok with me.
--
Sent from a phone, apologies for poor formatting.

On 28 December 2018 20:02:51 Rafael Sadowski  wrote:


On Fri Dec 28, 2018 at 07:04:51PM +, Stuart Henderson wrote:

On 2018/12/28 19:30, Rafael Sadowski wrote:
> On Fri Dec 28, 2018 at 02:31:49PM +, Stuart Henderson wrote:
> > Why subpackage this?
>
> Because nobody needs boost-build to run/build any ports. Let's be
> unfair, nobody needs boost-build except *maybe* a handful user.

If it was something huge then it would make sense. But really I don't
see the point in splitting it, it's got to be pretty small, I haven't
looked at the size of the new files but I can't imagine the whole thing
can be more than a MB or so can it? Less if the two identical files
b2 and bjam were hardlinked together.

> Doas another subpackge hurts?

Yes, it's extra scaffolding and extra risk of getting things wrong
both in the port itself, and in ports which might end up needing it
in the future.

I'm not going to insist but I really don't see a good reason to split
it. But if you are going to split it anyway see comments inline.;



Those are of course good points and it does not have to be for me
necessarily a subpackage. Below a diff without -build subpackage.

package fine for me. OK?

Rafael Sadowski

Index: Makefile
===
RCS file: /cvs/ports/devel/boost/Makefile,v
retrieving revision 1.79
diff -u -p -u -p -r1.79 Makefile
--- Makefile24 Dec 2018 23:34:27 -  1.79
+++ Makefile28 Dec 2018 19:56:58 -
@@ -9,7 +9,7 @@ VERSION=1.66.0
DISTNAME=   boost_${VERSION:S/./_/g}
PKGNAME-main=   boost-${VERSION}
PKGNAME-md= boost-md-${VERSION}
-REVISION-main= 1
+REVISION-main= 2
CATEGORIES= devel
MASTER_SITES=   ${MASTER_SITE_SOURCEFORGE:=boost/}
EXTRACT_SUFX=   .tar.bz2
@@ -167,12 +167,23 @@ do-build:
./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\

do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
-   ${PREFIX}/bin
+   # Libs and includes:
${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
@cd ${WRKSRC} && \
find boost -type d -exec ${INSTALL_DATA_DIR} 
${PREFIX}/include/{} \;
@cd ${WRKSRC} && \
		find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {} 
${PREFIX}/include/{} \;

+   # boost-build:
+   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
+   ${PREFIX}/bin
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
+   @cd ${WRKSRC}/tools/build/src && \
+   pax -r -w -p pm -s ':^./engine.*$$::' \
+   -s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
+   ${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
+   ${PREFIX}/share/examples/boost-build
+   ${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
+   ${PREFIX}/share/boost-build/

.include 
Index: pkg/PLIST-main
===
RCS file: /cvs/ports/devel/boost/pkg/PLIST-main,v
retrieving revision 1.6
diff -u -p -u -p -r1.6 PLIST-main
--- pkg/PLIST-main  13 Dec 2018 19:52:46 -  1.6
+++ pkg/PLIST-main  28 Dec 2018 19:56:59 -
@@ -14160,3 +14160,362 @@ lib/libboost_wserialization-mt.a
@lib lib/libboost_wserialization-mt.so.${LIBboost_wserialization-mt_VERSION}
lib/libboost_wserialization.a
@lib lib/libboost_wserialization.so.${LIBboost_wserialization_VERSION}
+share/boost-build/
+share/boost-build/__init__.py
+share/boost-build/__init__.pyc
+share/boost-build/bootstrap.jam
+share/boost-build/build/
+share/boost-build/build-system.jam
+share/boost-build/build/__init__.py
+share/boost-build/build/__init__.pyc
+share/boost-build/build/ac.jam
+share/boost-build/build/alias.jam
+share/boost-build/build/alias.py
+share/boost-build/build/alias.pyc
+share/boost-build/build/build-request.jam
+share/boost-build/build/build_request.py
+share/boost-build/build/build_request.pyc
+share/boost-build/build/config-cache.jam
+share/boost-build/build/configure.jam
+share/boost-build/build/configure.py
+share/boost-build/build/configure.pyc
+share/boost-build/build/engine.py
+share/boost-build/build/engine.pyc
+share/boost-build/build/errors.py
+share/boost-build/build/errors.pyc
+share/boost-build/build/feature.jam
+share/boost-build/build/feature.py
+share/boost-build/build/feature.pyc
+share/boost-build/build/generators.jam
+share/boost-build/build/generators.py
+share/boost-build/build/generators.pyc
+share/boost-build/build/project.jam
+share/boost-build/build/project.py
+share/boost-build/build/project.pyc
+share/boost-build/build/property-set.jam
+share/boost-build/build/property.jam
+share/boost-build/build/property.py
+share/boost-build/build/property.pyc
+share/boost-build/build/property_set.py
+share/boost-build/build/property_set.pyc

Re: update/fix: devel/boost

2018-12-28 Thread Rafael Sadowski 
On Fri Dec 28, 2018 at 07:04:51PM +, Stuart Henderson wrote:
> On 2018/12/28 19:30, Rafael Sadowski wrote:
> > On Fri Dec 28, 2018 at 02:31:49PM +, Stuart Henderson wrote:
> > > Why subpackage this?
> > 
> > Because nobody needs boost-build to run/build any ports. Let's be
> > unfair, nobody needs boost-build except *maybe* a handful user.
> 
> If it was something huge then it would make sense. But really I don't
> see the point in splitting it, it's got to be pretty small, I haven't
> looked at the size of the new files but I can't imagine the whole thing
> can be more than a MB or so can it? Less if the two identical files
> b2 and bjam were hardlinked together.
> 
> > Doas another subpackge hurts?
> 
> Yes, it's extra scaffolding and extra risk of getting things wrong
> both in the port itself, and in ports which might end up needing it
> in the future.
> 
> I'm not going to insist but I really don't see a good reason to split
> it. But if you are going to split it anyway see comments inline.;
> 

Those are of course good points and it does not have to be for me
necessarily a subpackage. Below a diff without -build subpackage.

package fine for me. OK?

Rafael Sadowski

Index: Makefile
===
RCS file: /cvs/ports/devel/boost/Makefile,v
retrieving revision 1.79
diff -u -p -u -p -r1.79 Makefile
--- Makefile24 Dec 2018 23:34:27 -  1.79
+++ Makefile28 Dec 2018 19:56:58 -
@@ -9,7 +9,7 @@ VERSION=1.66.0
 DISTNAME=  boost_${VERSION:S/./_/g}
 PKGNAME-main=  boost-${VERSION}
 PKGNAME-md=boost-md-${VERSION}
-REVISION-main= 1
+REVISION-main= 2
 CATEGORIES=devel
 MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=boost/}
 EXTRACT_SUFX=  .tar.bz2
@@ -167,12 +167,23 @@ do-build:
./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
-   ${PREFIX}/bin
+   # Libs and includes:
${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
@cd ${WRKSRC} && \
find boost -type d -exec ${INSTALL_DATA_DIR} 
${PREFIX}/include/{} \;
@cd ${WRKSRC} && \
find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {} 
${PREFIX}/include/{} \;
+   # boost-build:
+   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
+   ${PREFIX}/bin
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
+   @cd ${WRKSRC}/tools/build/src && \
+   pax -r -w -p pm -s ':^./engine.*$$::' \
+   -s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
+   ${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
+   ${PREFIX}/share/examples/boost-build
+   ${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
+   ${PREFIX}/share/boost-build/
 
 .include 
Index: pkg/PLIST-main
===
RCS file: /cvs/ports/devel/boost/pkg/PLIST-main,v
retrieving revision 1.6
diff -u -p -u -p -r1.6 PLIST-main
--- pkg/PLIST-main  13 Dec 2018 19:52:46 -  1.6
+++ pkg/PLIST-main  28 Dec 2018 19:56:59 -
@@ -14160,3 +14160,362 @@ lib/libboost_wserialization-mt.a
 @lib lib/libboost_wserialization-mt.so.${LIBboost_wserialization-mt_VERSION}
 lib/libboost_wserialization.a
 @lib lib/libboost_wserialization.so.${LIBboost_wserialization_VERSION}
+share/boost-build/
+share/boost-build/__init__.py
+share/boost-build/__init__.pyc
+share/boost-build/bootstrap.jam
+share/boost-build/build/
+share/boost-build/build-system.jam
+share/boost-build/build/__init__.py
+share/boost-build/build/__init__.pyc
+share/boost-build/build/ac.jam
+share/boost-build/build/alias.jam
+share/boost-build/build/alias.py
+share/boost-build/build/alias.pyc
+share/boost-build/build/build-request.jam
+share/boost-build/build/build_request.py
+share/boost-build/build/build_request.pyc
+share/boost-build/build/config-cache.jam
+share/boost-build/build/configure.jam
+share/boost-build/build/configure.py
+share/boost-build/build/configure.pyc
+share/boost-build/build/engine.py
+share/boost-build/build/engine.pyc
+share/boost-build/build/errors.py
+share/boost-build/build/errors.pyc
+share/boost-build/build/feature.jam
+share/boost-build/build/feature.py
+share/boost-build/build/feature.pyc
+share/boost-build/build/generators.jam
+share/boost-build/build/generators.py
+share/boost-build/build/generators.pyc
+share/boost-build/build/project.jam
+share/boost-build/build/project.py
+share/boost-build/build/project.pyc
+share/boost-build/build/property-set.jam
+share/boost-build/build/property.jam
+share/boost-build/build/property.py
+share/boost-build/build/property.pyc
+share/boost-build/build/property_set.py
+share/boost-build/build/property_set.pyc
+share/boost-build/build/readme.txt
+share/boost-build/build/scanner.jam

Re: update/fix: devel/boost

2018-12-28 Thread Stuart Henderson 
On 2018/12/28 19:30, Rafael Sadowski wrote:
> On Fri Dec 28, 2018 at 02:31:49PM +, Stuart Henderson wrote:
> > Why subpackage this?
> 
> Because nobody needs boost-build to run/build any ports. Let's be
> unfair, nobody needs boost-build except *maybe* a handful user.

If it was something huge then it would make sense. But really I don't
see the point in splitting it, it's got to be pretty small, I haven't
looked at the size of the new files but I can't imagine the whole thing
can be more than a MB or so can it? Less if the two identical files
b2 and bjam were hardlinked together.

> Doas another subpackge hurts?

Yes, it's extra scaffolding and extra risk of getting things wrong
both in the port itself, and in ports which might end up needing it
in the future.

I'm not going to insist but I really don't see a good reason to split
it. But if you are going to split it anyway see comments inline.;

> > -- 
> > Sent from a phone, apologies for poor formatting.
> > 
> > On 28 December 2018 13:41:22 Rafael Sadowski  wrote:
> > 
> > > Hi all!
> > > 
> > > Our boost.build executables b2 and bjam are useless without the *.jam
> > > stuff. The diff below want to fix the situation withe a third
> > > sub-package named "build".
> > > 
> > > do-install bits from NetBSD and DESCR from FreeBSD.
> > > Noticed by Ivan Krylov via openbsd@freenode. Thanks!
> > > 
> > > Comments, OK?
> > > 
> > > Rafael Sadowski
> > > 
> 
> New diff with a compileall.py call at the end of the do-install step,
> after feedback from semarie@ and aja@ Thanks!
> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/devel/boost/Makefile,v
> retrieving revision 1.79
> diff -u -p -u -p -r1.79 Makefile
> --- Makefile  24 Dec 2018 23:34:27 -  1.79
> +++ Makefile  28 Dec 2018 18:18:16 -
> @@ -2,6 +2,7 @@
>  
>  COMMENT-main=free peer-reviewed portable C++ source libraries
>  COMMENT-md=  machine-dependent libraries for boost
> +COMMENT-build=   extensible cross-platform build tool suite
>  
>  # XXX if updating, try to remove -D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR
>  # XXX in archivers/innoextract
> @@ -9,7 +10,8 @@ VERSION= 1.66.0
>  DISTNAME=boost_${VERSION:S/./_/g}
>  PKGNAME-main=boost-${VERSION}
>  PKGNAME-md=  boost-md-${VERSION}
> -REVISION-main=   1
> +PKGNAME-build=   boost-build-${VERSION}
> +REVISION-main=   2
>  CATEGORIES=  devel
>  MASTER_SITES=${MASTER_SITE_SOURCEFORGE:=boost/}
>  EXTRACT_SUFX=.tar.bz2
> @@ -76,7 +78,7 @@ WANTLIB += ${COMPILER_LIBCXX} bz2 c icud
>  
>  COMPILER= base-clang ports-gcc
>  
> -MULTI_PACKAGES=  -main -md
> +MULTI_PACKAGES=  -main -md -build
>  
>  MODULES= lang/python
>  MODPY_RUNDEP=No
> @@ -167,12 +169,22 @@ do-build:
>   ./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\
>  
>  do-install:
> - ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
> - ${PREFIX}/bin
>   ${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
>   @cd ${WRKSRC} && \
>   find boost -type d -exec ${INSTALL_DATA_DIR} 
> ${PREFIX}/include/{} \;
>   @cd ${WRKSRC} && \
>   find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {} 
> ${PREFIX}/include/{} \;
> + # -build
> + ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
> + ${PREFIX}/bin
> + ${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
> + @cd ${WRKSRC}/tools/build/src && \
> + pax -r -w -p pm -s ':^./engine.*$$::' \
> + -s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
> + ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
> + ${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
> + ${PREFIX}/share/examples/boost-build
> + ${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
> + ${PREFIX}/share/boost-build/
>  
>  .include 
> Index: pkg/DESCR-build
> ===
> RCS file: pkg/DESCR-build
> diff -N pkg/DESCR-build
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ pkg/DESCR-build   28 Dec 2018 18:18:16 -
> @@ -0,0 +1,7 @@
> +Boost.Build is an easy way to build C++ projects, everywhere. You name you
> +executables and libraries and list their sources.

"You name *your* executables"...

> +
> +Boost.Build takes care about compiling your sources with right options,

"with the right options"

> +creating static and shared libraries, making executables, and other chores --
> +whether you're using gcc, msvc, or a dozen more supported C++ compilers -- on
> +Windows, OSX, Linux and commercial UNIX systems.
> Index: pkg/PLIST-build
> ===
> RCS file: pkg/PLIST-build
> diff -N pkg/PLIST-build
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ pkg/PLIST-build   28 Dec 2018 18:18:16 -
> @@ -0,0 +1,362 @@
> +@comment

Re: update/fix: devel/boost

2018-12-28 Thread Rafael Sadowski 
On Fri Dec 28, 2018 at 02:31:49PM +, Stuart Henderson wrote:
> Why subpackage this?

Because nobody needs boost-build to run/build any ports. Let's be
unfair, nobody needs boost-build except *maybe* a handful user.

Doas another subpackge hurts?

> -- 
> Sent from a phone, apologies for poor formatting.
> 
> On 28 December 2018 13:41:22 Rafael Sadowski  wrote:
> 
> > Hi all!
> > 
> > Our boost.build executables b2 and bjam are useless without the *.jam
> > stuff. The diff below want to fix the situation withe a third
> > sub-package named "build".
> > 
> > do-install bits from NetBSD and DESCR from FreeBSD.
> > Noticed by Ivan Krylov via openbsd@freenode. Thanks!
> > 
> > Comments, OK?
> > 
> > Rafael Sadowski
> > 

New diff with a compileall.py call at the end of the do-install step,
after feedback from semarie@ and aja@ Thanks!

Index: Makefile
===
RCS file: /cvs/ports/devel/boost/Makefile,v
retrieving revision 1.79
diff -u -p -u -p -r1.79 Makefile
--- Makefile24 Dec 2018 23:34:27 -  1.79
+++ Makefile28 Dec 2018 18:18:16 -
@@ -2,6 +2,7 @@
 
 COMMENT-main=  free peer-reviewed portable C++ source libraries
 COMMENT-md=machine-dependent libraries for boost
+COMMENT-build= extensible cross-platform build tool suite
 
 # XXX if updating, try to remove -D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR
 # XXX in archivers/innoextract
@@ -9,7 +10,8 @@ VERSION=   1.66.0
 DISTNAME=  boost_${VERSION:S/./_/g}
 PKGNAME-main=  boost-${VERSION}
 PKGNAME-md=boost-md-${VERSION}
-REVISION-main= 1
+PKGNAME-build= boost-build-${VERSION}
+REVISION-main= 2
 CATEGORIES=devel
 MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=boost/}
 EXTRACT_SUFX=  .tar.bz2
@@ -76,7 +78,7 @@ WANTLIB += ${COMPILER_LIBCXX} bz2 c icud
 
 COMPILER= base-clang ports-gcc
 
-MULTI_PACKAGES=-main -md
+MULTI_PACKAGES=-main -md -build
 
 MODULES=   lang/python
 MODPY_RUNDEP=  No
@@ -167,12 +169,22 @@ do-build:
./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
-   ${PREFIX}/bin
${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
@cd ${WRKSRC} && \
find boost -type d -exec ${INSTALL_DATA_DIR} 
${PREFIX}/include/{} \;
@cd ${WRKSRC} && \
find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {} 
${PREFIX}/include/{} \;
+   # -build
+   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
+   ${PREFIX}/bin
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
+   @cd ${WRKSRC}/tools/build/src && \
+   pax -r -w -p pm -s ':^./engine.*$$::' \
+   -s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
+   ${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
+   ${PREFIX}/share/examples/boost-build
+   ${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
+   ${PREFIX}/share/boost-build/
 
 .include 
Index: pkg/DESCR-build
===
RCS file: pkg/DESCR-build
diff -N pkg/DESCR-build
--- /dev/null   1 Jan 1970 00:00:00 -
+++ pkg/DESCR-build 28 Dec 2018 18:18:16 -
@@ -0,0 +1,7 @@
+Boost.Build is an easy way to build C++ projects, everywhere. You name you
+executables and libraries and list their sources.
+
+Boost.Build takes care about compiling your sources with right options,
+creating static and shared libraries, making executables, and other chores --
+whether you're using gcc, msvc, or a dozen more supported C++ compilers -- on
+Windows, OSX, Linux and commercial UNIX systems.
Index: pkg/PLIST-build
===
RCS file: pkg/PLIST-build
diff -N pkg/PLIST-build
--- /dev/null   1 Jan 1970 00:00:00 -
+++ pkg/PLIST-build 28 Dec 2018 18:18:16 -
@@ -0,0 +1,362 @@
+@comment $OpenBSD: PLIST-build,v$
+@bin bin/b2
+@bin bin/bjam
+share/boost-build/
+share/boost-build/__init__.py
+share/boost-build/__init__.pyc
+share/boost-build/bootstrap.jam
+share/boost-build/build/
+share/boost-build/build-system.jam
+share/boost-build/build/__init__.py
+share/boost-build/build/__init__.pyc
+share/boost-build/build/ac.jam
+share/boost-build/build/alias.jam
+share/boost-build/build/alias.py
+share/boost-build/build/alias.pyc
+share/boost-build/build/build-request.jam
+share/boost-build/build/build_request.py
+share/boost-build/build/build_request.pyc
+share/boost-build/build/config-cache.jam
+share/boost-build/build/configure.jam
+share/boost-build/build/configure.py
+share/boost-build/build/configure.pyc
+share/boost-build/build/engine.py
+share/boost-build/build/engine.pyc
+share/boost-build/build/errors.py
+share/boost-build/build/errors.pyc
+share/boost-build/build/feature.jam

Re: update/fix: devel/boost

2018-12-28 Thread Stuart Henderson 

Why subpackage this?
--
Sent from a phone, apologies for poor formatting.

On 28 December 2018 13:41:22 Rafael Sadowski  wrote:


Hi all!

Our boost.build executables b2 and bjam are useless without the *.jam
stuff. The diff below want to fix the situation withe a third
sub-package named "build".

do-install bits from NetBSD and DESCR from FreeBSD.
Noticed by Ivan Krylov via openbsd@freenode. Thanks!

Comments, OK?

Rafael Sadowski

Index: Makefile
===
RCS file: /cvs/ports/devel/boost/Makefile,v
retrieving revision 1.79
diff -u -p -u -p -r1.79 Makefile
--- Makefile24 Dec 2018 23:34:27 -  1.79
+++ Makefile28 Dec 2018 10:39:12 -
@@ -2,6 +2,7 @@

COMMENT-main=   free peer-reviewed portable C++ source libraries
COMMENT-md= machine-dependent libraries for boost
+COMMENT-build= extensible cross-platform build tool suite

# XXX if updating, try to remove -D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR
# XXX in archivers/innoextract
@@ -9,7 +10,8 @@ VERSION=   1.66.0
DISTNAME=   boost_${VERSION:S/./_/g}
PKGNAME-main=   boost-${VERSION}
PKGNAME-md= boost-md-${VERSION}
-REVISION-main= 1
+PKGNAME-build= boost-build-${VERSION}
+REVISION-main= 2
CATEGORIES= devel
MASTER_SITES=   ${MASTER_SITE_SOURCEFORGE:=boost/}
EXTRACT_SUFX=   .tar.bz2
@@ -76,7 +78,7 @@ WANTLIB += ${COMPILER_LIBCXX} bz2 c icud

COMPILER= base-clang ports-gcc

-MULTI_PACKAGES=-main -md
+MULTI_PACKAGES=-main -md -build

MODULES=lang/python
MODPY_RUNDEP=   No
@@ -167,12 +169,20 @@ do-build:
./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\

do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
-   ${PREFIX}/bin
${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
@cd ${WRKSRC} && \
find boost -type d -exec ${INSTALL_DATA_DIR} 
${PREFIX}/include/{} \;
@cd ${WRKSRC} && \
		find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {} 
${PREFIX}/include/{} \;

+   # -build
+   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
+   ${PREFIX}/bin
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
+   @cd ${WRKSRC}/tools/build/src && \
+   pax -r -w -p pm -s ':^./engine.*$$::' \
+   -s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
+   ${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
+   ${PREFIX}/share/examples/boost-build

.include 
Index: pkg/DESCR-build
===
RCS file: pkg/DESCR-build
diff -N pkg/DESCR-build
--- /dev/null   1 Jan 1970 00:00:00 -
+++ pkg/DESCR-build 28 Dec 2018 10:39:12 -
@@ -0,0 +1,7 @@
+Boost.Build is an easy way to build C++ projects, everywhere. You name you
+executables and libraries and list their sources.
+
+Boost.Build takes care about compiling your sources with right options,
+creating static and shared libraries, making executables, and other chores --
+whether you're using gcc, msvc, or a dozen more supported C++ compilers -- on
+Windows, OSX, Linux and commercial UNIX systems.
Index: pkg/PLIST-build
===
RCS file: pkg/PLIST-build
diff -N pkg/PLIST-build
--- /dev/null   1 Jan 1970 00:00:00 -
+++ pkg/PLIST-build 28 Dec 2018 10:39:12 -
@@ -0,0 +1,297 @@
+@comment $OpenBSD: PLIST-build,v$
+@bin bin/b2
+@bin bin/bjam
+share/boost-build/
+share/boost-build/__init__.py
+share/boost-build/bootstrap.jam
+share/boost-build/build/
+share/boost-build/build-system.jam
+share/boost-build/build/__init__.py
+share/boost-build/build/ac.jam
+share/boost-build/build/alias.jam
+share/boost-build/build/alias.py
+share/boost-build/build/build-request.jam
+share/boost-build/build/build_request.py
+share/boost-build/build/config-cache.jam
+share/boost-build/build/configure.jam
+share/boost-build/build/configure.py
+share/boost-build/build/engine.py
+share/boost-build/build/errors.py
+share/boost-build/build/feature.jam
+share/boost-build/build/feature.py
+share/boost-build/build/generators.jam
+share/boost-build/build/generators.py
+share/boost-build/build/project.jam
+share/boost-build/build/project.py
+share/boost-build/build/property-set.jam
+share/boost-build/build/property.jam
+share/boost-build/build/property.py
+share/boost-build/build/property_set.py
+share/boost-build/build/readme.txt
+share/boost-build/build/scanner.jam
+share/boost-build/build/scanner.py
+share/boost-build/build/targets.jam
+share/boost-build/build/targets.py
+share/boost-build/build/toolset.jam
+share/boost-build/build/toolset.py
+share/boost-build/build/type.jam
+share/boost-build/build/type.py
+share/boost-build/build/version.jam
+share/boost-build/build/version.py
+share/boost-build/build/virtual-target.jam

update/fix: devel/boost

2018-12-28 Thread Rafael Sadowski 
Hi all!

Our boost.build executables b2 and bjam are useless without the *.jam
stuff. The diff below want to fix the situation withe a third
sub-package named "build".

do-install bits from NetBSD and DESCR from FreeBSD.
Noticed by Ivan Krylov via openbsd@freenode. Thanks!

Comments, OK?

Rafael Sadowski

Index: Makefile
===
RCS file: /cvs/ports/devel/boost/Makefile,v
retrieving revision 1.79
diff -u -p -u -p -r1.79 Makefile
--- Makefile24 Dec 2018 23:34:27 -  1.79
+++ Makefile28 Dec 2018 10:39:12 -
@@ -2,6 +2,7 @@
 
 COMMENT-main=  free peer-reviewed portable C++ source libraries
 COMMENT-md=machine-dependent libraries for boost
+COMMENT-build= extensible cross-platform build tool suite
 
 # XXX if updating, try to remove -D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR
 # XXX in archivers/innoextract
@@ -9,7 +10,8 @@ VERSION=   1.66.0
 DISTNAME=  boost_${VERSION:S/./_/g}
 PKGNAME-main=  boost-${VERSION}
 PKGNAME-md=boost-md-${VERSION}
-REVISION-main= 1
+PKGNAME-build= boost-build-${VERSION}
+REVISION-main= 2
 CATEGORIES=devel
 MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=boost/}
 EXTRACT_SUFX=  .tar.bz2
@@ -76,7 +78,7 @@ WANTLIB += ${COMPILER_LIBCXX} bz2 c icud
 
 COMPILER= base-clang ports-gcc
 
-MULTI_PACKAGES=-main -md
+MULTI_PACKAGES=-main -md -build
 
 MODULES=   lang/python
 MODPY_RUNDEP=  No
@@ -167,12 +169,20 @@ do-build:
./b2 ${BJAM_CONFIG} python=${MODPY_DEFAULT_VERSION_3}\
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
-   ${PREFIX}/bin
${INSTALL_DATA} ${WRKSRC}/stage/lib/lib!(*.so) ${PREFIX}/lib
@cd ${WRKSRC} && \
find boost -type d -exec ${INSTALL_DATA_DIR} 
${PREFIX}/include/{} \;
@cd ${WRKSRC} && \
find boost ! -name \*.orig -type f -exec ${INSTALL_DATA} {} 
${PREFIX}/include/{} \;
+   # -build
+   ${INSTALL_PROGRAM} ${WRKSRC}/tools/build/src/engine/bin.*/{b2,bjam} \
+   ${PREFIX}/bin
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/boost-build
+   @cd ${WRKSRC}/tools/build/src && \
+   pax -r -w -p pm -s ':^./engine.*$$::' \
+   -s ':^.*\.orig$$::' . ${PREFIX}/share/boost-build
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/boost-build
+   ${INSTALL_DATA} ${WRKSRC}/tools/build/example/site-config.jam \
+   ${PREFIX}/share/examples/boost-build
 
 .include 
Index: pkg/DESCR-build
===
RCS file: pkg/DESCR-build
diff -N pkg/DESCR-build
--- /dev/null   1 Jan 1970 00:00:00 -
+++ pkg/DESCR-build 28 Dec 2018 10:39:12 -
@@ -0,0 +1,7 @@
+Boost.Build is an easy way to build C++ projects, everywhere. You name you
+executables and libraries and list their sources.
+
+Boost.Build takes care about compiling your sources with right options,
+creating static and shared libraries, making executables, and other chores --
+whether you're using gcc, msvc, or a dozen more supported C++ compilers -- on
+Windows, OSX, Linux and commercial UNIX systems.
Index: pkg/PLIST-build
===
RCS file: pkg/PLIST-build
diff -N pkg/PLIST-build
--- /dev/null   1 Jan 1970 00:00:00 -
+++ pkg/PLIST-build 28 Dec 2018 10:39:12 -
@@ -0,0 +1,297 @@
+@comment $OpenBSD: PLIST-build,v$
+@bin bin/b2
+@bin bin/bjam
+share/boost-build/
+share/boost-build/__init__.py
+share/boost-build/bootstrap.jam
+share/boost-build/build/
+share/boost-build/build-system.jam
+share/boost-build/build/__init__.py
+share/boost-build/build/ac.jam
+share/boost-build/build/alias.jam
+share/boost-build/build/alias.py
+share/boost-build/build/build-request.jam
+share/boost-build/build/build_request.py
+share/boost-build/build/config-cache.jam
+share/boost-build/build/configure.jam
+share/boost-build/build/configure.py
+share/boost-build/build/engine.py
+share/boost-build/build/errors.py
+share/boost-build/build/feature.jam
+share/boost-build/build/feature.py
+share/boost-build/build/generators.jam
+share/boost-build/build/generators.py
+share/boost-build/build/project.jam
+share/boost-build/build/project.py
+share/boost-build/build/property-set.jam
+share/boost-build/build/property.jam
+share/boost-build/build/property.py
+share/boost-build/build/property_set.py
+share/boost-build/build/readme.txt
+share/boost-build/build/scanner.jam
+share/boost-build/build/scanner.py
+share/boost-build/build/targets.jam
+share/boost-build/build/targets.py
+share/boost-build/build/toolset.jam
+share/boost-build/build/toolset.py
+share/boost-build/build/type.jam
+share/boost-build/build/type.py
+share/boost-build/build/version.jam
+share/boost-build/build/version.py
+share/boost-build/build/virtual-target.jam
+share/boost-build/build/virtual_target.py
+share/boost-build/build_system.py
+share/boost-build/contrib/

Re: fix: devel/boost

2016-02-15 Thread Tobias Ulmer 
On Mon, Feb 15, 2016 at 08:51:34PM +, Christian Weisgerber wrote:
> On 2016-02-15, Tobias Ulmer  wrote:
> 
> > +padding for 32bit strict alignment archs
> > +
> > +--- tools/build/src/engine/hash.c.orig Mon Feb 15 20:11:07 2016
> >  tools/build/src/engine/hash.c  Mon Feb 15 20:22:03 2016
> > +@@ -33,6 +33,7 @@ typedef struct item ITEM;
> > + struct item
> > + {
> > + ITEM * next;
> > ++char padding[sizeof(long long)-sizeof(ITEM *)];
> > + };
> 
> Urgh.  sparc, as a 32-bit arch, enforces 64-bit alignment for 64-bit
> data types?

Yes, LDD and STD 'trap if the address is not doubleword-aligned' to
quote the SPARCv8 manual.

> 
> -- 
> Christian "naddy" Weisgerber  na...@mips.inka.de
>

Re: fix: devel/boost

2016-02-15 Thread Christian Weisgerber 
On 2016-02-15, Tobias Ulmer  wrote:

> +padding for 32bit strict alignment archs
> +
> +--- tools/build/src/engine/hash.c.orig   Mon Feb 15 20:11:07 2016
>  tools/build/src/engine/hash.cMon Feb 15 20:22:03 2016
> +@@ -33,6 +33,7 @@ typedef struct item ITEM;
> + struct item
> + {
> + ITEM * next;
> ++char padding[sizeof(long long)-sizeof(ITEM *)];
> + };

Urgh.  sparc, as a 32-bit arch, enforces 64-bit alignment for 64-bit
data types?

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

fix: devel/boost

2016-02-15 Thread Tobias Ulmer 
Fix 'jam' so it doesn't crash immediately on sparc.

While debugging I found file_query wasn't declared, which is nice since
it returns a pointer. Surprised this works at all on 64 bit machines,
I'm guessing it's because of -O0.

More sparc fixes may be coming, or I may mark the thing as BROKEN, we
shall see. I'm just putting it out there so you can see what's cooking.

diff --git a/devel/boost/Makefile b/devel/boost/Makefile
index 5f69adb..6f04d78 100644
--- a/devel/boost/Makefile
+++ b/devel/boost/Makefile
@@ -5,7 +5,7 @@ ONLY_FOR_ARCHS= ${GCC4_ARCHS}
 COMMENT=   free peer-reviewed portable C++ source libraries
 
 VERSION=   1.58.0
-REVISION=  0
+REVISION=  1
 DISTNAME=  boost_${VERSION:S/./_/g}
 PKGNAME=   boost-${VERSION}
 CATEGORIES=devel
diff --git a/devel/boost/patches/patch-tools_build_src_engine_hash_c 
b/devel/boost/patches/patch-tools_build_src_engine_hash_c
new file mode 100644
index 000..ea923e1
--- /dev/null
+++ b/devel/boost/patches/patch-tools_build_src_engine_hash_c
@@ -0,0 +1,14 @@
+$OpenBSD$
+
+padding for 32bit strict alignment archs
+
+--- tools/build/src/engine/hash.c.orig Mon Feb 15 20:11:07 2016
 tools/build/src/engine/hash.c  Mon Feb 15 20:22:03 2016
+@@ -33,6 +33,7 @@ typedef struct item ITEM;
+ struct item
+ {
+ ITEM * next;
++char padding[sizeof(long long)-sizeof(ITEM *)];
+ };
+ 
+ #define MAX_LISTS 32
diff --git a/devel/boost/patches/patch-tools_build_src_engine_modules_path_c 
b/devel/boost/patches/patch-tools_build_src_engine_modules_path_c
new file mode 100644
index 000..4a9a952
--- /dev/null
+++ b/devel/boost/patches/patch-tools_build_src_engine_modules_path_c
@@ -0,0 +1,14 @@
+$OpenBSD$
+
+fix implicit declaration of function 'file_query' for LP64 archs
+
+--- tools/build/src/engine/modules/path.c.orig Mon Feb 15 19:25:09 2016
 tools/build/src/engine/modules/path.c  Mon Feb 15 19:25:34 2016
+@@ -6,6 +6,7 @@
+ 
+ #include "../constants.h"
+ #include "../frames.h"
++#include "../filesys.h"
+ #include "../lists.h"
+ #include "../native.h"
+ #include "../timestamp.h"

FIX devel/boost

2010-09-19 Thread Markus Hennecke 
OpenBSD does not have the definitions for the signals SI_ASYNCIO and
SI_MESGQ. With this, the tests for wt (www.webtoolkit.eu, still work in
progress) compiles.

Kind regards
  Markus
Index: Makefile
===
RCS file: /cvs/ports/devel/boost/Makefile,v
retrieving revision 1.26
diff -u -p -r1.26 Makefile
--- Makefile30 Aug 2010 22:03:58 -  1.26
+++ Makefile19 Sep 2010 07:21:11 -
@@ -3,7 +3,7 @@
 COMMENT=   free peer-reviewed portable C++ source libraries
 
 PKGNAME=   boost-${VERSION}
-REVISION=  4
+REVISION=  5
 
 VERSION=   1.42.0
 DISTNAME=  boost_${VERSION:S/./_/g}
Index: patches/patch-boost_test_impl_execution_monitor_ipp
===
RCS file: patches/patch-boost_test_impl_execution_monitor_ipp
diff -N patches/patch-boost_test_impl_execution_monitor_ipp
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-boost_test_impl_execution_monitor_ipp 19 Sep 2010 07:21:11 
-
@@ -0,0 +1,19 @@
+$OpenBSD$
+--- boost/test/impl/execution_monitor.ipp.orig Sun Sep 19 09:16:17 2010
 boost/test/impl/execution_monitor.ipp  Sun Sep 19 09:16:41 2010
+@@ -341,6 +341,7 @@ system_signal_exception::report() const
+ report_error( execution_exception::system_error,
+   signal: the expiration of a timer set by 
timer_settimer() );
+ break;
++#if !defined(__OpenBSD__)
+ case SI_ASYNCIO:
+ report_error( execution_exception::system_error,
+   signal: generated by the completion of an asynchronous 
I/O request );
+@@ -349,6 +350,7 @@ system_signal_exception::report() const
+ report_error( execution_exception::system_error,
+   signal: generated by the the arrival of a message on 
an empty message queue );
+ break;
++#endif
+ default:
+ break;
+ }