| 1 |
On May 10, 2011, at 5:10 AM, Fabian Groffen wrote: |
| 2 |
|
| 3 |
> try "~binutils-2.21" |
| 4 |
> |
| 5 |
> The special Linux releases sometimes have oddities |
| 6 |
|
| 7 |
That doesn't doesn't seem to be a recognized version. |
| 8 |
|
| 9 |
From the `emerge binutils` that failed, it gives this version: |
| 10 |
|
| 11 |
Emerging (1 of 1) sys-devel/binutils-2.21.51.0.6 |
| 12 |
|
| 13 |
I see the following related to binutils in $EPREFIX/usr/portage/sys-devel/binutils |
| 14 |
|
| 15 |
$ ls usr/portage/sys-devel/binutils |
| 16 |
binutils-2.18-r04.1.ebuild binutils-2.21.51.0.6.ebuild Manifest |
| 17 |
binutils-2.19.1-r01.1.ebuild ChangeLog metadata.xml |
| 18 |
binutils-2.20.1-r1.ebuild files |
| 19 |
|
| 20 |
(question: what determines which versions I have at my disposal?) |
| 21 |
|
| 22 |
I tried the older one binutils-2.20.1-r1 using the ~ syntax you showed me :-) |
| 23 |
|
| 24 |
$ emerge --oneshot --nodeps ~binutils-2.20.1-r1 |
| 25 |
|
| 26 |
And that one worked. |
| 27 |
|
| 28 |
thanks! Onward... |
| 29 |
Ricky |
Archives