/bin/sh /var/tmp/portage/subversion-0.21.0-r1/work/subversion-0.21.0/libtool --silent --mode=compile gcc -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -march=pentium3 -O3 -pipe -pthread -DNEON_ZLIB -DNEON_SSL -I./subversion/include -I. -I/usr/include/neon -I/var/tmp/portage/subversion-0.21.0-r1/work/subversion-0.21.0/apr/include -I/var/tmp/portage/subversion-0.21.0-r1/work/subversion-0.21.0/apr-util/include -o subversion/libsvn_fs/trail.lo -c subversion/libsvn_fs/trail.c subversion/libsvn_fs/trail.c: In function `begin_trail': subversion/libsvn_fs/trail.c:57: structure has no member named `txn_begin' subversion/libsvn_fs/trail.c: In function `abort_trail': subversion/libsvn_fs/trail.c:77: dereferencing pointer to incomplete type subversion/libsvn_fs/trail.c: In function `commit_trail': subversion/libsvn_fs/trail.c:101: dereferencing pointer to incomplete type subversion/libsvn_fs/trail.c:107: structure has no member named `txn_checkpoint' make: *** [subversion/libsvn_fs/trail.lo] Error 1 make: *** Waiting for unfinished jobs.... !!! ERROR: dev-util/subversion-0.21.0-r1 failed. !!! Function src_compile, Line 106, Exitcode 2 !!! subversion python bindings failed Reproducible: Always Steps to Reproduce: 1. emerge subversion 2. or: emerge unmerge apache && emerge subversion 3. Actual Results: see details Expected Results: I expected to get away from CVS. ;-) that's it, contact me if I you feel I missed anything.
Thanks for the help, Paul.
This seems to be a problem involving berkely db. Do you by any chance have db4 installed. In that case you might want to try: "emerge =subversion-0.21.0" As the previous version of the ebuild does not try to use a preinstalled db. Trying to remerge sys-libs/db could also be a solution.
No, it's a thinko in the ebuild. --with-berkely-db does not work, --with-berkeley-db probably will (still compiling, slow machine) Google says: berkely: 64000 hits berkeley: 6710000 hits But it being common does not make it any less wrong ;-)
Fixing the --with-berkely-db / --with-berkeley-db typo fixes things, in case anyone was wondering :) I fixed my ebuild in place so if the typo is still there next time I emerge rsync it'll be broken again ..
It is fixed in cvs, but I guess I forgot to close the bug
