Message134766
| Author |
Jason.Vas.Dias |
| Recipients |
Jason.Vas.Dias, r.david.murray |
| Date |
2011年04月29日.13:31:18 |
| SpamBayes Score |
1.5490076e-07 |
| Marked as misclassified |
No |
| Message-id |
<1304083879.9.0.214044072452.issue11954@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
OK, so the ' vanilla configure ' build succeeds too - using DB module
only gdbm , and with internal libffi:
$ make clean
$/usr/src/cpython/configure --prefix=/usr --libdir=/usr/lib64 --enable-shared
...
$ echo $?
0
$ make -j2
...
$ echo $?
0
But exactly the same 'make test' errors result using gdm db module
and the internal libffi . Now running the verbose tests and will
append the failure details again.
Is there some special "vanilla configure" set of options
required by Python to pass its make tests ? If so, please
let me know what they are . |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年04月29日 13:31:19 | Jason.Vas.Dias | set | recipients:
+ Jason.Vas.Dias, r.david.murray |
| 2011年04月29日 13:31:19 | Jason.Vas.Dias | set | messageid: <1304083879.9.0.214044072452.issue11954@psf.upfronthosting.co.za> |
| 2011年04月29日 13:31:19 | Jason.Vas.Dias | link | issue11954 messages |
| 2011年04月29日 13:31:19 | Jason.Vas.Dias | create |
|