| 1 |
If you /etc/make.profile symbolic link points to |
| 2 |
../usr/portage/profiles/default-1.0 |
| 3 |
then /etc/make.profile/packages contains the line: |
| 4 |
*=sys-devel/gcc-2.95.3-r5 |
| 5 |
|
| 6 |
which means portage will only install that version of gcc, as far as I |
| 7 |
understand it. |
| 8 |
|
| 9 |
The solution is to either A) change the symbolic link of |
| 10 |
/etc/make.profile to use ../usr/portage/profiles/default-1.0-gcc3 OR |
| 11 |
B) use ebuild instead of emerge. AKA: |
| 12 |
ebuild /usr/portage/sys-devel/gcc/gcc-3.0.4-r5.ebuild merge |
| 13 |
|
| 14 |
-Jared H. |
| 15 |
|
| 16 |
Antonio M D'souza wrote: |
| 17 |
> I've been unable to figure out why, but emerge will not let me install |
| 18 |
> gcc-3.0.x at all. This screen dump should give you a clear idea of what it is |
| 19 |
> that I am running up against: |
| 20 |
> |
| 21 |
> root@quikbox:~# emerge /usr/portage/sys-devel/gcc/gcc-3.0.4-r5.ebuild |
| 22 |
> Calculating dependencies \ |
| 23 |
> |
| 24 |
> !!! ebuild sys-devel/gcc-3.0.4-r5 not found (possibly blocked by package.mask) |
| 25 |
> |
| 26 |
> root@quikbox:~# grep gcc /usr/portage/profiles/package.mask |
| 27 |
> #this gcc's new atexit() fix that is supposed to be wonderful, doesn't |
| 28 |
> work.... |
| 29 |
> =sys-devel/gcc-2.95.3-r2 |
| 30 |
> =sys-devel/gcc-2.95.3-r3 |
| 31 |
> #>=sys-devel/gcc-2.96 |
| 32 |
> root@quikbox:~# ls -l /usr/portage/sys-devel/gcc/gcc-3.0.4-r5.ebuild |
| 33 |
> -rw-r--r-- 1 root root 8679 05-02 17:43 |
| 34 |
> /usr/portage/sys-devel/gcc/gcc-3.0.4-r5.ebuild |
| 35 |
> root@quikbox:~# |
| 36 |
> |
| 37 |
> |
| 38 |
> Anyone have a clue as to why this could be happening? |
| 39 |
> |
| 40 |
> Tony |
| 41 |
> |
Archives