| 1 |
On Saturday, 23 June 2018 16:11:54 BST Grant Edwards wrote: |
| 2 |
> On 2018-06-23, Alec Ten Harmsel <alec@××××××××××××××.com> wrote: |
| 3 |
> > On Sat, Jun 23, 2018 at 12:35:32PM +0100, Mick wrote: |
| 4 |
> > |
| 5 |
> > I see this at the top of gdb-7.12.1.build: |
| 6 |
> > PYTHON_COMPAT=( python{2_7,3_4,3_5} ) |
| 7 |
> > |
| 8 |
> > For the mean time, you can either accept the breakage, set |
| 9 |
> > PYTHON_SINGLE_TARGET="python3_5" in /etc/portage/make.conf for now, or run |
| 10 |
> > an unstable gdb. |
| 11 |
> |
| 12 |
> Can't you set it to python3_5 just for gdb in /etc/portage/package.use? |
| 13 |
> |
| 14 |
> -- |
| 15 |
> Grant |
| 16 |
|
| 17 |
Yes, but then it wants to rebuild a number of packages with python3_5 |
| 18 |
(re)enabled and when gdb is updated for python3_6, I'll have to rinse and |
| 19 |
repeat. Two other packages with the same problem were obexftp and |
| 20 |
libreoffice-bin, on different PCs. I don't mind waiting for a while until the |
| 21 |
maintainers for these packages, or upstream, eventually catch up with |
| 22 |
python3_6. |
| 23 |
-- |
| 24 |
Regards, |
| 25 |
Mick |
Archives