Willem Grooters wrote:
I would like to add the shops that use VMS-native compilers (Fortran,
Cobol, Pascal, etc). If GCC delivers a non-VMS object format, it is of
no use at all. Even if it did - what would be the benefit (except the
cost)?
GCC delivers a VMS object format. With IA64, OpenVMS
The existence of a good port of GNU C/C++ for OpenVMS would make porting
Open
Source tools to OpenVMS easier, which would benefit some enterprise
development.
Well you are making exactly my point which is that a Unix-like interface
might be nice for porting Open Source tools, but I still
for HP C are not quite as
outrageous as unlimited licenses and I have seen various sites handle the problem that
way. Perhaps a case could be made for including a single-user C license with the OS.
Having said all this, I would be happy to see an up-to-date and useable GCC port on
OpenVMS just
What would help a lot with open source porting in general would be having
a sufficiently robust GNV package with all the utilities a Configure script
is likely to need and a cc command that is compatible with what unixy
packages expect (regardless of what compiler that cc command invokes).
Craig Berry wrote:
Having said all this, I would be happy to see an up-to-date and
useable GCC port on OpenVMS just for the niftiness factor if nothing
else. It might bring with it some other capabilities, like Objective
C, that are otherwise unavailable. But given the lack of a business
case
files
for objects and executables. There have been some extensions that have
been provided.
So there may be a possibility of building VMS binaries including
executables, objects, and shared images on other IA64 systems.
Or the reverse.
The problem with volunteers maintaining GCC on OpenVMS
