[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: building subversion

From: Travis P <svn_at_castle.fastmail.fm>
Date: 2004-02-04 18:44:55 CET

On Feb 3, 2004, at 7:56 AM, zafira007@gmx.de wrote:

> I'd a (probably a newbie-) question: i want to build the subversion
> 0.37 on
> a AIX 4.3.3 box with berkeley-db only for local use -> without
> apache-package. for this I use the GNU gcc 2.90 for AIX. when I
> configure with "configure
> --without-apache --with-berkeley-gb=path-to-installed-berkeley-db" and
> then
> make and make install, I get a message from the linker (which is no
> GNU-linker)
> duplicate symbols ._GLOBAL__DI, ._GLOBAL__DD and later _GLOBAL__DI,
> _GLOBAL__DD. I'd looked for these symbols and they occurs only one
> time.
> a following failure in revision-install in the makefile isn't
> successfull,
> the revision-install-part in the makefile
> "subversion/svnversion/svnversion
> $(top_srcdir) /repos/svn/trunk >
> $(DESTDIR)$(includedir)/subversion-1/svn-revision.txt" couldn't be
> startet.
> has anyone an idea? I can't install apache, so the subversion MUST run
> in
> local mode.

My needs were slightly different. I was only building the client on
AIX 5.1.
But in case it helps, here is how I configured:

% env PATH=.:/projects/svn/aix51/pkg/openssl-0.9.7c/bin:/bin:/usr/bin
-L/projects/svn/aix51/pkg/openssl-0.9.7c/lib" CC="xlc_r"
CFLAGS="-qmaxmem=-1 -O -qlanglvl=extended" ./configure
--prefix=/projects/svn/aix51/pkg/subversion-0.37.0 --with-ssl
--with-zlib --enable-shared=no --enable-maintainer-mode
--without-berkeley-db |& tee co.conf

I did discover that without "--enable-shared=no," I got a crash related
to shared libraries whether I compiled with xlc or with gcc (3.3.3).


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 4 18:44:22 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.