On Fri, Feb 6, 2009 at 3:34 AM, Anders F Björklund <[email protected]> wrote: > Jean-Michel Pouré wrote: > >> Most MacPorts packages do not carry a reference to a specific gcc >> version. As a result, Apple gcc installed in Xcode is used. >> >> I am just a beginner, but wouldn't it be a more stable solution to rely >> only on GNU gcc 2.4 and gcc-4.2 and 4.3 using MacPorts packages. More stable? Maybe. Viable? Unfortunately no. There are instances where apple's version of the compiler is _required_ to compile programs. This happens when some extensions/features which are present, and used in apple's version of gcc were not (and likely never will be) included into the official gnu version.
> > > In a word: no. :-) > > Even using the "apple-gcc*" ports would be more of a hassle than just > using /usr/bin/gcc*. And using GNU/FSF version of GCC would be worse... > Theoretically, you are right - owning the ports allows for more control. > But in practice the usual approach is to use Xcode for GCC and make etc. > > Other systems do it differently, but MacPorts usually recommends several > things to be present on the system before installing base/port(1) itself. > Like: GCC etc, X11, Tcl, Foundation, mtree, rsync, curl, ssl and more... > Some of these can be replaced with the versions from MacPorts, later on. > > > I'd go with the vendor GCC unless you need a feature that is not present, > like support for Java (GCJ) or Fortran or desires to play with GCC 4.3 ? > > And, yes, this the opposite approach as being used for Perl/Python/Ruby... > There MacPorts version are preferred. It's a little inconsistent, that way. > > --anders > > _______________________________________________ > macports-dev mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
