| 1 |
Hello, |
| 2 |
Quoting Ryan Hill <dirtyepic@g.o>: |
| 3 |
|
| 4 |
>> gcc is slotted. Is there any reason why we can't simply make grub depend |
| 5 |
>> on a working slot of gcc and set CC appropriately in the ebuild? |
| 6 |
> |
| 7 |
> We have no way of forcing an ebuild to be built with a particular version of |
| 8 |
> GCC. This is on purpose, and there are both technical and sociological |
| 9 |
> reasons for it. |
| 10 |
> |
| 11 |
> What we can do is take some kind of action if the compiler is 4.6, such as |
| 12 |
> die with a message to use grub-static instead. |
| 13 |
|
| 14 |
|
| 15 |
There were a time many applications needed libstdc++3 (or even GCC |
| 16 |
2.96) and we lived with 2 slots of GCC without any problem. And there |
| 17 |
are many work-around for not using grub legacy : grub-static, grub2, |
| 18 |
lilo, syslinux, u-boot-tools, ... |
| 19 |
|
| 20 |
Sorry for the intrusion, |
| 21 |
|
| 22 |
Xavier Miller. |
Archives