llvm-3.0 build failure (with Tiger on PowerPC/G4)

[darylew@…]

I wanted to try clang-3.0 on my PowerPC/G4 system (August-2002 eMac) running Mac OS X 10.4.11 Tiger. It choked while building one of its dependencies: llvm-3.0. The end of the process had:

...
--->  Building llvm-3.0
Error: Target org.macports.build returned: shell command failed (see log for details)
Error: Failed to install llvm-3.0
Log for llvm-3.0 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_llvm-3.0/llvm-3.0/main.log
Error: The following dependencies were not installed: ld64 llvm-3.0
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
>

I'll try to attach the log file.

When I searched the tickets for similar bugs, I found one that had you guys willing to fix it and one that didn't. Since I want to use Clang to help a user using my code, hopefully you'll pick the former.

[darylew@…]

Log file generated when llvm-3.0 build failed

[jeremyhu (Jeremy Huddleston Sequoia)]

Yeah... patches welcome, but I doubt this is the only issue getting clang up on Tiger.

[darylew@…]

Not having access to clang, due to not having LLVM, was a minor annoyance. But I could get around it because I still have the latest lines of GCC to go to for my C++2011 needs. Now, as indicated ​here, LLVM has become an indirect dependency for GCC too! I'm shut out of all advanced compilers; getting this fixed has become more imperative.

The attempt I had to build "gcc47" ended with ​LLVM not building. Since that build was made with the newly-installed "apple-gcc42," I'm going to add a new log.

[darylew@…]

Log file generated when llvm-3.0 build failed, using apple-gcc42 as the compiler

[jeremyhu (Jeremy Huddleston Sequoia)]

:info:build /usr/bin/ld: -i argument: nstall_name must have a ':' between its symbol names
:info:build collect2: ld returned 1 exit status

You need ld64. #33987