On Tue, Mar 22, 2005 at 07:58:53PM +0000, Andrew Haley wrote:
You mean that gcj-dbtool -p would print /usr/lib/`$CC $CFLAGS -print-multi-os-directory`/gcj-4.0.0/classmap.db and you'd need to pass that through shell after making sure $CC and $CFLAGS are properly defined?
gcj-dbtool is a target program, part of libgcj. So, on a multi-arch system, would there not be two gcj-dbtools, linked against different libgcjs? And, each one would print its *own* directory.
On multi-arch systems, there is usually just one set of binaries and one or two sets of libraries. If you want 2 gcj-dbtool programs, that's of course possible, but you need to decide where to install them (e.g. /usr/libexec/gcj/$LIB/gcj-dbtool ), but then all the programs that want to use gcj-dbtool need to figure out which one they want to call. For %post this location wouldn't be that hard, rpm %post would just call /usr/libexec/gcj/%{_lib}/gcj-dbtool -p ... But, will you require all Makefiles that deal with gcj-dbtool to call /usr/libexec/gcj/lib/`$CC $CFLAGS -print-multi-os-directory`/gcj-dbtool ?
Certainly, one master .db file, although it will need some work inside gcj-dbtool and libgcj.so, will make things far easier for the users and developers.
Jakub