When the subversion-1.0.1.ebuild script runs, it fails on the first subdirectory build, make libsvn_subr-1.la as the libtool var is set as "/bin/sh ./libtool" since abs_build_dir is set to . in the Makefile. I got round this by pausing the ebuild as soon as "Makefile created" was shown (while in configure.status) and editing the makefile manually to set the abs_bulild_dir to the absolute path (in my case /var/tmp/portage/subversion-1.0.1/work/subversion-1.0.1 ) then fg %1 to restart the build. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Set abs_build_dir to a real absolute path value.
I have observed that from one emerge to another autoconf toggles between version 2.57-r1 and version 2.58-r1 (on my computer). When using 2.58-r1 emerging subversion fails. When using 2.57-r1 it builds correctly.
Gosh, that must be why subversion has a dependency on either 2.57 or >=2.59, 2.58 is broken, and this is known, just update and things will work. The toggling is probably created by autoconf being in the world file and emerge thus updating it (allthough not to 2.59). There is no reason for autoconf to be in the world file so I advise you to remove it. That will get away of the toggling.
Oops, I did notice it trying to downgrade to autoconf-2.57 when I used ACCEPT_KEYWORDS="~x86" so I just edited the subversion-1.0.1 (x86 and use >= on autoconf-2.57 ref, deleting 2.59 ref) and the neon-0.24.4 (x86) ebuilds in order to keep things stable. Like I say, this workaround allowed me to emerge the ebuild, but I didn't know autoconf-2.58 was broken. Should I ACCEPT_KEYWORDS="~x86" emerge autoconf ?
If you don't want to use 2.57 (or downgrade to it on subversion upgrades) you might indeed best update to 2.59
OK, I've upgraded to 2.59.. I've noticed on a recent emerge that it correctly set libtool to ../libtool and not ./libtool in a sub-dir so that's cool ;) I guess the question is: "Why is autoconf 2.58 marked as stable when it's known to be broken?" Thanks for your help, Ranjit.
Well for other packages (like kde) 2.57 is broken. autoconf is just hell which one should avoid touching if possible (unfortunately we need to use it)
