This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Should dbexecdir be using toolexeclibdir?
- From: Mark Mitchell <mark at codesourcery dot com>
- To: java-patches at gcc dot gnu dot org
- Date: Mon, 09 Feb 2009 14:59:22 -0800
- Subject: Should dbexecdir be using toolexeclibdir?
When installing libjava, we end up with some files in $libdir:
lib/security/classpath.security
lib/logging.properties
lib/pkgconfig/libgcj-4.3.pc
lib/gcj-4.3.2-9/libjvm.so
lib/gcj-4.3.2-9/libjvm.a
Some of these, at least, are target-specific. As such, they should go
in paths that include $target. It looks like these files come from
installations into $dbexecdir, which is set like so:
multi_os_directory=`$CC -print-multi-os-directory`
case $multi_os_directory in
.)
dbexecdir='$(libdir)/'$gcjsubdir # Avoid /.
;;
*)
dbexecdir='$(libdir)/'$multi_os_directory/$gcjsubdir
;;
esac
in libjava/configure.ac. It looks like most other target run-time
libraries end up in $toolexeclibdir, which is set just above that code
in configure.ac to paths that include "gcc/$(target_noncanonical)" in
the cross case.
So, I'm thinking that the right patch is just to get rid of dbexecdir,
using toolexeclibdir instead, or to set dbexecdir to
$(toolexeclibdir)/$gcjsubdir.
But, I have no idea what might be depending on what here, so I wanted to
ask for advice first. Any hints?
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713