-
running build
running config_cc
unifing config_cc, config, build_clib, build_ext, build commands --compiler options
running config_fc
unifing config_fc, config, build_clib, build_ext, build commands -…
-
```
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.
```
…
-
With pypy it's show:
ImportError: No module named argon2._ffi
Like in travis build (same error)
More Log:
```
/bin/ld: cannot find -llibargon2
collect2: error: ld returned 1 exit status
Traceback …
-
```
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.
```
…
-
```
What steps will reproduce the problem?
1.Compile Cantera.
What is the expected output? What do you see instead?
Instead of compiling correctly, it crashes.
What version of the product are you us…
-
```
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.
```
…