Blackdown on SuSE

[Sam Joseph]

Hi,

I've been trying to install a blackdown jdk on an IBM penguin box using
SuSE linux and have not had much luck so far.

I can extract the blackdown version, and unpack it but when I try to run

the java command I get this:

l008064:~/j2sdk1.3.0/bin # ./java -version
Error: can't find libjava.so.

and I also get a sinking feeling when reading the system requirements
for blackdown which say:

 Check your version of glibc using the following command:

 ls /lib/libc-*

 The output of this command should show libc-2.1.3.so or higher.

when I check ls /lib/libc-* I find nothing.

The closest I get is libc.so.6 and I am really not sure where to go from
here.

My apologies for my lack of ignorance, but I am not a regular Linux user
and am not sure how to deal with these library issues.

Thanks in advance

CHEERS> SAM





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Blackdown on SuSE

[Sam Joseph]

Follow up to my own mail - I got help from another list, the solution seems
to be:

>You need JDK that is compiled for s390(search google "s390 jdk"), for
> example:

>
http://www.ibiblio.org/pub/languages/java/blackdown.org/JDK-1.2.2/s390/FCS/?M=A



Sam Joseph wrote:

> I've been trying to install a blackdown jdk on an IBM penguin box using
> SuSE linux and have not had much luck so far.
>
> I can extract the blackdown version, and unpack it but when I try to run
>
> the java command I get this:
>
> l008064:~/j2sdk1.3.0/bin # ./java -version
> Error: can't find libjava.so.
>
> and I also get a sinking feeling when reading the system requirements
> for blackdown which say:
>
>  Check your version of glibc using the following command:
>
>  ls /lib/libc-*
>
>  The output of this command should show libc-2.1.3.so or higher.
>
> when I check ls /lib/libc-* I find nothing.
>
> The closest I get is libc.so.6 and I am really not sure where to go from
> here.
>
> My apologies for my lack of ignorance, but I am not a regular Linux user
> and am not sure how to deal with these library issues.
>
> Thanks in advance
>
> CHEERS> SAM
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Blackdown on SuSE

[Sam Joseph]

Juergen Kreileder wrote:

> On Wed, 27 Jun 2001, Alan Hawrelak wrote:
>
> > Sam Joseph wrote:
> >
> >> I can extract the blackdown version, and unpack it but when I try
> >> to run
> >>
> >> the java command I get this:
> >>
> >> l008064:~/j2sdk1.3.0/bin # ./java -version
> >> Error: can't find libjava.so.
>
> Looks more like he tried to run a x86 build on S/390

Juergen is right. This was the problem, as someone on a different list
also informed me.
I had been given access to a machine remotely and didn't know what
processor was being used.

Is there some way to check this remotely perhaps?

[quick check of system properties]

I guess typing printenv HOSTTYPE might help.
It all sounds so simple after the event ...

Anyhow, thanks to Alan, Franz and Amol for various helpful comments on the
java library issues which have helped advance my understanding of the
issue.

CHEERS> SAM


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Threads on i386-redhat-linux-gnu

[Sam Joseph]

Hi All,

So I'm having this problem that the logging system that I have used
successfully on other linux platforms is not working on
i386-redhat-linux-gnu.

The logging system is designed to store logging messages and then write
them to the log file in a low priority thread.  However when I run the
code on i386-redhat-linux-gnu the logging thread doesn't even start.
The main Logger class implements runnable, and a new thread is created
in the constructor:

  public Logger( Log p_log)
  {
if(o_verbosity > 0) System.out.println("creating new logger");
o_messages = new Vector(100);
o_log = p_log;
o_thread = new Thread( this);
o_running = false;
o_sem = new Semaphore();
o_thread.start();
if(o_verbosity > 0) System.out.println("starting logger thread");
  }

and as you can see the thread is started, but the run method doesn't
start.  Or at least the debug command on the first line of the run
command does not get displayed:


  public void run()
  {
if(o_verbosity > 0) System.out.println("logger thread running ...");

o_running = true;
...
...


And yes, the o_verbosity is set to 10.  Is there some special setting
that I need on red hat linux to allow the spawning of new threads?

Thanks in advance.

CHEERS> SAM


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]