[MacPorts] #42899: llvm-gcc42 fails to install after installing Xcode 5.1
MacPorts
noreply at macports.org
Sat Mar 22 16:36:22 PDT 2014
#42899: llvm-gcc42 fails to install after installing Xcode 5.1
----------------------------------+------------------------
Reporter: tcollett+macports@… | Owner: jeremyhu@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: llvm-gcc42 |
----------------------------------+------------------------
Comment (by jeremyhu@…):
Replying to [comment:6 ryandesign@…]:
> Replying to [comment:4 jeremyhu@…]:
> > IMO, the real bug is with whatever is still trying to use this ancient
relic. There's no good reason that we should still have to keep llvm-gcc
on life support like this.
>
> There absolutely is. Some ports blacklist clang, and llvm-gcc is the
next best fallback MacPorts tries.
Yes. That's my point. Some ports blacklist clang. Those ports really
need to be fixed to build with clang.
Unless you would prefer that we remove that fallback and fallback to
apple-gcc-4.2 instead?
No. I would prefer it if ports were updated to not depend on a 7 year old
compiler.
> Yes, ideally ports would be fixed to compile with clang, but not
everyone is proficient enough in C/C++ to accomplish that immediately, and
often blacklisting clang is the simplest way to get a port to build
immediately.
Yes, but that is not a long-term solution. Such ports have been that way
for 3+ years now. They need to be fixed.
Yes, we should fix llvm-gcc's build, but we also should really fix the
dependent ports to not use llvm-gcc.
--
Ticket URL: <https://trac.macports.org/ticket/42899#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list