Because of emerge problems with eclipse I noticed that the file /etc/env.d/java/20blackdown-jdk-1.4.2.03 contains errors: LDPATH="${JAVA_HOME}/jre/lib/athlon64/:${JAVA_HOME}/jre/lib/athlon64/native_threads/:${JAVA_HOME}/jre/lib/athlon64/classic/:${ JAVA_HOME}/jre/lib/athlon64/server/" The problem is that both in sun and blackdown java, the path isn't /jre/lib/athlon64 but /jre/lib/amd64, so the linker couldn't find e.g. libawt.so since LDPATH was wrong. Symlinking amd64 to athlon64 solved it. If I look at less /usr/portage/dev-java/blackdown-jdk/files/blackdown-jdk-1.4.2.env I can see that the variable @PLATFORM@ is the cause for that. Since I'm new to ebuilds I don't know where this is evaluated and how one could change it. Reproducible: Always Steps to Reproduce: 1. emerge blackdown-jdk-1.4.2.03-r13 on amd64 2. emerge something that depends on it (e.g. eclipse) 3. see that LDPATH isn't updated correctly Actual Results: Emerge problems with other ebuilds. Expected Results: Correct LDPATH and JAVA_HOME
The value is evaluated in java-vm-2.eclass function get_system_arch() I don't see why your output would be athlon64 though... Only if $ARCH was empty (but why?) and athlon64 came from the uname... I thought that ARCH corresponds with what is in KEYWORDS and 'use arch', blackdown ebuild itself also assumes this when installing the nsplugin: case ${ARCH} in amd64) platform="amd64" ;; x86) platform="i386" ;; ppc) platform="ppc" ;; sparc*) platform="sparc" ;; esac Any ideas, others?
I think I found out what was causing the problem: I was using the make.conf provided by the "Conrad install method V400". This make.conf contains a line ARCH=athlon64 which is then used in CFLAGS="-march=$ARCH..." The author of that make.conf probably didn't realize that setting ARCH breaks other things. :( I'll set this to INVALID, sorry for the unconvenience.
