| 1 |
On Sat, Jun 23, 2018 at 12:35:32PM +0100, Mick wrote: |
| 2 |
> On Saturday, 23 June 2018 11:09:10 BST Alec Ten Harmsel wrote: |
| 3 |
> > |
| 4 |
> > How about `emerge --info | grep PYTHON_SINGLE_TARGET'? The problem looks |
| 5 |
> > |
| 6 |
> > to be: |
| 7 |
> > > PYTHON_SINGLE_TARGET="-python2_7 -python3_4 -python3_5" |
| 8 |
> > |
| 9 |
> > At least one PYTHON_SINGLE_TARGET needs to be set. I'd guess that |
| 10 |
> > PYTHON_SINGLE_TARGET got updated to 3.6, leaving GDB in its dust. |
| 11 |
> > |
| 12 |
> > Alec |
| 13 |
> |
| 14 |
> Thanks Alec, yes python-3.6 was moved to the stable tree. This is what I |
| 15 |
> have: |
| 16 |
> |
| 17 |
> PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" |
| 18 |
> |
| 19 |
> -- |
| 20 |
> Regards, |
| 21 |
> Mick |
| 22 |
|
| 23 |
I see this at the top of gdb-7.12.1.build: |
| 24 |
|
| 25 |
PYTHON_COMPAT=( python{2_7,3_4,3_5} ) |
| 26 |
|
| 27 |
For the mean time, you can either accept the breakage, set |
| 28 |
PYTHON_SINGLE_TARGET="python3_5" in /etc/portage/make.conf for now, or run an |
| 29 |
unstable gdb. |
| 30 |
|
| 31 |
Alec |
Archives