Package Details: mingw-w64-boost 1.83.0-1

Git Clone URL: https://aur.archlinux.org/mingw-w64-boost.git (read-only, click to copy)
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: 19
Popularity: 0.000000
First Submitted: 2012-03-22 18:46 (UTC)
Last Updated: 2023-09-03 19:55 (UTC)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

Martchus commented on 2021-06-12 18:59 (UTC)

That was very fast, thank you!

Martchus commented on 2021-06-12 18:42 (UTC)

Hi, can you apply https://patch-diff.githubusercontent.com/raw/boostorg/process/pull/181.patch ?

gerum100 commented on 2021-05-18 21:30 (UTC)

Download servers have changed: https://www.boost.org/users/news/boost_has_moved_downloads_to_jfr.html

xantares commented on 2019-11-29 18:46 (UTC)

yes, sorry I did not test fully

an env package is a good idea, I'll try soon

Martchus commented on 2019-11-29 12:56 (UTC)

This needs linkflags="-Wl,-O1,--sort-common,--as-needed -fstack-protector" \ similar to the other packages. And is everything within the package() function intentionally?

Maybe we should have a package like https://aur.archlinux.org/packages/android-environment for mingw-w64 as well. That would be better than hard coding the flags into mingw-w64-configure, mingw-w64-cmake, mingw-w64-meson, mingw-w64-qt5-base, mingw-w64-boost and possibly even more.

grandchild commented on 2019-03-07 15:44 (UTC)

@Martchus: That was it, thank you! Sorry for the noise.

Martchus commented on 2019-03-06 13:39 (UTC)

Are you already using the recently patched version of https://aur.archlinux.org/packages/mingw-w64-gcc/ ?

grandchild commented on 2019-03-06 13:28 (UTC) (edited on 2019-03-06 13:30 (UTC) by grandchild)

I can't build the current version, tried on 3 different machines.

Always get the same error: https://pastebin.com/raw/h15uB9PF

I also disabled 32bit, same error on 64bit, for what it's worth.

xantares commented on 2018-12-26 10:37 (UTC)

I used "MAKEFLAGS -l0" as a workaround.

Hagar commented on 2018-12-25 23:21 (UTC)

The boost build does not honour MAKEFLAGS properly. It misinterprets -l4 as a time limit to compile, when in fact it is a message to the make command to limit the number of processes to use.

eg. -j10 -l4 - means - use a max of 10 processes with a max system load of 4. Boost interprets this to mean use a max of 4 seconds for each compile.

Can you please use - export MAKEFLAGS=-j$(nproc) to make sure that the -l flag is removed.

I only build in a clean makechrootpkg

1 2 3 4 5 6 7 Next › Last »