On 31/10/2006, at 12:28 AM, Mark Mitchell wrote:
Ian Lance Taylor wrote:Mark Mitchell <[EMAIL PROTECTED]> writes:I would strongly oppose downloading stuff during the build process. We're not in the apt-get business; we can leave that to the GNU/Linux distributions, the Cygwin distributors, etc.
I can't speak for, say, Google, or even Apple, but I don't plan to have GMP (or, therefore, MFPR) shared libraries or .a files ship with Mac OS; the library is not ABI-stable and .a files are not worth the effort, and anyway by the time they shipped they would probably be out of date. You'll need to get them separately from somewhere. Maybe 'somewhere' will be gcc.gnu.org, if I find the time to package them up nicely.
I disagree: the process of building gcc from a release (as opposed to building the development version of gcc) really isn't complicated. The only remotely non-standard thing that is required is GNU make. Given that, all you need to do is "SRCDIR/configure; make".OK, I agree: a native compiler, with no special options, isn't too hard. I don't think typing that sequence twice would be too hard either, though. :-)
For something that's not too hard, it's sure causing me a lot of trouble...
smime.p7s
Description: S/MIME cryptographic signature
