Rinil,

I just took a look at the NonStop architecture. It is a message based operating system, quite unique. I don't know how well NonStop implements POSIX functionality. Do you have a standard C++ compiler?

If the GNU "make" program can be installed on your platform, then the Xerces-C and Xalan-C libraries should have capability of being compiled.

You may need to do a little configuration of the development toolset, but I don't know why the undertaking should be impossible.

Sincerely,
Steven J. Hathaway

On 2/18/2013 8:36 PM, Baxi, Rinil Rushabh wrote:
Hello Steven,

We have a POSIX standard virtual OS on NonStop. We are planning to use that on 
NonStop Server.

Best Regards,
Rinil

-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, February 19, 2013 6:57 AM
To: [email protected]
Cc: [email protected]
Subject: Re: Regarding Xerces-C++ porting

Hi,

I am trying to port Xerces-C++ 3.1 on HP NonStop (nse) machines.
Please let me know if you have any information about it.

Best Regards,
Rinil

I don't do any work with HP NonStop systems.  Looking at the specifications on 
the Internet, the systems use the Intel Itanium (IA64) processors and a custom 
fault-tolerant hardware platform.

HP mentions that the operating system is the NonStop OS.  I have not looked at 
the native C++ development tools for this platform.  The GNU toolkit may also 
be available.

Are there other operating systems supported on the NonStop servers?  If so, 
which OS are you planning to use?

Sincerely,
Steven J. Hathaway


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to