[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Compiling jheatbugs
From: |
pauljohn |
Subject: |
Re: Compiling jheatbugs |
Date: |
Wed, 13 Jun 2001 08:45:38 -0500 |
Marco Prosperi wrote:
> > 1. which platform you are using?
>
> Linux RedHat 6.1
I used that a couple of years ago, and at one time I knew all the ins
and outs.
> > 2. Which swarm (just 2.1.1, or a newer patched version), and precisely
> > how did you install it?
>
> swarm-hdf5-2_1_1-1_rh6_i386.rpm
It concerns me a little bit that your file names have underscores in
them. That is an indicator they were sifted through a Windows OS.
Perhaps you could ftp down a clean set directly into your RH box. The
internet is fast, after all. You might consider going to the last RPMS I
made for RH6 systems.
http://lark.cc.ukans.edu/~pauljohn/Swarm/Swarm-2.1_RPMSforRH6/i686/
That has been about a year, but I don't recall particular troubles.
> kaffe-1.0.5.tar.gz
There is an rpm for kaffe. Do you have it?
> swarm-kaffe-2_1_1-1_rh6_i386.rpm
> jheatbugs-2.1.tar.gz
> > 3. Does objective-c swarm work for you?
>
> yes, I compiled and run heatbugs correctly. Kaffe seems to work too (I
> tried with a 'Hello World'
> program).
> Maybe I need a 'Globals.*' in my '/usr/include/swarm' directory?
There was a problem back then with Kaffe. Some kaffe rpms were
installing the stuff under /usr/lib/Kaffe and some under
/usr/share/kaffe, as I recall. I know that if you swarm rpms were not
built on the same kaffe kit as the system you have, it spelled doom.
When you installed your swarm rpms, nothing like --force was required,
was it?
--
Paul E. Johnson email: address@hidden
Dept. of Political Science http://lark.cc.ukans.edu/~pauljohn
University of Kansas Office: (785) 864-9086
Lawrence, Kansas 66045 FAX: (785) 864-5700
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.