This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
PATCH: dbexecdir
- From: mitchell at codesourcery dot com (Mark Mitchell)
- To: java-patches at gcc dot gnu dot org
- Date: Tue, 10 Feb 2009 10:00:45 -0800 (PST)
- Subject: PATCH: dbexecdir
- Reply-to: mark at codesourcery dot com
Here's the last of this series of patches...
This one moves dbexecdir, which is where libjvm is installed, into
toolexeclibdir, instead of libdir. Again, I think this is an
appropriate fix for cross-compilation; libjvm.{a,so} are target
libraries, so should not go directly in $prefix/lib.
However, I don't fully understand how all these things are intended to
find each other a run-time. In other words, I'm hoping that there
aren't hard-coded assumptions elsewhere about the paths to these
things.
OK to apply?
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
2009-02-10 Mark Mitchell <mark@codesourcery.com>
* configure.ac (dbexecdir): Base on toolexeclibdir.
Index: libjava/configure.ac
===================================================================
--- libjava/configure.ac (revision 236120)
+++ libjava/configure.ac (working copy)
@@ -1409,10 +1409,10 @@ gcjsubdir=gcj-$gcjversion-$libgcj_sovers
multi_os_directory=`$CC -print-multi-os-directory`
case $multi_os_directory in
.)
- dbexecdir='$(libdir)/'$gcjsubdir # Avoid /.
+ dbexecdir='$(toolexeclibdir)/'$gcjsubdir # Avoid /.
;;
*)
- dbexecdir='$(libdir)/'$multi_os_directory/$gcjsubdir
+ dbexecdir='$(toolexeclibdir)/'$multi_os_directory/$gcjsubdir
;;
esac
AC_SUBST(dbexecdir)