Build Problems Resolved
Marc Stiegler
marcs@skyhunter.com
Mon, 30 Aug 1999 09:03:59 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_004E_01BEF2C6.992C0D40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
E seems to be a very, very intensive exerciser for jvms and JITs. We =
haven't found any JIT that works with E yet (right, markm? Or does the =
Symantec JIT work?). Neither the IBM 1.1.6 jvm nor the Microsoft 1.1.6 =
jvm works with E either. No 1.1.5 jvm from anywhere ever worked with it. =
Though we haven't tried HotSpot or BulletTrain yet, and I have big hopes =
for the 1.1.8 jvm from IBM, which rumor suggests will be a crackerjack =
implementation.
--marcs
-----Original Message-----
From: Paul Snively <psnively@earthlink.net>
To: e-lang@eros-os.org <e-lang@eros-os.org>
Date: Sunday, August 29, 1999 10:26 PM
Subject: Build Problems Resolved
=20
=20
Gentlemen,
=20
My apologies--I had suspected that I had to be overlooking something =
obvious, as I was.
=20
First of all, Mark, I did notice that it was necessary to change the =
jsrc/Makefile to refer to JCOMPILE, but thanks for the reminder!
=20
The bigger issue, though, is that the Makefiles all have CRLF line =
endings, per their having been created on Windows. Using GNU EMACS on =
Linux was making this from me by reconciling line-endings transparently. =
Using M-x hexl-find-file to open the file in hex mode revealed the =
problem, and then using M-x find-file-literally brought the file in =
without line-ending conversions... causing all of those ^M's to show up =
and be amenable to M-x replace-string ^Q^M <RET><RET>. After that, the =
remainder of getting E built consisted of some mostly trivial edits to =
the Makefiles (generally dealing with CLASSPATH issues) and replacing =
occurrances of com.sun.java.swing with javax.swing in the sources, since =
I refuse to roll back to Swing 1.0.3 and already had Swing 1.1.1 =
installed for other reasons.
=20
Incidentally, I don't know why, but E 0.8.4 also breaks the TYA JIT =
for the Blackdown JDK. If I disable the JIT, everything works fine. With =
TYA 1.4 enabled, both E and Elmer just hang sometime during =
initialization. *sigh*
=20
Thanks for the help!
Paul Snively
<mailto:psnively@earthlink.net>
=20
------=_NextPart_000_004E_01BEF2C6.992C0D40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
E seems to be a very, very intensive =
exerciser=20
for jvms and JITs. We haven't found any JIT that works with E yet =
(right,=20
markm? Or does the Symantec JIT work?). Neither the IBM 1.1.6 jvm nor =
the=20
Microsoft 1.1.6 jvm works with E either. No 1.1.5 jvm from anywhere ever =
worked=20
with it. Though we haven't tried HotSpot or BulletTrain yet, and I have =
big=20
hopes for the 1.1.8 jvm from IBM, which rumor suggests will be a =
crackerjack=20
implementation.
--marcs
-----Original =
Message-----
From:=20
Paul Snively <psnively@earthlink.net>
=
To:=20
e-lang@eros-os.org =
<e-lang@eros-os.org>
Date:=
=20
Sunday, August 29, 1999 10:26 PM
Subject: Build =
Problems=20
Resolved
Gentlemen,
My apologies--I had suspected =
that I had to=20
be overlooking something obvious, as I was.
First of all, Mark, I did notice =
that it was=20
necessary to change the jsrc/Makefile to refer to JCOMPILE, but =
thanks for=20
the reminder!
The bigger issue, though, is =
that the=20
Makefiles all have CRLF line endings, per their having been created =
on=20
Windows. Using GNU EMACS on Linux was making this from me by =
reconciling=20
line-endings transparently. Using M-x hexl-find-file to open the =
file in hex=20
mode revealed the problem, and then using M-x find-file-literally =
brought=20
the file in without line-ending conversions... causing all of those =
^M's to=20
show up and be amenable to M-x replace-string ^Q^M =
<RET><RET>.=20
After that, the remainder of getting E built consisted of some =
mostly=20
trivial edits to the Makefiles (generally dealing with CLASSPATH =
issues) and=20
replacing occurrances of com.sun.java.swing with javax.swing in the =
sources,=20
since I refuse to roll back to Swing 1.0.3 and already had Swing =
1.1.1=20
installed for other reasons.
Incidentally, I don't know why, =
but E 0.8.4=20
also breaks the TYA JIT for the Blackdown JDK. If I disable the JIT, =
everything works fine. With TYA 1.4 enabled, both E and Elmer just =
hang=20
sometime during initialization. *sigh*
Thanks for the =
help!
Paul Snively
<mailto:psnively@earthlink.net>