| 1 |
On Fri, Feb 20, 2009 at 12:56 PM, Harry Putnam <reader@×××××××.com> wrote: |
| 2 |
> Can anyone tell me if there is some way to tell emerge to use a |
| 3 |
> specific compiler during an emerge? |
| 4 |
> |
| 5 |
> I get this output during emerge of virutalbox-ose. Note that it says |
| 6 |
> to use a version of gcc earlier than 4.3. Is there some way to do |
| 7 |
> that without causing grief somewhere else? |
| 8 |
> |
| 9 |
> [...] |
| 10 |
> VirtualBox-2.0.6-OSE.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] |
| 11 |
> * checking ebuild checksums ;-) ... [ ok ] |
| 12 |
> * checking auxfile checksums ;-) ... [ ok ] |
| 13 |
> * checking miscfile checksums ;-) ... [ ok ] |
| 14 |
>>>> cfg-update-1.8.2-r1: Creating checksum index... |
| 15 |
> * there are known problems with gcc 4.3 and the virtualbox |
| 16 |
> * recompiler stuff. Please use at least a version of gcc < 4.3 |
| 17 |
> * |
| 18 |
> * ERROR: app-emulation/virtualbox-ose-2.0.6 failed. |
| 19 |
> * Call stack: |
| 20 |
> * ebuild.sh, line 49: Called pkg_setup |
| 21 |
> * virtualbox-ose-2.0.6.ebuild, line 54: Called die |
| 22 |
> * The specific snippet of code: |
| 23 |
> * die "gcc 4.3 cannot build the virtualbox recompiler" |
| 24 |
> * The die message: |
| 25 |
> * gcc 4.3 cannot build the virtualbox recompiler |
| 26 |
> [...] |
| 27 |
|
| 28 |
I guess you can just use gcc-config to change versions, compile it, |
| 29 |
then gcc-config back to normal... Maybe there's a way to define it at |
| 30 |
the package level (so you don't have to do that every time there's an |
| 31 |
update) but I don't know it off the top of my head. |
Archives