You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Sam TH <sa...@uchicago.edu> on 2001/02/01 03:45:42 UTC
Build on BeOS
Well, on BeOS for the i386, R4.5 (truly ancient), I get the following
error when I build subversion:
/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
However, if I just do make check at that point, it goes through a
whole bunch of tests, until it gets to that same error again, when it
tries to do the tests in svnadmin.
Does anyone know what would be causing this?
Also, how can I tell if the tests are operating properly? The output
seems reasonable, but I can't tell for sure.
Thanks
sam th
sam@uchicago.edu
http://www.abisource.com/~sam/
GnuPG Key:
http://www.abisource.com/~sam/key
Re: Build on BeOS
Posted by Sam TH <sa...@uchicago.edu>.
On Wed, Jan 31, 2001 at 11:10:08PM -0600, Ben Collins-Sussman wrote:
> Sam TH <sa...@uchicago.edu> writes:
>
> > Make check appears to pass all tests.
> >
> > Ain't portability nifty.
>
> Sure. Seems like we spend an awful lot of time porting our
> portability though. :)
Well, I still need to get APR ported to QNX before I will be able to
replace CVS. Now, if I only had a QNX machine . . .
>
> I don't think there's anyone else on the subversion list who's running
> BeOS. Sam, we'd be much obliged if you occasionally let us know that
> we compile there.
>
Well, I don't actually *use* BeOS. I have telnet access to a machine
that's used as a build host for AbiWord. But I'll keep you posted.
sam th
sam@uchicago.edu
http://www.abisource.com/~sam/
GnuPG Key:
http://www.abisource.com/~sam/key
Re: Build on BeOS
Posted by Ben Collins-Sussman <su...@newton.collab.net>.
Sam TH <sa...@uchicago.edu> writes:
> Make check appears to pass all tests.
>
> Ain't portability nifty.
Sure. Seems like we spend an awful lot of time porting our
portability though. :)
I don't think there's anyone else on the subversion list who's running
BeOS. Sam, we'd be much obliged if you occasionally let us know that
we compile there.
Re: Build on BeOS
Posted by Sam TH <sa...@uchicago.edu>.
On Wed, Jan 31, 2001 at 10:24:50PM -0600, Sam TH wrote:
> On Wed, Jan 31, 2001 at 09:57:28PM -0600, Ben Collins-Sussman wrote:
> > Sam TH <sa...@uchicago.edu> writes:
Well, all the problems are now gone. Yay.
Make works wonderfully, and compiles fine.
Make check appears to pass all tests.
Ain't portability nifty.
sam th
sam@uchicago.edu
http://www.abisource.com/~sam/
GnuPG Key:
http://www.abisource.com/~sam/key
Re: Build on BeOS
Posted by Sam TH <sa...@uchicago.edu>.
On Wed, Jan 31, 2001 at 09:57:28PM -0600, Ben Collins-Sussman wrote:
> Sam TH <sa...@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. :)
>
Hey, I only count 2 other times. :)
> And everything should be hunky-dory.
Well, it would be if it wasn't for the lock in CVS on tigris. Oh
well.
sam th
sam@uchicago.edu
http://www.abisource.com/~sam/
GnuPG Key:
http://www.abisource.com/~sam/key
Re: Build on BeOS
Posted by Ben Collins-Sussman <su...@newton.collab.net>.
Sam TH <sa...@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.