| 1 |
On Thu, Jan 10, 2013 at 7:51 PM, Adam Carter <adamcarter3@×××××.com> wrote: |
| 2 |
> 17 compiled with pgo but in the emerge output for 18 it shows as (-pgo). pgo |
| 3 |
> is selected in make.conf, and in the ebuild; |
| 4 |
> |
| 5 |
> DEPEND="${RDEPEND} |
| 6 |
> dev-python/pysqlite |
| 7 |
> virtual/pkgconfig |
| 8 |
> pgo? ( |
| 9 |
> =dev-lang/python-2*[sqlite] |
| 10 |
> >=sys-devel/gcc-4.5 ) |
| 11 |
> amd64? ( ${ASM_DEPEND} |
| 12 |
> virtual/opengl ) |
| 13 |
> x86? ( ${ASM_DEPEND} |
| 14 |
> virtual/opengl )" |
| 15 |
> |
| 16 |
> And I have python 2 built with sqlite and gcc 4.7.2. Why is pgo not enabled? |
| 17 |
|
| 18 |
I had noticed it a while ago, it appears to be hardmasked: |
| 19 |
|
| 20 |
# Jory A. Pratt <anarchy@g.o> (15 Dec 2012) |
| 21 |
# PGO is known to be busted with most configurations |
| 22 |
www-client/firefox pgo |
| 23 |
|
| 24 |
I never had a single problem with it, so I'm going to unmask it and |
| 25 |
see if anything breaks. |
Archives