-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
Hi,
I get an compilation error for htslib when running pysam installation script
`python setup.py`build``
but compiling htslib separately (in htslib folder ./configure and make ) runs without err…
-
Hi,
I experienced similar issues as described in https://github.com/scikit-learn/scikit-learn/issues/6115 and it's obviously a problem with numpy-scipy.
Here is the minimal steps to reproduce (I use…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…
-
```
When linking pyv8 to v8 on CentOS 5, it's unable to find the library because
it's using a relative path (i.e.
-Lbuild/v8...). Changing this to an absolute path works fine.
Patch attached.
```
…