| 1 |
On Mon, Nov 27, 2017 at 11:47 AM, Walter Dnes <waltdnes@××××××××.org> wrote: |
| 2 |
> On Wed, Oct 11, 2017 at 10:15:50PM -0400, Walter Dnes wrote |
| 3 |
>> On Wed, Oct 11, 2017 at 11:56:21AM -0400, Mike Gilbert wrote |
| 4 |
>> |
| 5 |
>> > I can reproduce the issue by adding -fopenmp to my CFLAGS. You can |
| 6 |
>> > work around it by adding -fopenmp to LDFLAGS as well. |
| 7 |
>> |
| 8 |
>> Thanks. The following workaround makes python build properly. |
| 9 |
>> |
| 10 |
>> LDFLAGS="-fopenmp" emerge =dev-lang/python-2.7.12 =dev-lang/python-3.4.5 |
| 11 |
>> |
| 12 |
>> > This is probably a bug in the Python build system; it should probably |
| 13 |
>> > be passing CFLAGS to gcc when linking libpython. |
| 14 |
>> |
| 15 |
>> Bug https://bugs.gentoo.org/634064 filed. |
| 16 |
> |
| 17 |
> Bump; I had to... |
| 18 |
> |
| 19 |
> LDFLAGS="-fopenmp" emerge -1 =dev-lang/python-2.7.14 =dev-lang/python-3.5.4 |
| 20 |
> |
| 21 |
> ..to get the latest pythons to build properly. |
| 22 |
|
| 23 |
Just stick it in make.conf and call it fixed. |
| 24 |
|
| 25 |
You can track further updates via the bug report. |
Archives