Tom Tromey <[EMAIL PROTECTED]> writes:
> Brian> I think as far as CVS goes we could set it up so that the ,v
> Brian> files from Classpath's tree get copied over to cygnus regularly
> Brian> in the libjava directory of libgcj.
>
> No, we can't do that. This approach fails to consider branches in our
> repository. It also fails if anybody ever commits to any of the files
> we just copy over.
>
> However if we don't have a shared source tree we can do periodic
> imports in one direction or another. I'd prefer to avoid this (since
> I am the most likely candidate for doing the work :-).
What sort of solution do you propose? As you say libgcj is a VM and
class libraries but our project only deals with class libraries.
We're somewhat limited by what CVS is capable of.
> Brian> I can't build libgcj at the moment, missing rpath on my system.
>
> There is a line in Makefile.in that looks like this:
>
> $(LINK) -rpath $(toolexeclibdir) [ ... elided ... ]
>
> For some reason, $(LINK) is empty in your Makefile. The "-" is
> swallowed by make (that is why the error code is ignored), and "rpath"
> is run as a command.
>
> The question is, why is LINK empty? In my source tree it is defined
> with a rather lengthy value (starting $(LIBTOOL) --mode=compile ...).
> Did you re-run automake or something like that?
> Which release are you using?
> Needless to say, I've never seen this bug before.
I ran autoreconf. I probably shouldn't have. The source is from CVS
at cygnus. Do you have to copy the tree to a different directory in
order to build always? This is what I did to get around the build/src
being the same error, but it's annoying. I'll reget a few files which
have changed through my actions and try again.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
