Hilko Bengen <ben...@debian.org> writes:
> I will accept patches. :-)
That's fair. I've attached a minimal patch that implements the pathconf
approach, as the fully dynamic approach looked like it would be
relatively involved here. With this patch, the build succeeds, albeit
skipping most tests (I guess that's typical?):
PASS: test_library.sh
SKIP: test_esedbinfo.sh
SKIP: test_esedbexport.sh
SKIP: test_python_module.sh
============================================================================
Testsuite summary for libesedb 20170121
============================================================================
# TOTAL: 4
# PASS: 1
# SKIP: 3
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Index: libesedb/libcpath/libcpath_path.c
===================================================================
--- libesedb.orig/libcpath/libcpath_path.c
+++ libesedb/libcpath/libcpath_path.c
@@ -450,6 +450,9 @@ int libcpath_path_get_current_working_di
libcerror_error_t **error )
{
static char *function = "libcpath_path_get_current_working_directory";
+#if !defined(PATH_MAX) && defined _PC_PATH_MAX
+ size_t PATH_MAX = pathconf(".", _PC_PATH_MAX);
+#endif
if( current_working_directory == NULL )
{
_______________________________________________
forensics-devel mailing list
forensics-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel
