On Tue, Dec 05, 2006 at 10:16:52AM +1100, John Vandenberg wrote:
> Hi Bob,
>
> On 12/2/06, Bob Rossi <[EMAIL PROTECTED]> wrote:
>
> >First, and oddly enough, the buildconf script fails for me because
> >build/buildcheck.sh doesn't recognize my libtool --version. I don't know
> >sed well enough, and thought someone here would quickly be able to spot
> >the problem. If not, I'll have to look deeper.
> >
> > $ libtool --version 2>/dev/null
> >
> > ltmain.sh (GNU libtool) 1.5.23a (1.1220.2.412 2006/10/13 14:13:30)
> >
> > Copyright (C) 2006 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions. There is
> > NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> >
> >This command is failing by giving me no output.
> > $ libtool --version 2>/dev/null|sed -e 's/([^)]*)//g;s/^[^0-9]*//;s/[-
> > ].*//g;q'
>
> The following worked for me on Fedora Core 3, MSYS (MINGW32_NT-5.1 -
> 1.0.11), and Cygwin (CYGWIN_NT-5.1 - 1.5.18):
>
> $ cat <<EOF | sed -e 's/([^)]*)//g;s/^[^0-9]*//;s/[- ].*//g;q'
> > ltmain.sh (GNU libtool) 1.5.23a (1.1220.2.412 2006/10/13 14:13:30)
> >
> > Copyright (C) 2006 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions. There is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> >EOF
> 1.5.23a
>
> Could you let us know which version of sed you are using.
$ sed --version
GNU sed version 4.1.5
That's on Cygwin of course.
> >So, after patching autoconf, and making these two patches to apr, I was
> >able to cross compile on cygwin with this command,
> >
> > ./configure apr_cv_tcp_nodelay_with_cork=no ac_cv_func_setpgrp_void=yes
> > ac_cv_file__dev_zero=no --build=i686-pc-cygwin --host=i686-pc-mingw32
> > CC='gcc -mno-cygwin' CXX='g++ -mno-cygwin'
> >
> >I was able to take a sample program, and run it on a machine that did
> >not have cygwin installed, and it ran fine. It was simply a hello world
> >type program with apr stuff in it.
>
> Have you tried the test suite?
Nope, great idea. Attached is the results. I'm going to try a native
build of mingw to make sure the results are the same. How do these
results look?
Thanks,
Bob Rossi
(cd test && make check)
make[1]: Entering directory
`/home/bobbybrasko/rcs/svn/vigilant/vigilant/builddir/vigilant-tools/apr/test'
for prog in testlockperf.exe testshmproducer.exe testshmconsumer.exe
testmutexscope.exe testall.exe ; do \
./$prog; \
if test $? = 255; then \
echo "$prog failed"; \
break; \
fi; \
done
APR Lock Performance Test
==============
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (UNNESTED) OK
Starting 1 threads OK
microseconds: 859375 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (NESTED) OK
Starting 1 threads OK
microseconds: 31250 usec
apr_thread_rwlock_t Tests
Initializing the apr_thread_rwlock_t OK
Starting 1 threads OK
microseconds: 875000 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (UNNESTED) OK
Starting 2 threads OK
microseconds: 1828125 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (NESTED) OK
Starting 2 threads OK
microseconds: 78125 usec
apr_thread_rwlock_t Tests
Initializing the apr_thread_rwlock_t OK
Starting 2 threads OK
microseconds: 1812500 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (UNNESTED) OK
Starting 3 threads OK
microseconds: 3140625 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (NESTED) OK
Starting 3 threads OK
microseconds: 125000 usec
apr_thread_rwlock_t Tests
Initializing the apr_thread_rwlock_t OK
Starting 3 threads OK
microseconds: 3343750 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (UNNESTED) OK
Starting 4 threads OK
microseconds: 4312500 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (NESTED) OK
Starting 4 threads OK
microseconds: 140625 usec
apr_thread_rwlock_t Tests
Initializing the apr_thread_rwlock_t OK
Starting 4 threads OK
microseconds: 4593750 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (UNNESTED) OK
Starting 5 threads OK
microseconds: 5625000 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (NESTED) OK
Starting 5 threads OK
microseconds: 187500 usec
apr_thread_rwlock_t Tests
Initializing the apr_thread_rwlock_t OK
Starting 5 threads OK
microseconds: 5843750 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (UNNESTED) OK
Starting 6 threads OK
microseconds: 6500000 usec
apr_thread_mutex_t Tests
Initializing the apr_thread_mutex_t (NESTED) OK
Starting 6 threads OK
microseconds: 218750 usec
apr_thread_rwlock_t Tests
Initializing the apr_thread_rwlock_t OK
Starting 6 threads OK
microseconds: 6703125 usec
Assertion failed: rv == APR_SUCCESS, file testmutexscope.c, line 168
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
testatomic : SUCCESS
testdir : SUCCESS
testdso : FAILED 4 of 5
testdup : SUCCESS
testenv : SUCCESS
testfile : SUCCESS
testfilecopy : SUCCESS
testfileinfo : SUCCESS
testflock : SUCCESS
testfmt : SUCCESS
testfnmatch : SUCCESS
testargs : SUCCESS
testhash : SUCCESS
testipsub : SUCCESS
S
testlock : SUCCESS
testlfs : SUCCESS
testmmap : SUCCESS
testnames : SUCCESS
testoc : SUCCESS
testpath : SUCCESS
testpipe : FAILED 2 of 9
testpoll : SUCCESS
testpools : SUCCESS
testproc : SUCCESS
testprocmutex : SUCCESS
testrand : SUCCESS
testrand2 : SUCCESS
testsleep : SUCCESS
testshm : SUCCESS
testsock : SUCCESS
testsockets : SUCCESS
testsockopt : SUCCESS
teststr : SUCCESS
teststrnatcmp : SUCCESS
testtable : SUCCESS
testtemp : SUCCESS
testthread : SUCCESS
testtime : SUCCESS
testud : SUCCESS
testuser : SUCCESS
testvsn : SUCCESS
Failed Tests Total Fail Failed %
===================================================
testdso 5 4 80.00%
testpipe 9 2 22.22%
make[1]: Leaving directory
`/home/bobbybrasko/rcs/svn/vigilant/vigilant/builddir/vigilant-tools/apr/test'
