HP3000-L Archives

June 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ian Collins <[log in to unmask]>
Reply To:
Ian Collins <[log in to unmask]>
Date:
Thu, 25 Jun 1998 11:23:13 +1200
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Can someone help me with some configuration issues.

I have a large package written in C for a variety of Unix platforms.
This package has also been ported to MPE to support our MPE customer
base. It has always been a long and drawnout process porting to MPE.
However, we have just moved to 5.5, and I was considering the Posix
capabilities herein.
Ideally, I would like to compile and link my package in the posix
environment, and for our customer base to take those executables and run
them in either the posix or native environment.
This would turn our MPE porting platform into just another Unix machine.

A number of questions,

1. I have noticed from searching this mailing list that there is gcc,
gdb and emacs support in the 5.5 posix layer. Where would I get them,
and how reliable are they?

2. If I do use the gcc to compile and link my package, can the resulting
executables only run in the posix layer? Or can they also be run in the
native MPE?

3. When we migrated to 5.5, we took our existing HP/C compiler (from
version 4) with us (as HP wanted an excessive figure to upgrade to the
latest C compiler). Can we use the native C tools from the posix
environment to build our package?

Lastly, an open question. Has anyone else any suggestions, tips or help
they can offer with a project as described above?

Ian Collins.
KIWIPLAN NZ.

ATOM RSS1 RSS2