On Aug 31, 2012, at 12:47, John Daschbach wrote: > Still struggling with being unable to configure or compile lots of > macports. Using port -d hasn't really changed much. it clearly is related > to clang, but not clear exactly how. > > > python27 dies in the first call to clang in configure, python33 dies in > the second. > > I can build both by running configure from a shell with the same call > as macports. (using the call line from the top of configure.log). > > This same approach has worked for other standard ports (using GNU > configure scripts). So the problem has something to do with how clang > behaves when called as a subprocess from macports (tcl). > > Some ports configure and build fine. Have not checked in detail what > their configure scripts test or don't test for compared with ones that fail. > > > Now my question is after building and installing from a shell, but into > /opt/local, how do I alter the macports db to indicate I have dependencies > installed?
It's probably best not to try to do that. Instead, we should figure out why MacPorts is unable to compile those ports on your system, and then fix that problem. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-users
