1.5 build problem on montavista cygwin

I am using montavista cygwin 4.0 and I tried to compile subversion 1.5 in it.

make
[...]
make[1]: Entering directory `/home/jzan/svn/subversion-1.5.0/serf'
/home/jzan/svn/subversion-1.5.0/apr/libtool --silent --mode=compile gcc -g
-O2 -DCYGWIN -I. -I/home/jzan/sv/subversion-1.5.0/apr/include
-I/home/jzan/svn/subversion-1.5.0/apr-util/include -c -o
buckets/aggregate_bucketslo buckets/aggregate_buckets.c && touch
buckets/aggregate_buckets.lo
/home/jzan/svn/subversion-1.5.0/apr/libtool --silent --mode=compile gcc -g
-O2 -DCYGWIN -I. -I/home/jzan/sv/subversion-1.5.0/apr/include
-I/home/jzan/svn/subversion-1.5.0/apr-util/include -c -o
buckets/request_buckets.l buckets/request_buckets.c && touch
buckets/request_buckets.lo
/home/jzan/svn/subversion-1.5.0/apr/libtool --silent --mode=compile gcc -g
-O2 -DCYGWIN -I. -I/home/jzan/sv/subversion-1.5.0/apr/include
-I/home/jzan/svn/subversion-1.5.0/apr-util/include -c -o context.lo
context.c && t
uch context.lo
context.c:137: error: size of array `vec' is too large
make[1]: *** [context.lo] Error 1
make[1]: Leaving directory `/home/jzan/svn/subversion-1.5.0/serf'
make: *** [external-all] Error 1

So I did a bit of poking around and I found:
#define IOV_MAX (__INT_MAX__-1)
which is
$ grep __INT_MAX__ /usr/include/limits.h
#ifndef __INT_MAX__
#define __INT_MAX__ 2147483647
#define INT_MAX __INT_MAX__
#define IOV_MAX (__INT_MAX__-1)

So I can compile only if I set IOV_MAX to __INT_MAX__/4 but I don't know if
that is ok with the vec array.

Any ideas to what value I can safely set IOV_MAX as a hack? (and I can't
replace my montavista cygwin)

Cheers
J.

-- 
View this message in context: http://www.nabble.com/1.5-build-problem-on-montavista-cygwin-tp18074392p18074392.html
Sent from the Subversion Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org