Re: opcodes.* (fwd)

• To: OS/2 Java Porting List <sl65r@hyrum.declab.usu.edu>
• Subject: Re: opcodes.* (fwd)
• From: Philip R Brenan <phil@bga.com>
• Date: Sun, 17 Sep 1995 19:34:52 -0500 (CDT)

We will also need AWK!

Phil
http://www.realtime.net/~phil

---------- Forwarded message ----------
Date: Mon, 18 Sep 1995 09:19:28 -1000
From: Darren Steven <D.Steven@its.amc.edu.au>
To: Philip R Brenan <phil@bga.com>
Cc: java-porting@java.sun.com
Subject: Re: opcodes.*

At 12:11 AM 17/09/95 -0500, you wrote:
>How do I obtain
>
>opcodes.init
>opcodes.length
>
>
These are created (in solaris) by an awk script in a the make.rules (I
think) file in the build/..../Makefiles dir.

The awk script (I'm sure that there is an awk for OS/2 - I found one for
Amiga) parses opcodes.??? to produce these two files.


I hope that helps (and good luck)

Regards,


Darren Steven

Australian Maritime College
Information Technology Services Department
Newnham Campus
Launceston, Tasmania, Australia

Phone (003) 35 4842

D.Steven@its.amc.edu.au

• Prev: Re: Code run-through meeting
• Next: Re: DCE 2.1 for OS/2...use it for Java port?
• Index: Mail Index
• Thread: Mail Thread Index