checking whether to build Java/JDBC tools... yes checking for jakarta-ant... no checking for ant... /usr/bin/ant checking whether /usr/bin/ant works... no configure: error: ant does not work !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 38, Exitcode 1 !!! (no error message) !!! emerge aborting on /usr/portage/dev-db/postgresql/postgresql-7.2-r3.ebuild .
use vars, compiler?
In the flurry of new ebuilds in the last few days I probably built/rebuilt something that caused a problem to the postgresql ebuild as it now built OK. In any case, the compiler is 2.95.3 and the use variables are USE="cups alsa ssl mozilla spell tcltk apm arts bonobo dga dvd evo gb gnome gtk gtkhtml jpeg kde mmx motif mozilla mysql ncurses odbc oggvorbis opengl pam pcmcia png postgres python readline ruby samba sdl slang spell sse ssl tcpd truetype X xmms"
good to hear that it is working
I've seen the same problem too, using blackdown-jdk-1.3.1-r7 and ant-1.4.1-r3. My compiler is gcc-2.95.3-r7 and the USE-variable must include "java" for the problem to exist. The problem exists not only with postgresql-7.2.1-r2 but also with the new postgresql-7.2.2 ebuilds. The solution is to include /opt/blackdown-jdk-1.3.1/lib/tools.jar in CLASSPATH via /etc/profile.env, I believe this should be done by the blackdown-jdk ebuild.
I'm actually still having this problem, blackdown-jdk and jre 1.4.2, postgresql 7.3.2. Adding /opt/blackdown-jdk-1.4.1/lib/tools.jar works, as does removing java from the use variables. Perhaps the tools.jar to classpath could be added to the JRE/JDK ebuild?
I have followed all the advice here and PostgreSQL 7.3.3 still fails with this error. As I can't (for reasons that escape me) upgrade Gnome without upgrading PostgreSQL, I'm stuck. I'm using GCC 2.95.3 and my USE settings are "-kde pda" All help appreciated!
Did you try adding /opt/blackdown-jdk-versionnum/lib/tools.jar to your classpath? Also, did you try adding "-java" to your use variables just for the postgres emerge?
I had the tools.jar pathed; "-java" in USE was the key. Many thanks
Manually setting USE=-java isnt a resolved fix ;-) I just ran into this, I fixed it by: # java-config --list-available-vms [blackdown-jre-1.3.1] Blackdown JRE 1.3.1 (/etc/env.d/java/20blackdown-jre-1.3.1) () [blackdown-jdk-1.3.1] Blackdown JDK 1.3.1 (/etc/env.d/java/20blackdown-jdk-1.3.1) (*) [blackdown-jdk-1.4.1] Blackdown JDK 1.4.1 (/etc/env.d/java/20blackdown-jdk-1.4.1) () # java-config --set-system-vm=blackdown-jdk-1.4.1 Now using Blackdown JDK 1.4.1 (/etc/env.d/java/20blackdown-jdk-1.4.1) * You should login again to make your java-config changes available >>> Regenerating /etc/ld.so.cache... * Or, you can type 'source /etc/profile' in your current session. # source /etc/profile Now reemerge postgresql.. it seems postgresql didn't like blackdown-jdk-1.3.1.
I'm getting exactly the same failure, and I am using Sun's java (although Blackdown is installed). So it might be a general Postgres/java problem...? Also, should this bug really be declared "RESOLVED FIXED" when the average gentoo user can not emerge postgresql??
Mogens: Have you tried Chris' java-config fix?
Sorry for the delay! Both excluding java ("USE=-java") or switching to the very old blackdown-jdk-1.4.1 works around this bug here. But I don't know why.
