On 2012-3-26 19:14 , Ryan Schmidt wrote: > > Ok, then you could change this back in the portfile, and this time add a > comment explaining why it's there. Also report the problem to the developers > of ffmpeg so they can fix it. Jeremy seems to be on a hunt for ports that > think they can't use clang, and trying to fix them to use clang.
Everyone should really follow his example here. Don't fall back to llvm-gcc just because clang is complaining about invalid code, rather fix it if at all possible. And if there is an actual bug in clang or you can't fix the invalid code, file a bug with the llvm project or the upstream developers, respectively, and make a note of the bug number/URL in a comment next to the configure.compiler change in the portfile. - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
