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