Re: Build on BeOS

Sam TH <sam@uchicago.edu> writes:

> /bin/sh ../../libtool --silent --mode=link gcc -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wpointer-arith -Wwrite-strings -Wshadow -Wredundant-decls -DSVN_DEBUG -DAP_DEBUG -g -Wall -o svnadmin main.o ../../subversion/libsvn_fs/libsvn_fs.la ../../subversion/libsvn_subr/libsvn_subr.la ../../apr/libapr.la /boot/home/subversion/apr/shmem/unix/mm/libmm.la ../../expat-lite/libexpat.la
> libtool: link: `../../subversion/libsvn_fs/libsvn_fs.la' is not a
> valid libtool archive
>
> Does anyone know what would be causing this?
>

<sigh>

OK, this about the 5th time I've had to explain this problem. No
offense to you, Sam. :)

Listen, everyone, here's what's going on:

   1. ./configure only builds libsvn_fs if it is able to find a copy
      of berkeley db3 on your system. (Unless you've explicitly
      installed db3, you probably don't have it.)

   2. Greg S. recently added a new svnadmin/ tool to the build, which
      depends on libsvn_fs. However, Greg S. forgot to make the build
      of svnadmin dependent on the build of libsvn_fs. (No offense to
      Greg S. :))

   3. The error above is what happens when your build scripts attempt
      to build svnadmin and libsvn_fs *hasn't* been built.

   4. This morning I fixed the problem in the obvious way; svnadmin
      is built if and ONLY if libsvn_fs is built.

Therefore, if you see this error, please just update from the top
level of your working copy (making sure you get a new `configure.in').
Then do the usual

    ./autogen.sh
    ./configure --with-maintainer-mode --disable-shared
    make clean
    make

And everything should be hunky-dory.
Received on Sat Oct 21 14:36:20 2006