Jakub Jelinek writes:
On Tue, Mar 22, 2005 at 08:11:10PM +0000, Andrew Haley wrote:
> Jakub Jelinek writes:
> > 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.
> That's impossible.
> The .db is a mapping from bytecode to shared objects, and there is no
> guarantee that if a class exists in lib/foo.so it will also exist in
> lib64/foo.so. However, that class might well exist in lib64/bar.so.
Why impossible? If can be a mapping from <bytecode, arch> pair to
Oh, what a horrible idea. Yes, that would work, I suppose. It
doesn't scale well, though.
I would have thought it easier just to give the db an appropriate name
for the arch. We don't use fat libraries, so why create fat
databases? The reasoning is exactly the same.