Package Details: boost-build-nightly 20140102-2

Git Clone URL: https://aur.archlinux.org/boost-build-nightly.git (read-only)
Package Base: boost-build-nightly
Description: Boost build system, Nightly build
Upstream URL: http://www.boost.org/doc/tools/build/
Licenses: custom:boost
Conflicts: boost, boost-build
Submitter: ytj
Maintainer: marcs
Last Packager: marcs
Votes: 3
Popularity: 0.002785
First Submitted: 2011-04-23 03:11
Last Updated: 2016-02-29 11:03

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

marcs commented on 2016-02-29 10:57

Hi snork,

Makes no sense to remove those two files. If you want to use the boost official package versions of b2 or bjam, you should keep using the official package (boost).

But makes sense to insert boost in the conflict array. Some time ago b2 and bjam were not present inside the boost official package.

Thanks for noticing.

M

snork commented on 2016-02-21 09:15

Fixed file conflict with boost package on files `b2` and `bjam` by adding

rm ${pkgdir}/usr/bin/b2
rm ${pkgdir}/usr/bin/bjam

after
/b2 install --prefix=${pkgdir}/usr

zoidberg_md commented on 2014-09-19 15:49

$ namcap boost-build-nightly/boost-build-nightly-20140102-1-any.pkg.tar.xz
boost-build-nightly E: ELF file ('usr/share/boost-build/b2') outside of a valid path.
boost-build-nightly E: ELF file ('usr/share/boost-build/b2') found in an 'any' package.
boost-build-nightly E: ELF file ('usr/bin/b2-nightly') found in an 'any' package.

Basically, the package can't be `any`, because it has architecture-dependent b2-nightly binary.

I used the following patch. I think I missed the point completely. Is there another package I need in addition to this one so I can use boost-build? Is there any reason not to run ./b2 install?

--- boost-build-nightly/PKGBUILD 2014-01-03 16:16:28.000000000 +0200
+++ boost-build-nightly.fixed/PKGBUILD 2014-09-19 18:43:28.451194034 +0300
@@ -5,10 +5,10 @@
pkgver=20140102
pkgrel=1
pkgdesc="Boost build system, Nightly build"
-arch=('any')
+arch=('i686' 'x86_64')
url="http://www.boost.org/doc/tools/build/"
license=('custom:boost')
-depends=('lib32-glibc' 'python')
+depends=('python')
conflicts=('boost-build')
source=("http://www.boost.org/LICENSE_1_0.txt")
md5sums=('e4224ccaecb14d942c71d31bef20d78c')
@@ -47,5 +47,7 @@

cd build
sh bootstrap.sh
- install -D -m755 b2 ${pkgdir}/usr/bin/b2-nightly
+ ./b2 install --prefix=${pkgdir}/usr
+ rm ${pkgdir}/usr/share/boost-build/b2
+ rm ${pkgdir}/usr/bin/bjam
}

ytj commented on 2014-01-14 05:00

I am the submitter and I am pretty sure that I did not add lib32-glibc and python in depends array. Actually the origin dependency should be "depends=('boost')" IIRC.

marcs commented on 2014-01-14 00:09

Strange, i don't have this problem, are you sure that is related to lib32-glibc ?

I've adopted this package so for now i don't know for sure, but also namcap requires lib32-glibc as dependency.

So for now i'm keeping it.

carneiro commented on 2014-01-13 23:38

Why does it depend on lib32-glibc ? I couldn't build because of that, and I simply removed it from the dependencies and it works like a charm.

marcs commented on 2014-01-05 01:32

Because it's a nightly build. Same concept that you are using for your packages based on git. Validation can go south every day.

schuay commented on 2014-01-04 10:05

Why are you downloading the source manually instead of simply using source=()?

matsic commented on 2012-05-29 14:58

user-config.jam contains line
using qt : /Users/asydorchuk/Downloads/Qt ;

it's boost-build bug i think.
may be we should check that all non empty lines are comments in this file when install. Or may be just clear the file.

ytj commented on 2012-05-29 14:15

I removed boost-build-config from this package, backup /etc/site-config.jam before upgrade.

matsic commented on 2012-05-28 08:07

Please add b2 program to your package.
Invoking bjam from boost package we can get some warnings:
<<<
warning: mismatched versions of Boost.Build engine and core
warning: Boost.Build engine (bjam) is 2011.04.00
warning: Boost.Build core (at /usr/share/boost-build) is 2011.12-svn
>>>

matsic commented on 2012-04-12 16:48

It will be good if your boost-build auto configuration tool become a separate project. So it can be used for original boost-build package.

matsic commented on 2012-04-12 16:44

You can put in site-config.jam
"using qt : /usr ;"

You can test qt instalation with "pacman -Qq qt"

ytj commented on 2012-03-14 19:26

@matsic

About your another request, add "using gcc : makepkg : : ..." to site-config.jam
I don't think this is a good idea. Why don't you just write this:

build(){
cd "$srcdir/$pkgname-$pkgver"
bjam release cxxflags="${CXXFLASG}" # ...
}

AFAIK, only few package uses boost build (boost-libs, for example).
You can just write it by hands.

ytj commented on 2012-03-14 19:02

@matsic

Since I don't use qt, you can write a patch for boost-build-config,
or just tell me how to add qt to site-config.jam:

1. How to test if Qt is already installed. ("pacman -Qq qt" maybe?)
2. What should I put into site-config.jam? (Should I just append "using qt ;"?)

matsic commented on 2012-03-14 16:47

please add qt auto configuration in boost-build-config script

matsic commented on 2012-03-14 16:35

using gcc ;
# we can write this lines by hands or may be they can be generated from makepkg.conf
GCC_MAKEPKG_COMPILE_FLAGS = "-march=native -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" ;
GCC_MAKEPKG_LINK_FLAGS = "-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu" ;
using gcc : makepkg : : <cflags>$(GCC_MAKEPKG_COMPILE_FLAGS) <cxxflags>$(GCC_MAKEPKG_COMPILE_FLAGS) <linkflags>$(GCC_MAKEPKG_LINK_FLAGS) ;

# above lines can be added in 'site-config.jam' or user-config.jam

if some pakage builds with bjam, then we can write in build() function in PKGBUILD file:
build(){
cd "$srcdir/$pkgname-$pkgver"
bjam toolset=gcc-makepkg release
}

and we can use user's compilation flags for this

matsic commented on 2012-03-14 16:20

using gcc ;
# we can write this lines by hands or may be they can be generated from makepkg.conf
GCC_MAKEPKG_COMPILE_FLAGS = "-march=native -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2" ;
GCC_MAKEPKG_LINK_FLAGS = "-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu" ;
using gcc : makepkg : : <cflags>$(GCC_MAKEPKG_COMPILE_FLAGS) <cxxflags>$(GCC_MAKEPKG_COMPILE_FLAGS) <linkflags>$(GCC_MAKEPKG_LINK_FLAGS) ;

# above lines can be added in 'site-config.jam'

if some pakage builds with bjam, then we can write in build() function in PKGBUILD file:
build(){
cd "$srcdir/$pkgname-$pkgver"
bjam toolset=gcc-makepkg release
}

and we can use user's compilation flags for this

ytj commented on 2012-03-14 15:17

@matsic Fixed.

ytj commented on 2012-03-14 15:17

@matsic fixed

matsic commented on 2012-03-14 15:01

boost-build-nightly should provide boost-build