| 1 |
On 04/23/2015 07:51:30 AM, james wrote: |
| 2 |
> Nikos Chantziaras <realnc <at> gmail.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
> > > So is my best hope the "toolchain" repo ? |
| 6 |
> |
| 7 |
> > You can always compile and install locally in your $HOME directory. |
| 8 |
> 5.1 |
| 9 |
> > was just released, so you can try that. |
| 10 |
> |
| 11 |
> I hear you. It'd take me a long time to figure out the settings, |
| 12 |
> configs |
| 13 |
> and such. Beside I know that folks that do this sort of thing put |
| 14 |
> some time into learning the tricks..... |
| 15 |
> |
| 16 |
> I'll wait at least until there is an ebuild of some kind. Those folks |
| 17 |
> (toolchain) that put out the 5.0.x builds should have one for 5.1 |
| 18 |
> soon.......... I do agree with the subliminal suggestion that I should |
| 19 |
> find those gcc compile and install docs to read about the new options |
| 20 |
> and feature and where I needed them turned off or on, regardless of |
| 21 |
> how it is installed on my systems. |
| 22 |
> |
| 23 |
|
| 24 |
I've just renamed the gcc-6.0.0_alpha20150412.ebuild (the 6 must be typo) from toolchain overlay |
| 25 |
to gcc-5.1.0.ebuild which I have attached. |
| 26 |
It worked just fine here. |
| 27 |
|
| 28 |
Helmut |
Archives