Building subversion 1.2.1 fails

I try to upgrade to Subversion 1.2.1 where version 1.1.3 was already
installed. The build fails with the following error:

> make

cd subversion/libsvn_ra && /bin/sh
/project/sega/temp/svn/subversion-1.2.1/libtool --tag=CC --silent
--mode=link cc -g -g -qHALT=E -Wl,-brtl
-L/project/sega/temp/svn/subversion-1.2.1/apr-util/xml/expat/lib -rpath
/opt/svn/lib -o libsvn_ra-1.la ra_loader.lo
../../subversion/libsvn_subr/libsvn_subr-1.la
../../subversion/libsvn_ra_local/libsvn_ra_local-1.la
../../subversion/libsvn_repos/libsvn_repos-1.la
../../subversion/libsvn_fs/libsvn_fs-1.la
../../subversion/libsvn_delta/libsvn_delta-1.la
../../subversion/libsvn_subr/libsvn_subr-1.la
../../subversion/libsvn_ra_svn/libsvn_ra_svn-1.la
../../subversion/libsvn_delta/libsvn_delta-1.la
../../subversion/libsvn_subr/libsvn_subr-1.la
../../subversion/libsvn_ra_dav/libsvn_ra_dav-1.la
../../subversion/libsvn_delta/libsvn_delta-1.la
../../subversion/libsvn_subr/libsvn_subr-1.la
/project/sega/temp/svn/subversion-1.2.1/apr-util/libaprutil-0.la
/project/sega/temp/svn/subversion-1.2.1/apr-util/xml/expat/lib/libexpat.
la -liconv /project/sega/temp/svn/subversion-1.2.1/apr/libapr-0.la -lm
-lnsl -lpthread
/project/sega/temp/svn/subversion-1.2.1/subversion/libsvn_ra
ld: 0711-738 ERROR: Input file /opt/svn/lib/libsvn_ra_local-1.so:
        XCOFF32 object files are not allowed in 64-bit mode.
make: 1254-004 The error code from the last command is 8.

I ran configure like that with /opt/svn as installation directory:
> ./configure --prefix /opt/svn --without-berkeley-db

The installed version 1.1.3 was configured with the same options. Now
the error message of the build process lists the file
/opt/svn/lib/libsvn_ra_local-1.so as input file, but this file lies in
the installation directory of the old version 1.1.3. As version 1.1.3
was built with 32-bit and version 1.2.1 should be built with 64-bit, the
object files cannot be mixed.

I do not understand however why the build process references a file from
the installation directory as input file.

When I run configure using another installation directory, e.g.
> ./configure --prefix /opt/svn2 --without-berkeley-db

everythings works fine.

In my understanding, it should be possible to use the same installation
directory when upgrading to a newer version, and the build process is
somehow flawed as it references a file in the installation diretory.
What do you think?

I attach the output of the configure script.
Thomas

____________________________________________________________
This message may contain legally privileged or confidential
information and is therefore addressed to the named persons only.
The recipient should inform the sender and delete this message,
if he/she is not named as addressee.
The sender disclaims any and all liability for the integrity
and punctuality of this message.
The sender has activated an automatic virus scanning by
Messagelabs, but does not guarantee the virus free
transmission of this message.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org