Re: Eclipse 3.0 Running ILLEGALY on Kaffe
Brian Thomas Sniffen wrote:
What about the case where there's a common ABI, such as Java written
against Sun's standard API, then compiled into Java Bytecode?
Combining X+Y in the way that you have described is anything but
mechanical: it is a task which typically takes a skilled programmer a
great amount of time and thought. Different programmers might do it
in different ways. I'm not referring here to the work done by ld, but
to the process of building a new program which has libfoo as a
Additionally, the program ultimately delivered to the user isn't X
with some minor bits of Y. It contains big chunks of Y -- one per
function used, at least -- directly copied. Just being in a different
memory space isn't enough to change the relationship between the
creative parts of the works. The program vim encompasses a copy of
In this case, writing against Y is creative, but when the end-user runs
the program, is Java's run-time-linking creative or mechanical?
Does this change when the program could also be linked with A, W, or Z,
all of which implement the same ABI?
Does this change if there's no way to tell which of A, W, Y or Z X was
originally written against?
Does this change if the program is aggregated with W and Z, but not Y?