So we got a building, working boost now. What I did was fairly stupid: simply copy the gcc autoconfig configuration, and use it for now. We can always activate the remaining stuff afterwards.
While running boost, I found two issues: - excessive warnings, because boost hardcode __attribute__((unused)) wrongly. - no autodetection of threads, which was easy to fix. Now a lot of ports are actually building. There's still some nonsense to fix in ports that don't like clang because suddenly, /usr/local is not in their path. Spotlight on some remaining failures: - the clang/ld bug wrt variables that share the same name as a library. That one really needs fixing. - asterisk wants BlockRuntime instead of nested functions. - a few languages (luajit, objc) require unwinder support closer to gcc's runtime - other languages just fail, there are quite a few. Most notable are go and mono - bad compiler flags in the middle of a hugeeee toolchain (ming, libreoffice, chromium, iridium, other gcc derivatives). Ardour is still annoying me even though I fixed a few things. I understand why people hate scons... - there's some fairly ancient C++ that doesn't use the same libraries we do. Some of this might require a bit of boost's help (single linked lists) or may have to do eventually. - there are a few trivial fixes I haven't done yet (mostly a few games with wrong returns or missing prototypes) - there are some bizarre errors I have no idea about. One port does try to build its own copy of libsup++, for instance ? Bottom-line is, in a few days, there will be no trivial fixes left, but only stuff that really require some people to look at things. Now, this is just some build report... If I fix libreoffice, I'll probably have enough pieces so that I can start actually running this stuff.
