Package Details: mingw-w64-boost 1.60.0-1

Git Clone URL: https://aur.archlinux.org/mingw-w64-boost.git (read-only)
Package Base: mingw-w64-boost
Description: Free peer-reviewed portable C++ source libraries (mingw-w64)
Upstream URL: http://www.boost.org/
Licenses: custom
Submitter: ekpyron
Maintainer: xantares
Last Packager: xantares
Votes: 12
Popularity: 0.027101
First Submitted: 2012-03-22 18:46
Last Updated: 2015-12-24 08:02

Latest Comments

xantares commented on 2015-05-18 10:29

@Pse, thanks added it, I guess the error appears from the mingw-gcc 5.1 update

travnick commented on 2015-05-17 18:23

Can not build 1.58:

common.copy [...]/mingw-w64-boost/pkg/mingw-w64-boost/usr/i686-w64-mingw32/lib/libboost_wave-mt.a
...failed updating 6 targets...
...skipped 13 targets...
...updated 12666 targets...

silverhammermba commented on 2015-05-15 21:40

Where do you define that? I tried adding -D compiler flags but the build still fails for me.

Pse commented on 2015-05-15 19:39

I had to add the following definitions for Boost to compile on my 64-bit system:

BOOST_NO_CXX11_CHAR16_T
BOOST_NO_CXX11_CHAR32_T

xantares commented on 2015-04-29 07:47

@schala: i cant update 1.58 just yet; the coroutine lib does not build because of a symbol problem in boost.context

xantares commented on 2014-11-20 12:45

hi,
could you use the right mingw flags (https://wiki.archlinux.org/index.php/MinGW_package_guidelines):
cxxflags=-std=c++11 \
-->
cxxflags="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4" \
(is -std=c++11 flag still necessary ? the core package doesn't have that)
xan.

ekpyron commented on 2014-09-28 18:09

@applesauce

Could you be more specific about error messages, etc.? It should build on x86_64 without any changes. Note that yaourt usually compiles packages in /tmp and boost needs a lot of space, so you need a lot of RAM for that to work - "yaourt --tmp /some/directory/on/disk/ -S mingw-w64-boost" should work, if that's the problem.

applesauce commented on 2014-09-28 05:53

When I tried installing this on an x86_64 system, yaourt told me that the installation failed. Do I need to change anything in the PKGBUILD?

ekpyron commented on 2014-09-09 22:05

@xantares

The reason was that there were some differences between the architectures anyways in earlier versions. Still now the correct address-model=[32|64] must be specified, but you're right - it makes sense to combine the code for the architectures, so I updated the PKGBUILD accordingly.

xantares commented on 2014-09-09 13:58

why dont you use an arch list loop:

_architectures = "i686-... x86_64-..."
for _arch in ${_architectures}; do
mkdir -p build-${_arch} && pushd build-${_arch}
...

package code would be twice shorter


All comments