> There is a test, test_realpath in tests/test_other.py. Does that not pass
> for you (tests/runner.py other.test_realpath)? Or does it not test the
> functionality you are seeing broken?
Yes... well, I don't know how to run tests through python, but, looking at
its code and compiling this test:
// file testrealpath.c
#include <stdlib.h>
#include <stdio.h>
#include <errno.h>
#define TEST_PATH "/boot/README.txt"
int
main(int argc, char **argv)
{
errno = 0;
char *t_realpath_buf = realpath(TEST_PATH, NULL);
if (NULL == t_realpath_buf) {
printf("Resolved failed\n");fflush(stdout);
perror("Resolve failed");
return 1;
} else {
printf("Resolved: %s", t_realpath_buf);fflush(stdout);
free(t_realpath_buf);
return 0;
}
}
emcc -o testrealpath.html testrealpath.c
>
firefox ./testrealpath.html
>
Then in the console it says: Resolved failed.
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
