At 4/13/2005 09:50 AM, Matthew England wrote:
>I've had a few people email me about my build-on-cygwin note in the
>ever-popular "Subversion 1.2 RC1 Binaries" thread, but I have yet to see a
>response to the "forked" therad I made below regarding my failure to build
>1.2-rc1 on winxp-cygwin (maybe I missed something in my email)?
It's come to my intention that I may be pushing this thread rather
impatiently. My apologies for any iconvenience. Here's some thoughts on
why I followed up my original note:
I received several private inquiries about what happened with my build per
the "flame" thread, and I've had to redirect those that were interested to
my forked thread. (I suspect this because the flame thread was getting so
much publicity it was hard to see mine through the noise, but I'm not
sure.) So rather then having to continue to do this privately and continue
to respond to multiple private emails, I thought I would do it publicly and
1) proactively save the work of managing the private inquiries, and 2) try
to get eyeballs on this forked thread being that there seems to be interest
in both Windows build failure and cygwin build assistance.
Further, I'm in no rush to get an answer right away. I have no business
dependence on this yet, but I may in the next month.
Thanks for your time and patience and support. Subversion may turn out to
be a valuable asset to my business.
-Matt
At 4/13/2005 09:50 AM, Matthew England wrote:
>I've had a few people email me about my build-on-cygwin note in the
>ever-popular "Subversion 1.2 RC1 Binaries" thread, but I have yet to see a
>response to the "forked" therad I made below regarding my failure to build
>1.2-rc1 on winxp-cygwin (maybe I missed something in my email)?
>
>Anybody have any thoughts on the errors below?
>
>-Matt
>
>
>At 4/12/2005 05:38 PM, Matthew England wrote:
>>Hello,
>>
>>As per the "Subversion 1.2 RC1 Binaries" thread, I'm trying to build
>>Subversion 1.2-rc1 on my cygwin-winxp box without any apache integration
>>(svnserve-based only) and no Berkley DB support (fsfs only). I figured
>>this deserved a new thread (sorry if I'm breaking svn-email-list
>>etiquette here...but please don't hesitate to let me know).
>>
>>(I was able to build the same things under Redhat9 without any problems.)
>>
>>Is this (svn 1.2-rc1 build on cygwin-winxp w/out apache nor bdb)
>>currently possible? If so, how? My details below.
>>
>>fyi, I will not be able to attempt any VS build process, only cygwin.
>>
>>-Matt
>>
>>
>>>Date: Tue, 12 Apr 2005 17:26:19 -0500
>>>To: users@subversion.tigris.org
>>>From: Matthew England <mengland@mengland.net>
>>>
>>>At 4/12/2005 04:16 PM, Matthew England wrote:
>>>>I'm curious: If 1.2-rc1 present enough difficulty compiling with
>>>>VisualStudio/Microsoft compilers, why not build with a cygwin
>>>>(http://cygwin.com) instead?
>>>
>>>Well, I'll try to answer my own question: the cygwin-svn-1.2-rc1 broke
>>>on me. Details below. These issues may or may not be the same thing as
>>>mentioned previously (on this thread or others), so my apologies for not
>>>reading more closely if this is the case.
>>>
>>>Fyi, I'm building without apache integration (I'll run exclusively from
>>>svnserve or the native svn lib) nor Berkley DB capability. My build cmdline:
>>>
>>> ./configure --without-berkeley-db && make && make check
>>>
>>>The following is an exercept of my build output.
>>>
>>>So I too am in the "how do I build 1.2-rc1 on Windows?" boat.
>>>
>>>-Matt
>>>
>>>
>>>[...]
>>>cd subversion/libsvn_subr && /bin/bash
>>>/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/libtool --tag=CC
>>>--silent --mode=link gcc -g -O2 -g -O2 -DNEON_ZLIB -rpath
>>>/usr/local/lib -o libsvn_subr-1.la -no-undefined auth.lo cmdline.lo
>>>config.lo config_auth.lo config_file.lo config_win.lo ctype.lo date.lo
>>>error.lo hash.lo io.lo lock.lo md5.lo opt.lo path.lo pool.lo quoprint.lo
>>>sorts.lo stream.lo subst.lo svn_base64.lo svn_string.lo target.lo
>>>time.lo utf.lo utf_validate.lo validate.lo version.lo xml.lo
>>>/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/apr-util/libaprutil-0.la
>>>-lgdbm -lexpat -liconv
>>>/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/apr/libapr-0.la -lresolv
>>>-lcrypt -lintl
>>>
>>>*** Warning: This system can not link to static lib archive
>>>/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/apr-util/libaprutil-0.la.
>>>*** I have the capability to make that library automatically link in when
>>>*** you link to this library. But I can only do this if you have a
>>>*** shared version of the library, which you do not appear to have.
>>>
>>>*** Warning: This system can not link to static lib archive
>>>/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/apr/libapr-0.la.
>>>*** I have the capability to make that library automatically link in when
>>>*** you link to this library. But I can only do this if you have a
>>>*** shared version of the library, which you do not appear to have.
>>>Creating library file: .libs/libsvn_subr-1.dll.a
>>>.libs/auth.o(.text+0x19): In function `svn_auth_open':
>>>/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/subversion/libsvn_subr/auth.c:103:
>>>undefined reference to `_apr_palloc'
>>>.libs/auth.o(.text+0x32):/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/subversion/libsvn_subr/auth.c:104:
>>>undefined reference to `_apr_hash_make'
>>>.libs/auth.o(.text+0x3f):/cygdrive/e/scratch/builds/subversion-1.2.0-rc1/subversion/libsvn_subr/auth.c:105:
>>>undefined reference to `_apr_hash_make'
>>>[...]
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>>>For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 13 17:39:23 2005