Package Details: mingw-w64-boost 1.86.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: 2024-09-02 20:58 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Schala commented on 2012-08-15 03:15 (UTC)

It just occurred to me that perhaps I have a malformed system setting. I recall the time that hardly anything would build for me and it turns out the thing I had to do was set my system LOCALE. However, I wonder what the problem is this time...

Schala commented on 2012-08-10 10:39 (UTC)

For some odd reason, some packages fail in mingw-w64 64 32-bit wwhereas they build in mingw32. I think fontconfig is one of them.

ekpyron commented on 2012-08-09 16:53 (UTC)

Well, first of all we'd need mingw-w64-gcc in [community] - it has 9 out of 10 votes that are mentioned to be required for an inclusion in [community], so yes, hopefully things will move in that direction soon - it will make things easier indeed (I'd even consider mingw32 deprecated then as mingw-w64 can compile both 32 and 64 bit).

Schala commented on 2012-08-09 15:17 (UTC)

Yeah, bjam is a nightmare to comprehend. I don't urgently need this, but I cast my vote in hopes this'll make it into [community] or something and save me a headache when I do need it.

ekpyron commented on 2012-08-09 09:09 (UTC)

Yes, that was what I meant, but my guess is still that for some strange reason bjam on your system doesn't use the right version of g++... as it worked on every system with a clean new mingw-w64 I tried it on, I recommend that you remove and then reinstall your whole mingw-w64 (i.e. not only mingw-w64-gcc, but also mingw-w64-binutils, mingw-w64-winpthreads, etc.) and see whether the problem remains (sometimes updating only mingw-w64-gcc without rebuilding all the other packages from scratch breakes things). Also check if the normal boost on your system is up to date. If you urgently need this package I put a pre-compiled version online at https://ekpyron.org/mingw-w64-boost.pkg.tar.xz (install with "pacman -U [path to downloaded file]"). I'm sorry that I can't help you further, but I'm not an expert in regards to the boost build system myself (I always found this whole bjam-stuff to be quite a bit crappy...) and without being able to reproduce your problem, I can't do much more.

Schala commented on 2012-08-09 05:30 (UTC)

Well, I copied and pasted the whole thing into the following file. Sorry if it's not what you meant, but if you want to see where the error occurs, look to the very bottom. http://dl.dropbox.com/u/62535551/output.txt

ekpyron commented on 2012-08-09 04:04 (UTC)

Not surprising that it also happened with mingw32 as I took the PKGBUILD from there (with only minor modifications)... Maybe I could help you if you gave me the full build messages and not only the final error message - as I said, I think for some reason bjam tries to use the wrong version of g++... what's strange is that I just set up a fresh 64-bit arch system recently and I don't have the problem, so I think there is most likely something strange going on with your system (whatever that could be)...

Schala commented on 2012-08-09 02:33 (UTC)

64-bit, and no it doesn't unfortunately. mingw-w64-gcc is up to date. The same error happened with mingw32 as well, so... I have no clue what's going on.

ekpyron commented on 2012-08-09 01:47 (UTC)

Are you sure your mingw-w64-gcc is up to date and working correctly? x86_64-w64-mingw32-g++ and i686-w64-mingw32-g++ do recognize the '-mthreads' option - it appears that for some reason on your system the boost build system tries to use the normal g++ instead of the mingw-w64 version... Are you on a 32-bit or a 64-bit system? It's difficult to fix the problem without being able to reproduce it... Does it work if you change the version number in the PKGBUILD back to 1.49.0 (there haven't been any changes in the PKGBUILD apart from updating the version number)?

Schala commented on 2012-08-09 00:19 (UTC)

I got the following error about a dozen times: g++: error: unrecognized command line option ‘-mthreads’

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »