| 1 |
On Fri, 14 Nov 2014 14:17:12 -0500 |
| 2 |
Rich Freeman <rich0@g.o> wrote: |
| 3 |
> On Fri, Nov 14, 2014 at 1:22 PM, Ciaran McCreesh |
| 4 |
> <ciaran.mccreesh@××××××××××.com> wrote: |
| 5 |
> > On Fri, 14 Nov 2014 09:08:17 -0500 |
| 6 |
> > Michael Orlitzky <mjo@g.o> wrote: |
| 7 |
> >> Question 1: is it desirable to e.g. switch compilers, compile |
| 8 |
> >> systemd, and then switch back? |
| 9 |
> > |
| 10 |
> > This will horrifically break things like Portage's parallel build... |
| 11 |
> > |
| 12 |
> > Note that on every distribution except Gentoo, there are no problems |
| 13 |
> > with running multiple versions of gcc simultaneously. |
| 14 |
> > |
| 15 |
> |
| 16 |
> Not really an apples to apples. If you exclusively use binary |
| 17 |
> packages I suspect that you won't run into any of these problems on |
| 18 |
> Gentoo either. |
| 19 |
|
| 20 |
It *also* isn't an issue on any other source based distribution. This |
| 21 |
is entirely down to Gentoo libstdc++ silliness. |
| 22 |
|
| 23 |
> However, the right way to do this isn't to toggle some global setting |
| 24 |
> - it is to just apply specific settings when building specific |
| 25 |
> packages. |
| 26 |
|
| 27 |
Which doesn't work properly on Gentoo due to the weird way libstdc++ is |
| 28 |
handled. |
| 29 |
|
| 30 |
-- |
| 31 |
Ciaran McCreesh |
Archives