|
Packit |
a4aae4 |
|
|
Packit |
a4aae4 |
On some systems 'make check' will report that the script config.guess' could
|
|
Packit |
a4aae4 |
not be found. If that happens, create a symbolic link from ../conf/config.guess
|
|
Packit |
a4aae4 |
to either this directory or the libdap-* directory (one level up). The check
|
|
Packit |
a4aae4 |
target should now work.
|
|
Packit |
a4aae4 |
|
|
Packit |
a4aae4 |
Tests that are known/expected to fail
|
|
Packit |
a4aae4 |
|
|
Packit |
a4aae4 |
There are four tests that are know to fail: expr-test.0/test.1.exp,
|
|
Packit |
a4aae4 |
test.6.exp and the expr-test.1 versions. These tests check to see if a CE
|
|
Packit |
a4aae4 |
with a selection works when applied to a non-relational data type. It does
|
|
Packit |
a4aae4 |
not work and that behavior was never defined by DAP 2.0.
|
|
Packit |
a4aae4 |
|
|
Packit |
a4aae4 |
Tests expr-test.1/test.xc.exp and test.yc.exp also fail because of the
|
|
Packit |
a4aae4 |
situation described in ticket #995 - a nested sequence is not correctly
|
|
Packit |
a4aae4 |
processed by the intern_data() methods. This problem will show up in the JGOFS
|
|
Packit |
a4aae4 |
handler when ASCII responses are requested, but will not affect other
|
|
Packit |
a4aae4 |
Sequence data sets such as the file servers' data.
|
|
Packit |
a4aae4 |
|