Replying to myself: That was it! Time to do some testing... Thanks!!! On Tue, Feb 10, 2009 at 12:28 PM, Kristian Kielhofner <kristian.kielhofner@gmail.com> wrote:
Yep, now that Tony boiled down that gdb output to a mutex lock I agree.
I'm trying a compile now with these values (cross compiling, no native compiler).
Cross compiling is so much fun!
On Tue, Feb 10, 2009 at 11:34 AM, Michael Jerris <mike@jerris.com> wrote:
From that link, these are the ones that are most likey causing the issue. I think the first one. Can you check your config.log and see what results it has for those checks? If you can compile native on the device I would suggest to on the device do a ./configure -C and then to use that config.cache file generated to get all your answers to feed your cross toolchain. You can probably just slim down that exact file and have everything you need. export apr_cv_mutex_recursive=yes; \ export ac_cv_func_pthread_rwlock_init=yes; \ export apr_cv_type_rwlock_t=yes; \
Mike
-- Kristian Kielhofner http://blog.krisk.org http://www.submityoursip.com http://www.astlinux.org http://www.star2star.com
-- Kristian Kielhofner http://blog.krisk.org http://www.submityoursip.com http://www.astlinux.org http://www.star2star.com