| 1 |
On Tue, 2007-10-09 at 03:24 +0200, Bo Ørsted Andresen wrote: |
| 2 |
> On Tuesday 09 October 2007 02:56:06 W.Kenworthy wrote: |
| 3 |
> > Something that has bothered me ever since I had some version |
| 4 |
> > inconsistencies way back in the dark days ... now a new binutils update |
| 5 |
> > is in (not listed below) |
| 6 |
> > |
| 7 |
> > bunyip ~ # binutils-config -l |
| 8 |
> > [1] i686-pc-linux-gnu-2.16 |
| 9 |
> > [2] i686-pc-linux-gnu-2.16.1 * |
| 10 |
> > [3] i686-pc-linux-gnu-2.17 |
| 11 |
> > [4] i686-pc-linux-gnu-2.18 |
| 12 |
> > [5] i686-pc-linux-gnu-2.18.50.0.1 |
| 13 |
> > |
| 14 |
> > On a mixed stable/unstable x86, which binutils should one generally use? |
| 15 |
> |
| 16 |
> So why do you use multislot at all? |
| 17 |
> |
| 18 |
On a previous job (long ago now) I was switching gcc's and needed |
| 19 |
multislot. Now I dont. I presume if I remove the flag, and 'emerge |
| 20 |
world -NuDv' it will clean up after itself properly - or is it better to |
| 21 |
leave as is (critical machine :( |
| 22 |
|
| 23 |
Billk |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-user@g.o mailing list |
Archives