Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-13 Thread S . N . Grigoriev
13.09.2013, 01:11, "Dimitry Andric" : > On Sep 12, 2013, at 21:47, S.N.Grigoriev wrote: > >>  after upgrading to r255423 (make buildworld && make buildkernel && make >> installkernel && make installworld && reboot; make delete-old && make >> delete-old-libs) I cannot build the system with the

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-12 Thread Dimitry Andric
On Sep 12, 2013, at 21:47, S.N.Grigoriev wrote: > after upgrading to r255423 (make buildworld && make buildkernel && make > installkernel && make installworld && reboot; make delete-old && make > delete-old-libs) I cannot build the system with the WITH_GCC=yes and > WITH_GNUCXX=yes options in m

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-12 Thread S . N . Grigoriev
Hi list, after upgrading to r255423 (make buildworld && make buildkernel && make installkernel && make installworld && reboot; make delete-old && make delete-old-libs) I cannot build the system with the WITH_GCC=yes and WITH_GNUCXX=yes options in my src.conf. The following error occures: --- l

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-12 Thread David Chisnall
On 11 Sep 2013, at 21:06, "David O'Brien" wrote: > It is still very useful for folks to test changes in order to help ensure > one doesn't break the build on platforms still using GCC. If you want to do this test, then you should do make universe or make tinderbox (you should do one or the othe

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-11 Thread David O'Brien
On Fri, Sep 06, 2013 at 09:19:32PM +0100, David Chisnall wrote: > As of r255321, we are no longer building gcc or libstdc++ as part of > the default install on platforms where clang is cc. I guess I missed where this was discussed. I don't feel we should not ship 10.0 without /usr/bin/g[c+][c+].

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-10 Thread Ulrich Spörlein
2013/9/9 David Chisnall : > On 9 Sep 2013, at 14:27, Ulrich Spörlein wrote: > >> Case in point, I only recently switched to clang in base and now the >> newsbeuter port crashes during startup (yeah, it builds fine). So all >> I'm asking for now is: how can I override a random port to be built with

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-09 Thread David Chisnall
On 9 Sep 2013, at 14:27, Ulrich Spörlein wrote: > Case in point, I only recently switched to clang in base and now the > newsbeuter port crashes during startup (yeah, it builds fine). So all > I'm asking for now is: how can I override a random port to be built with > gcc (either from base or port

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-09 Thread Ulrich Spörlein
On Fri, 2013-09-06 at 21:19:32 +0100, David Chisnall wrote: > Hi Everyone, > > As of r255321, we are no longer building gcc or libstdc++ as part of the > default install on platforms where clang is cc. > > If you are using gcc, you have two options: > > 1) Install one of the lang/gcc* ports (Wa

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-07 Thread O. Hartmann
On Fri, 6 Sep 2013 21:19:32 +0100 David Chisnall wrote: > Hi Everyone, > > As of r255321, we are no longer building gcc or libstdc++ as part of > the default install on platforms where clang is cc. > > If you are using gcc, you have two options: > > 1) Install one of the lang/gcc* ports (Warne

HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-06 Thread David Chisnall
Hi Everyone, As of r255321, we are no longer building gcc or libstdc++ as part of the default install on platforms where clang is cc. If you are using gcc, you have two options: 1) Install one of the lang/gcc* ports (Warner has been working on separating out the patches to our GCC, so these sh