Boost 1.71 fails to build: Failed to build Boost.Build build engine on Tiger Intel

[programmingkidx]

When trying to build Boost I see this error: Failed to build Boost.Build build engine

I'm using Mac OS 10.4.11 (x86).

Here is some info that might help:

:debug:configure CC='/opt/local/bin/clang-mp-3.4'
:debug:configure CC_PRINT_OPTIONS='YES'
:debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_boost/boost/work/.CC_PRINT_OPTIONS'
:debug:configure CFLAGS='-pipe -Os -arch i386'
:debug:configure CPATH='/opt/local/include'
:debug:configure CPPFLAGS='-I/opt/local/include'
:debug:configure CXX='/opt/local/bin/clang++-mp-3.4'
:debug:configure CXXFLAGS='-pipe -Os -std=gnu++11 -stdlib=macports-libstdc++ -D_GLIBCXX_USE_CXX11_ABI=0 -arch i386'
:debug:configure DEVELOPER_DIR='/Developer'
:debug:configure F90FLAGS='-pipe -Os -m32'
:debug:configure FCFLAGS='-pipe -Os -m32'
:debug:configure FFLAGS='-pipe -Os -m32'
:debug:configure INSTALL='/usr/bin/install -c'
:debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -arch i386'
:debug:configure LIBRARY_PATH='/opt/local/lib'
:debug:configure MACOSX_DEPLOYMENT_TARGET='10.4'
:debug:configure OBJC='/opt/local/bin/clang-mp-3.4'
:debug:configure OBJCFLAGS='-pipe -Os -arch i386'
:debug:configure OBJCXX='/opt/local/bin/clang++-mp-3.4'
:debug:configure OBJCXXFLAGS='-pipe -Os -std=gnu++11 -stdlib=macports-libstdc++ -D_GLIBCXX_USE_CXX11_ABI=0 -arch i386'

[kencu (Ken)]

what you got here is yet another example of 59584, which I would fix if I thought it might get committed.

Perhaps I will go through the effort of writing up the PR...

[kencu (Ken)]

For now, base defaults to choosing an inappropriate version of clang on < 10.6. Only clangs >= 3.8 understand -stdib=macports-libstdc++ (and that's my special 3.8 from TigerPorts, as macports doesn't have clang-3.8 anymore).

To make it build on 10.4 Intel you could use TigerPorts to install clang-3.8 or clang-5.0 or clang-7.0, or you could try forcing gcc7 like this -- I haven't tried it recently, so it might or might not work:

sudo port -v install boost configure.compiler=macports-gcc-7

[programmingkidx]

You saved the day again. The command worked.

Mac OS 10.4 should have its own place to store binaries of packages for quicker and easier installation. Mac OS 10.6 and higher already has this. I would totally be willing to upload to that server all the ports I have built. Please let me know if there is anything more I could do to help with MacPorts.

I'm not sure if you have clang 3.8 still on your system but if you do, could you make a .dmg installer for it? It would make things easier.

Thank you.

[ryandesign (Ryan Carsten Schmidt)]

I have two Power Mac G5s, one of which was building our 10.5 ppc archives and the other which I was going to set up to build 10.4 ppc archives, but then the power supply on the first one died, so if I set up the second one it will be to resume building 10.5 ppc archives.

I have no plans to add 10.4-10.5 i386 builders because there's no reason why you couldn't upgrade to 10.6 for which we already have archives.

[programmingkidx]

Because I really like Mac OS 10.4 :)

[kencu (Ken)]

I just tweaked my TigerPorts repo for clang-3.8, to make it use cmake-bootstrap. So it should work for you. I just used it to build clang-3.8 on my 10.4 Intel VM and it went without a hitch... so please give it a try.

If you have the TigerPorts repo in your sources, sudo port -v install clang-3.8 should install it for you.

MacPorts will not automatically use it, so you have to force it when you want it, as above.

I'll consider how we might make archives available. It can't be directly in the macports ecosystem, if we do it, but there are ways.

I'm impressed with your enthusiasm, and I hope you leverage all this knowledge you're gathering to contribute to MacPorts further in the future. MacPorts is -- I believe -- by far the most powerful and versatile package manager system for macOS available, but in exchange for that power, the learning curve is steeper than alternative systems.

[programmingkidx]

This is how my sources.conf file looks like now:

file:///Users/Shared/TigerPorts
rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default]
file:///opt/tenfourfox-macports

What do I need to add to the file to use your TigerPorts repo?

[kencu (Ken)]

that should do it, assuming those are the locations where you checked out the repos. You can disable either or both of those in a few seconds with a "#".

What you're doing here is advanced -- you will learn the intricacies of MacPorts much more quickly than average doing this -- but if you ever get stuck, before you open any tickets, first make sure to do a port file XYZ to make sure you know exactly where a given port is coming from.

Please try not to open tickets about things that are or might be related to TigerPorts in the macports trac system. The MacPorts admins are and have been quite accepting of helping keep older systems going, exactly to support enthusiastic new people like you joining into the project, but it has a definite limit and we don't want to find out where that limit is. That will only happen if we're suitably reasonable about things.

If you have a question about TigerPorts that you can't figure out, email me first. My hope is that steadily TigerPorts will disappear and anything useful will be carefully melded back into MacPorts.

[programmingkidx]

Thank you again for all your help. I did run 'sudo port -v install clang-3.8', but was told it was not found.

I ran 'port file clang-3.8' and saw this error: Error: Port clang-3.8 not found

[kencu (Ken)]

most likely no index yet.

make sure there is actually a repo at /Users/Shared/TigerPorts

go in there and generate an index

cd /Users/Shared/TigerPorts
portindex

then try again. if you still see no clang-3.8, check your sources.conf carefully again, as the process does work.

[kencu (Ken)]

the portindex will be updated every time you run sudo port sync in the future.

I put all my repos in /opt, but /Users/Shared should work too.