Julian and I talked over coffee this morning and we have some ideas on how
to improve some aspects of this that I'll do something about before the
next release. But, these changes will only simplify making sure that
Jikes RVM can find/download & configure classpath. I don't see anything
we can do about people trying to build classpath libraries on machines
that don't even have the header files for GTK.
Disabling GTK completely is unattractive as it implies that you can't run
any awt programs, and some simple ones actually work now.
Chris Hoffmann <hoffmann@...>
Sent by: jikesrvm-core-admin@...
10/15/2003 12:34 PM
Please respond to jikesrvm-core
Subject: Re: [Jikesrvm-core] automatic classpath download
You probably don't really need GCTK+ installed, if I remember correctly
this was only in the JikesRVM configuration because Watson used it in
some tests/reports on Intel. If you disable the gtk peer on intel, as
jBuildClassPathJar already does for non-Intel builds, I *think* you'll
I agree, though, getting classpath built properly is often a real pain.
Steve Blackburn wrote:
> Hi all,
> I think what Dave did is a good move and will reduce the level of
> However, as my painful experience today shows, we have a long way to go.
> I have searched the web and cannot find a classpath rpm. I binary
> distribution would make life a lot easier.
> I tried to use the new system and blew a lot of time running into the
> following problems:
> 1. For reasons I do not understand, wget behaves very poorly over a
> slow connect---or could it be a firewall issue? I don't know...
> The upshot was the entire build stalled.
> Downloading GNU Classpath
> => `classpath.tar.gz'
> Resolving alpha.gnu.org... done.
> Connecting to alpha.gnu.org[18.104.22.168]:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done. ==> PWD ... done.
> ==> TYPE I ... done. ==> CWD /pub/gnu/classpath ... done.
> ==> PORT ... done. ==> RETR classpath-0.06.tar.gz ... done.
> <hangs here>
> 2. I ftp'd the file successfully (well inside a minute), and
> untarred it in /tmp. I then followed the instructions on the web
> page and set my CLASSPATH_ROOT to /tmp. I find this perverse.
> Why isn't the CLASSPATH_ROOT /tmp/classpath-0.06??
> ...anyway it didn't work. It apparently (silently) ignored my
> setting of CLASSPATH_ROOT and just tried (fruitlessly) to download
> the file.
> I eventually discovered that it was looking for stuff in
> $CLASSPATH_ROOT/classspath, not $CLASSPATH_ROOT/classpath-0.06.
> As I write this email, I discover that the instructions that I had
> so "carefully" followed on the userguide do actually ask me to
> rename the directory. But if you take a look, I think you'll
> that the formatting of the text unfortunately makes it easy to
> miss! Argh!
> The above would all be solved if we just invited the user to tell
> us where the sources where, rather than telling us the parent of
> the directory with the sources in it, and then asking them to
> rename the directory from what they got when they untarred it.
> I the came up with the cunning idea of copying the classpath
> tarball to a local server and letting the build pick it up from
> there. I did that, found out the file I needed to change and
> lo and belhold it worked. But...
> 3. The machine I was working on did not have the gctk+ source files
> installed. So it died in a heap and my efforts were all for
> OK. So you all can say I made some dumb mistakes and I'm incompetent.
> But I was super motivated----I need something done "yesterday", and am
> pretty well informed. I wonder sometimes how many potential users we
> lose because their first experience is like the one above and they don't
> have the stamina to work it through. A slightly depressing thought.
> My 2c worth. Now back to the thing I was trying to do an hour ago......
> Jikesrvm-core mailing list
Chris Hoffmann -- Dept. of Computer Science/UMass at Amherst
Jikesrvm-core mailing list