On Thu, Sep 13, 2001 at 09:17:25PM +0000, Ian Rogers wrote:
> I haven't. TBH, I've had difficulty with all the latest autoconf, etc. I
Have you tried downloading these auto* from ftp.gnu.org:/pub/gnu/auto*
(replacing auto* by autoconf, automake, libtool) and installing them in
your PATH?
> usually try and avoid the bleeding edge and stick with more stable
> distributions.
My problem is that I migrated to Debian unstable to get packages like
libffi-dev and the latest glibc and Linux kernel 2.4 with better
multithreading support. Because the intruduction of autoconf 2.50, the
configure syntax has changed, so I migrated it for SableVM ...
> WRT autoconf for some reason libtool isn't geting set up
> properly, even tho' I've rebuilt that and everything else I'm missing
> the necessary macro definitions.
If you made a local installation, you should make sure your C_INCLUDE_PATH
and similar environment variables are correctly set. Here's the list:
LIBRARY_PATH
LD_LIBRARY_PATH
C_INCLUDE_PATH
> I'm sure I'll track the problem down in
> the end. I'd have prefered not to have to, but I don't like having to
> rely on the prebuilt configure script in the tgz. Ohwell..
>
If you want to checkin your improvements to Sablepath in CVS, you
need to get this auto* stuff working.
> The problems with java/text/BreakIterator.java are the references to
> gnu.java.text.* which simply doesn't exist in the sablepath CVS tree. If
> jikes 1.13 is building BreakIterator then it is more slack in allowing
> classes to be built with undefined references in them than jikes 1.12.
> Let me know your thoughts.
If it is a simple thing to fix, you could modify BreakIterator.java,
then add:
Modification (C) 2001 Ian... <email>.
just below the FSF's copyright, then do a "cvs commit"?
Have fun!
Etienne
--
Etienne M. Gagnon http://www.info.uqam.ca/~egagnon/
SableVM: http://www.sablevm.org/
SableCC: http://www.sablecc.org/
|
