Re: Building C++ with --enable-languages=c,fortran

2011-08-06 Thread Mikael Morin
On Saturday 06 August 2011 00:52:02 Thomas Koenig wrote: Hello world, I just noticed that C++ now appears to be built by default, even when only the C and fortran are specified. Yes, but it doesn't make much difference in practice. The only difference I saw is the debugging symbols including

Re: Building C++ with --enable-languages=c,fortran

2011-08-06 Thread Toon Moene
On 08/06/2011 11:22 AM, Mikael Morin wrote: WRT to bootstrap time, as usual: it's too long. Well, that all depends on your (time) frame of reference, of course. In the summer months leading up to Craig Burley asking for volunteers testing g77 (the g77-alpha phase), i.e., during the summer

Re: Building C++ with --enable-languages=c,fortran

2011-08-06 Thread Steve Kargl
On Sat, Aug 06, 2011 at 03:16:43PM +0200, Toon Moene wrote: On 08/06/2011 11:22 AM, Mikael Morin wrote: WRT to bootstrap time, as usual: it's too long. Well, that all depends on your (time) frame of reference, of course. In the summer months leading up to Craig Burley asking for

Re: Building C++ with --enable-languages=c,fortran

2011-08-06 Thread Toon Moene
On 08/06/2011 05:14 PM, Steve Kargl wrote: You left out the crucial hardware spec. How much memory did you have 19 years ago compared to the system today? My experience with g++ is that it will consume more memory than gcc. That might be true - I have never experienced memory shortage

Building C++ with --enable-languages=c,fortran

2011-08-05 Thread Thomas Koenig
Hello world, I just noticed that C++ now appears to be built by default, even when only the C and fortran are specified. The configure line ../trunk/configure --prefix=$HOME --enable-languages=c,fortran --with-mpc=/usr/local --with-mpfr=/usr/local leads to the message checking for

Re: Building C++ with --enable-languages=c,fortran

2011-08-05 Thread Steve Kargl
On Sat, Aug 06, 2011 at 12:52:02AM +0200, Thomas Koenig wrote: Hello world, I just noticed that C++ now appears to be built by default, even when only the C and fortran are specified. The configure line ../trunk/configure --prefix=$HOME --enable-languages=c,fortran

Re: Building C++ with --enable-languages=c,fortran

2011-08-05 Thread Ian Lance Taylor
Thomas Koenig tkoe...@netcologne.de writes: I just noticed that C++ now appears to be built by default, even when only the C and fortran are specified. The configure line ../trunk/configure --prefix=$HOME --enable-languages=c,fortran --with-mpc=/usr/local --with-mpfr=/usr/local leads to

Re: Building C++ with --enable-languages=c,fortran

2011-08-05 Thread Steve Kargl
On Fri, Aug 05, 2011 at 06:51:12PM -0700, Ian Lance Taylor wrote: Thomas Koenig tkoe...@netcologne.de writes: I just noticed that C++ now appears to be built by default, even when only the C and fortran are specified. The configure line ../trunk/configure --prefix=$HOME

Re: Building C++ with --enable-languages=c,fortran

2011-08-05 Thread Ian Lance Taylor
Steve Kargl s...@troutmask.apl.washington.edu writes: The ChangeLog entry says that if --enable-build-poststage1-with-cxx is set, C++ becomes a boot language. That is what you are seeing. I guess what the ChangeLog entry does not say is that --enable-build-poststage1-with-cxx is set by