Package Details: mingw-w64-boost 1.70.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: 21
Popularity: 1.344735
First Submitted: 2012-03-22 18:46
Last Updated: 2019-04-13 05:37

Latest Comments

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

ekpyron commented on 2012-09-06 06:02

@naelstrof
Hm - strange. For me both versions, the one here and the one you uploaded, work without problems. Could you do some testing as to figure out what exactly makes the difference for you? I think the problem must be one of the following:
* you use "unset LDFLAGS" - if this is the cause of your problem, it's likely that you have a modified /etc/makepkg.conf that prevents the build from succeeding.
* you use "threading=single", I use "threading=multi" - I'd rather not want to change that. If that's the cause for your problem, we should report the problem upstream, as I think that would likely mean there's an issue in boost.
* you use "using gcc : mingw64 : ${_arch}-g++" and thus "toolset=gcc-mingw64" - I use "using gcc : 4.7 : ${_arch_target32}-g++" and thus "toolset=gcc" - I think this is actually meant to be used like I do (or at least work both ways), but if this causes the problem for you it's no problem to change the PKGBUILD accordingly.
* I don't think that "using mpi;" makes any difference.
Apart from that your PKGBUILD seems to do pretty much the same as mine. If you were so kind as to check which of these point(s) allow you to compile the package and which prevent you from doing so, I'll happily adjust the PKGBUILD accordingly.

@Schala
Could you try the PKGBUILD naelstrof posted, as to check whether this solves your problem as well?

naelstrof commented on 2012-09-06 02:38

For whatever reason I couldn't compile it properly either, I adjusted the PKGBUILD till it worked for me. You can find it here for whoever needs it:
http://farmpolice.com/content/texts/mingw-w64-boost

Schala commented on 2012-08-15 03:15

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

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

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

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

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

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

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

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.